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:
When querying issues, the "Last seen" always seem to show a value within the queried time frame, not the actual "first seen". In Sentry, the "first seen" always displays correctly as the actual timestamp this issue was first seen (first event in the issue)
When exploring the query sent to Sentry, I see the interval for timestamps set for start and end are very close:
When using the issues (with first seen) for Annotations, I can't force the start time to be very early (to get the correct data from sentry) without changing the entire time range for the dashboard, which makes it a little useless, since I want to see when new issues occurred, but I can't rely on the date.
What you expected to happen:
That there's a way to correctly get the actual "first seen" for issues when querying them for annotaitons.
How to reproduce it (as minimally and precisely as possible):
Add sentry integration
Add annotations like on screenshot
Screenshots
Environment:
Grafana version: Latest Grafana Cloud
Plugin version: 1.5.0
The text was updated successfully, but these errors were encountered:
What happened:
When querying issues, the "Last seen" always seem to show a value within the queried time frame, not the actual "first seen". In Sentry, the "first seen" always displays correctly as the actual timestamp this issue was first seen (first event in the issue)
When exploring the query sent to Sentry, I see the interval for timestamps set for
start
andend
are very close:https://sentry.io/api/0/organizations/xxxl/issues/?end=2024-01-15T19%3A56%3A22&environment=production&limit=10000&project=xxxxxx&query=&sort=date&start=2024-01-15T13%3A56%3A22
When using the issues (with first seen) for Annotations, I can't force the
start
time to be very early (to get the correct data from sentry) without changing the entire time range for the dashboard, which makes it a little useless, since I want to see when new issues occurred, but I can't rely on the date.What you expected to happen:
That there's a way to correctly get the actual "first seen" for issues when querying them for annotaitons.
How to reproduce it (as minimally and precisely as possible):
Screenshots
Environment:
The text was updated successfully, but these errors were encountered: