Grouped queries against the documented /api/0/organizations/{org}/events-timeseries/ endpoint return HTTP 500 {"detail":"Internal Error"} for the errors and discover datasets, while the same queries succeed ungrouped and succeed grouped on the spans dataset.
Repro (any org with error events):
GET /api/0/organizations/{org}/events-timeseries/?dataset=discover&yAxis=count()&interval=3600&statsPeriod=1d&groupBy=project&sort=-project&topEvents=5
Expected: a grouped time series, as documented. Actual: 500 {"detail":"Internal Error"}. Example error IDs from 2026-07-17: 2f71f4784f1b44189ebc0677875b5f52, 41cccfe4a6e94063816aed11153d3add, 5aa8d048c1624638b9d853e92a4d35d3.
The same request shape returned 200 earlier on 2026-07-17, so this looks like a regression rather than an intended contract change. It reproduces with statsPeriod or start/end, with and without sort, and with excludeOther=0 or 1. Ungrouped requests on the same datasets return 200, and grouped requests with dataset=spans return 200.
Impact: the Grafana Sentry data source migrated its Events Stats queries to this endpoint and has had to route grouped queries back to the legacy events-stats endpoint until this is resolved.
Grouped queries against the documented
/api/0/organizations/{org}/events-timeseries/endpoint returnHTTP 500 {"detail":"Internal Error"}for theerrorsanddiscoverdatasets, while the same queries succeed ungrouped and succeed grouped on thespansdataset.Repro (any org with error events):
Expected: a grouped time series, as documented. Actual:
500 {"detail":"Internal Error"}. Example error IDs from 2026-07-17:2f71f4784f1b44189ebc0677875b5f52,41cccfe4a6e94063816aed11153d3add,5aa8d048c1624638b9d853e92a4d35d3.The same request shape returned 200 earlier on 2026-07-17, so this looks like a regression rather than an intended contract change. It reproduces with
statsPeriodorstart/end, with and withoutsort, and withexcludeOther=0or1. Ungrouped requests on the same datasets return 200, and grouped requests withdataset=spansreturn 200.Impact: the Grafana Sentry data source migrated its Events Stats queries to this endpoint and has had to route grouped queries back to the legacy
events-statsendpoint until this is resolved.