8000 aliasYAxis – Setting axis right not working with dynamic alias names · Issue #14 · grafana/grafana · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

aliasYAxis – Setting axis right not working with dynamic alias names 8000 #14

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

Closed
syepes opened this issue Jan 22, 2014 · 1 comment
Closed

Comments

@syepes
Copy link
Contributor
syepes commented Jan 22, 2014

Hello,

I have just noticed and issue when setting the axis to the right of a target that is using the Graphite legendValue() function.
I think the issue must come from the fact that the target alias name is dynamic, so each time the target alias name changes it does not find the stored setting in the panel config (aliasYAxis).

As a workaround I have removed the legendValue() function and it work as expected.

          {
              "target": "legendValue(alias(timeShift(Performance.node.CustomPoller.fw_activesessions,\"1d\"),\"Active Sessions -1D\"),\"max\",\"avg\",\"si\")"
          },
..
..
..
          "aliasYAxis": {
            "Active Sessions -1D max  140.51K   avg  127.61K   ": 2,
            "Active Sessions     max  200.20K   avg  130.92K   ": 2,
            "Active Sessions     max  187.12K   avg  129.21K   ": 2,
            "Active Sessions -1D max  152.63K   avg  127.35K   ": 2,
            "Active Sessions -1D max  148.54K   avg  129.10K   ": 2,
            "Active Sessions     max  162.33K   avg  128.89K   ": 2
          },

Best regards,
Sebas

@torkelo
Copy link
Contributor
torkelo commented Jan 22, 2014

Had not thought about this scenario. I think it could be solved by checking if the target name (alias) returned from graphite contains legend values then parse them out of the alias, so the alias that is used to map to YAxis settings do not change.

Another approach would be to calculate the legend values client side, but I think I prefer to let graphite do this.

Thanks for the feedback! Will take a lot at this when I have some spare time.

@torkelo torkelo closed this as completed in 0015f81 Feb 6, 2014
Dieterbe pushed a commit to Dieterbe/grafana that referenced this issue May 12, 2015
Text adjustments as outlined in issue
8000
s 14 and 15
Dieterbe pushed a commit to Dieterbe/grafana that referenced this issue May 12, 2015
bentranter referenced this issue in walmartlabs/grafana May 15, 2017
Use radio buttons for version select
roidelapluie added a commit to roidelapluie/grafana that referenced this issue Dec 24, 2017
owen-d added a commit to owen-d/grafana that referenced this issue Apr 19, 2021
stevepostill referenced this issue in Reveal-International/grafana Nov 3, 2021
…m-github to revdev

* commit '8c0e0cf22d394075e54ba878922014e64e2cb169':
  Release v8.1.5
  fix typo in grafana#39208 causing "plot is undefined" error (grafana#39304)
  ReleaseNotes: Updated changelog and release notes for 8.1.4 (grafana#39288) (grafana#39289)
Jguer pushed a commit that referenced this issue Dec 5, 2022
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

2 participants
0