-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[APM] Decrease amount of tick labels in the transaction graphs #18085
Comments
Original comment by @sqren:
Yes, we have full control over the ticks. Currently we require 7 tick marks, and let d3 decide the specific values. |
Original comment by @formgeist: @sqren Can we change it to max. 8 on the x-axis? That's just a magic number I pulled out of my 🎩 but from what I can count that's a decent amount before it breaks on the viewport. |
Original comment by @sqren: @formgeist That should be possible. I actually thought we already limited it to 7, but looking closer at the screenshot you posted I see 12 ticks, so that's clearly not the case. |
Original comment by @sqren: Btw. should it be responsive? So depending on the width: or something like it? |
Original comment by @formgeist: Lets leave the responsiveness out of it for now. 8 ticks is good as default for any size viewport IMO. |
Fixed in #44870 |
Original comment by @formgeist:
When the viewport is small(er), the amount of tick labels displayed on the x-axis for the transaction graphs (Response times and RPM/TPM) overlap. A quick fix would be simply decrease the amount of labels displayed on the x-axis.
It seems the amount of ticks is determined by the time range selected (split in minutes have more than split in hours etc.). Is this controlled by Kibana for some reason, or can we set a min/max tick label amount in the graphs ourselves?
The text was updated successfully, but these errors were encountered: