Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I didn't use distinct count on timestamp because you’re essentially counting how many distinct timestamps appear, which isn't typically useful for visualizing time-series data. Since the timestamp field is being used as a row-pivot, it's already grouping data by each distinct timestamp without needing to aggregate it. You'd want the graph to display the actual time points rather than a count of those time points.
However, if you need to use "timestamp": "distinct count" for a specific purpose (such as counting the number of unique timestamps or events), feel free to include it, but it may not provide meaningful insights in a line chart that shows trends over time.