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 have made an attempt to better understand percentiles in Atlas and hopefully address this issue as well: #718.
Given the following request latencies:
And applying the example query yields the following result:
name,requestLatency,:eq,(,25,50,90,),:percentiles
Unfortunately, from the generated docs, the input graph looks as follows, due to aggregation:
Obviously having percentiles generate from a single input does not make sense, therefore ideally it would be possible to generate the example input using
:all
, but I didn't pursue this route any further.Please let me know if I can enhance the example in any way!