-
Notifications
You must be signed in to change notification settings - Fork 13
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
Error while parsing alert_dashboard from grafana 5.0.0 #372
Labels
Comments
@shtripat @nthomas-redhat @r0h4n suggestion please |
Have you checked with the Grafana team about this irregularity? Maybe file an issue on them. |
Anything related to 5.0.0 is lower priority as we already in agreement that we are not planning to upgrade in the upcoming release. So why testing with version? I suggest to use 4,x,x and worry about this later. @GowthamShanmugam |
GowthamShanmugam
added a commit
to GowthamShanmugam/monitoring-integration
that referenced
this issue
Oct 4, 2018
I did small change to work existing alerting logic to work with latest grafana. tendrl-bug-id: Tendrl#372 Signed-off-by: GowthamShanmugasundaram <[email protected]>
GowthamShanmugam
added a commit
to GowthamShanmugam/monitoring-integration
that referenced
this issue
Jan 14, 2019
I did small change to work existing alerting logic to work with latest grafana. tendrl-bug-id: Tendrl#372 Signed-off-by: GowthamShanmugasundaram <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
grafana 5.0.0 supports backward compatibility, It creates alert_dashboard with json which we are passing. And it gives the same json when we send dashboard API request to grafana. problem with the new version is when someone does save operation in grafana directly in grafana then dashboard json is converted to a new version of json. So the alert dashboard logic in monitoring-integration is affected.
in older json all panels are stored under rows, so the json is like
so now the new json is changed like,
The text was updated successfully, but these errors were encountered: