Skip to content

Conversation

@gggritso
Copy link
Member

There's an API difference between /events-stats/ and /events-timeseries/. In /events-stats/, the fields parameter includes both the group by, and the Y axis. e.g., fields can be ["count(span.duration)", "environment"] and the Y axis would be ["count(span.duration)"] which works correctly, and the "environment" field is only used for the grouping.

In /events-timeseries/, there is not "fields", there is only an explicit group by, and an explicit Y axis. In this PR, I'm filtering the Y axis values out of the groupBy, to prevent us sending an unnecessary groupBy parameter. This doesn't change the response at all, it's just less confusing when looking at the request.

@gggritso gggritso requested a review from a team November 17, 2025 20:39
@linear
Copy link

linear bot commented Nov 17, 2025

@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Nov 17, 2025
topEvents,
groupBy: fields as unknown as any,
groupBy,
pageFilters: pageFilters.selection,

This comment was marked as outdated.

@gggritso gggritso merged commit 6683ff1 into master Nov 18, 2025
47 checks passed
@gggritso gggritso deleted the georgegritsouk/eng-5914-remove-unneeded-groupby-parameter-from-queries branch November 18, 2025 15:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants