-
Notifications
You must be signed in to change notification settings - Fork 18
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
Opensearch plugin doesn't support using Grafana configured time zone for ES queries #109
Comments
👋 Thanks for creating this issue, @ I’m forwarding this issue to the observability squad for review |
@thislyc thanks for reporting your issue, we're trying to recreate it on our end. Do you know:
I looked in main grafana and noticed there does seem to be an open issue around relative timezones, so it's possible you're running into that?: grafana/grafana#59665 I believe this plugin works the same as all grafana plugins in which it:
Can you explain more how converting a query to UTC and back would result in inaccurate or inconsistent data? I would expect the opposite? |
@thislyc thanks for that! Unfortunately I still haven't been able to reproduce this, so a few more questions:
|
It self hosted
all open search queries
In fact I don't use opensearch, but ElasticSearch6.5 |
Thanks for that @thislyc one more clarifying q are you running Elastic Search 6.5 through Amazon's Open Search Service or is it self hosted? |
Self hosted |
Hi @thislyc, we haven't been able to reproduce this yet.
Do you have a screenshot of setting the time zone to "auto"? For the time zone picker, there's only a "Default" option. Can you share the dashboard JSON? You can do so as follows:
|
Going to close this since we haven't been able to reproduce it and it's been a while. But if you're still running into issues please feel free to make a new issue with the dashboard json as @kevinwcyu has suggested and we will take another look! |
While using Grafana for data visualization, I noticed that the Opensearch plugin doesn't support using the time zone configured in Grafana for ES queries. Regardless of how I change the time zone settings in Grafana, the Opensearch plugin always uses the UTC time zone for queries.
Expected result: The Opensearch plugin should support using the time zone configured in Grafana for ES queries to ensure data accuracy and consistency.
Steps to reproduce:
Set different time zones in Grafana, such as UTC+8, UTC-5, etc.
Create a panel based on the Opensearch data source and set the time zone to "auto".
Observe the time range and display of the query results.
Actual result: Regardless of the time zone set in Grafana, the Opensearch plugin always uses the UTC time zone for queries, resulting in inaccurate or inconsistent data.
Suggested solution: Add support for using the time zone configured in Grafana for ES queries to the Opensearch plugin to ensure data accuracy and consistency. An option can be added in the plugin settings to allow users to choose whether to use the time zone configured in Grafana for ES queries. Additionally, updating the plugin documentation to explicitly state that the plugin doesn't support using the time zone configured in Grafana for ES queries can be considered.
The text was updated successfully, but these errors were encountered: