We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug No data on multiple panels
Environment NAbox 3.0_beta7 (2021-10-02) - Alpine Linux 3.14.2 Grafana8.1.5 Graphite1.2.0 NetApp Harvest21.08.0-6 NetApp NMSDK 9.8P2
To Reproduce Go to SVM details dashboard and get no data such as under Highlights
Expected behavior Tell us what should happen
Actual behavior Tell us what happens instead
Possible solution, workaround, fix No
Additional context Internal system, if you want I can give access as it is on corporate network.
-Paul Stejskal
The text was updated successfully, but these errors were encountered:
@MrObvious Yes send us an email with system details and we'll check.
Sorry, something went wrong.
Rahul,
What e-mail is best? ng-harvest-maintainers?
Feel free to hit me up on Teams as well.
@MrObvious's Grafana was setup with a default Graphite datasource
Graphite
and the SVM details dashboard panels do not define a datasource
"datasource": null,
which means the default (Graphite) will be used. I changed all these to
"datasource": "${DS_PROMETHEUS}",
and boom, beautiful SVM stats.
Fixed by #640
No branches or pull requests
Describe the bug
No data on multiple panels
Environment
NAbox 3.0_beta7 (2021-10-02) - Alpine Linux 3.14.2
Grafana8.1.5
Graphite1.2.0
NetApp Harvest21.08.0-6
NetApp NMSDK 9.8P2
To Reproduce
Go to SVM details dashboard and get no data such as under Highlights
Expected behavior
Tell us what should happen
Actual behavior
Tell us what happens instead
Possible solution, workaround, fix
No
Additional context
Internal system, if you want I can give access as it is on corporate network.
-Paul Stejskal
The text was updated successfully, but these errors were encountered: