You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
Trim Edges functionality has not been working since v2.16.0 in alerts. The workaround for them is to shift the time from the datetime picker. However, since 2.22.2 it has stopped working in normal visualizations too. Currently, Trim Edges values are not considered and have no effect on a visualization.
What you expected to happen:
The value that is entered to Trim Edges should cut the values from the beginning and end of the values in the panels. (The same behavior as in an Elasticsearch data source.)
How to reproduce it (as minimally and precisely as possible):
1- Create a time series visualization with an OpenSearch data source in a dashboard.
2- Try to enter some values to the Trim Edges input box in the @timestamp date histogram aggregation.
Anything else we need to know?:
This problem previously exists in the alerts but not as critical as exists in visualizations. Every visualization in a Grafana deployment can be affected by this bug.
Environment:
Grafana version: 11.3.2
OpenSearch version: 2.17.1
Plugin version: 2.22.2
The text was updated successfully, but these errors were encountered:
I managed to get Trim Edges working again by disabling openSearchBackendFlowEnabled feature toggle. Trim Edges in alerts are still not working. I think this might be related with #545 and #407.
What happened:
Trim Edges functionality has not been working since v2.16.0 in alerts. The workaround for them is to shift the time from the datetime picker. However, since 2.22.2 it has stopped working in normal visualizations too. Currently, Trim Edges values are not considered and have no effect on a visualization.
What you expected to happen:
The value that is entered to Trim Edges should cut the values from the beginning and end of the values in the panels. (The same behavior as in an Elasticsearch data source.)
How to reproduce it (as minimally and precisely as possible):
1- Create a time series visualization with an OpenSearch data source in a dashboard.
2- Try to enter some values to the Trim Edges input box in the
@timestamp
date histogram aggregation.Anything else we need to know?:
This problem previously exists in the alerts but not as critical as exists in visualizations. Every visualization in a Grafana deployment can be affected by this bug.
Environment:
The text was updated successfully, but these errors were encountered: