After a deployment, I monitor the Error Rate/Error Analytics chart to compare the error rate before and after the deployment finished. Occasionally there’s an error spike that occurs due to the deploy, but subsides after a short time. When this kind of spike occurs, it is more difficult to compare the error rate, because the Y-axis grows to encompass the new error spike.
It would be great if I was able to customize the y-axis, so that I could more accurately compare the error rate before and after the deployment (when the error spike occurred). If I was able to set the upper-bound to 1% or even .5%, I would be able to more easily compare the error rate over time.
I’m thinking that the chart would look like this afterwards, where the data from the spike is truncated, which is okay and not my concern. I really wouldn’t care if the truncated section was red either, since I’m aware of the spike.
Seems like a straight-forward change once there’s some kind of UI to customize the y-axis. You could map over the data-points and max them out at the new upper-bound, or the chart component might already handle truncating data that exceeds the max y-axis.
- I want this, too
- I have more info to share (reply below)
- I have a solution for this
We take feature ideas seriously and our product managers review every one when plotting their roadmaps. However, there is no guarantee this feature will be implemented. This post ensures the idea is put on the table and discussed though. So please vote and share your extra details with our team.