Skip to content
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

logBase in chart with 2 y-axes results in incorrect detection of yMaxLeft and yMaxRight #250

Open
markzabaro opened this issue Mar 17, 2020 · 0 comments

Comments

@markzabaro
Copy link

Apologies I can't share my testcase, the metric path is from work.

start with a chart that has a y-axis and a second y-axis: /render/?from=-24hours&width=1300&height=600&&lineWidth=2&target=aliasByNode(hourly.endpoints.*.wallclock.percentile_99,3,4,2)&target=secondYAxis(aliasByNode(hourly.endpoints.*.request_count,3,2))

add logBase=2 to the chart and it renders, but lots of things are different (beyond mere scaling of values and the labelling of the axes, which is the sole change I expect from adding this parameter).

What I observe:

  • linear Base: previously left y axis had range from 0 to 700 and right y axis from 0 to 1250, with 5 lines visible across the entire timespan.
  • log Base: left y-axis range is 8-128; right y-axis range is 1-256. only 3 lines visible across entire timespan. if i manually override yMaxRight and yMaxLeft to some value about the maximums autochosen in the linear scaled version, all lines are shown.

My guess is that the addition of logBase in a two y-axis scenario somehow interferes with default value detection for yMaxLeft and yMaxRight.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant