Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for float timestamp for logs #626

Open
oplehto opened this issue Sep 12, 2024 · 2 comments · May be fixed by #668
Open

Support for float timestamp for logs #626

oplehto opened this issue Sep 12, 2024 · 2 comments · May be fixed by #668
Assignees
Labels
p2 Priority 2
Milestone

Comments

@oplehto
Copy link

oplehto commented Sep 12, 2024

In the logs panel and logs explore, if the first column is a float then it should be considered a timestamp with subsecond precision (similar to the UInt64 special case for Unix timestamps).

@Slach Slach added this to the 3.3.0 milestone Sep 12, 2024
@oplehto
Copy link
Author

oplehto commented Sep 12, 2024

Thining a bit further, the most versatile way would be the following:

  • The timestamp column should be obtained from the "Query Settings" tab if its set there
  • The "Query Settings" timestamp selector should support also Float* and UInt64 based timestamps (this would also benefit timeseries and table panes)

@svb-alt svb-alt added p1 Priority 1 p2 Priority 2 and removed p1 Priority 1 labels Nov 5, 2024
@Slach
Copy link
Collaborator

Slach commented Nov 12, 2024

@oplehto when use UInt64, shall we define how many right pad digits will use for fractional seconds? or just need to define 3 right digits always and use is as milliseconds?

@lunaticusgreen lunaticusgreen linked a pull request Nov 24, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p2 Priority 2
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants