Support subsecond resolutions in range selector

[sakjur]

Why do we need this?

With Grafana becoming more generally useful than just an observability visualization tool, the usecases where there is a legitimate need for subsecond range selection increases (such as electrical engineering, nuclear physics, rocketry).

What needs to be done?

• [ ] Decide reasonable minimum resolution (ms/µs/ns)
  • JavaScript uses milliseconds, Go uses nanoseconds. Going beyond that in either language risks introducing significant complexity. Do we want to do that? (see #6252)
• [ ] Frontend needs to support subsecond range selection
• [ ] Backend needs to support subsecond range selection
  • I have a branch for the datemath lib that we're using implementing that https://github.com/sakjur/go-datemath/tree/nanoseconds

Related comments from #44707:

Finally tested this and everything seems to work fine. I wonder if we should also make the range selector take less than 1s time diff as this does not work now

But that can be left for different PR.

We have both a backend and frontend implementation of the range selector, we should make sure that both gets updated when doing this 🙂 I can probably help out with the backend if someone decides to pick this up for the frontend. On the backend side we're using https://github.com/vectordotdev/go-datemath through the legacydata (🙃) package and it wouldn't be too hard to add support for millisecond precision in the upstream package as well as long as we remember it.

Originally posted by @sakjur in https://github.com/grafana/grafana/issues/44707#issuecomment-1115085958

[alexanderzobnin]

@sakjur bingo! 50000! So we should fix this asap :smile:

[sakjur]

💪 I know, right!

[FZambia]

Oh no, I just came from mine which was 50001 😄

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had activity in the last year. It will be closed in 30 days if no further activity occurs. Please feel free to leave a comment if you believe the issue is still relevant. Thank you for your contributions!

[gabor]

it's still relevant.