The use case is that I've constructed a pattern task in a container with a dashboard for use as an preliminary start off line which I'd like customers to have the ability to customize for his or her very own needs. Using the provisioning methodology at once they'll not make and save variations with no duplicating the dashboard first. I'd recommend that even including a 'Save As' operate to a half of the "Cannot save provisioned dashboard" UI could be a primary enchancment to the UX. I copy the exported dashboards to the /etc/grafana/provisioning and once I ship out a curl command with the exported json. I get an error "cannot save provisioned dashboard". I am in search of this function as effectively or a workflow answer that permits builders to bulk import dashboards into Grafana from github with no provisioning in order that they'll work on them after which export. We have been utilizing the supply / export possibility for native growth on developer workstations with an older variation of Grafana. Without this function we're caught manually copy and pasting json to replace developer workspaces which leaves us with potential for work to be lost. We will not revert this alteration however we ought to always introduce an possibility for permitting customers to save lots of over provisioned dashboards. To create the persistent dashboard, you ought to have on the least the Manage Config Maps Rancher RBAC permissions assigned to you within the task or namespace that comprises the Grafana Dashboards.
Grafana Cant Save When Volumes This correlates to the monitoring-dashboard-edit or monitoring-dashboard-admin Kubernetes native RBAC Roles uncovered by the Monitoring chart. In order to stop problems, we have briefly set our customers to solely be granted the Viewer role, however this prevents our customers from creating new short-term dashboards for testing purposes. We'd just like the provisioned dashboards to perpetually stay unchanged until we modify our config files. Of course, I can nonetheless use the API to export dashboards. But since I can't save provisioned dashboards, the export is ineffective because it does not include unsaved changes. Since saving the provisioned dashboards just isn't allowed , we can't use it for automating growth to create dashboards which shall be later deployed. While changing provisioned dashboards by importing was allowed in 5.0.x model of grafana it isn't allowed in newer versions. Since we wish to have the whole lot automated, we have a script that exports all dashboards applying the API. With provisioned dashboards being readonly now (#10883), this strategy not works. We need to manually copy and paste the dashboard JSON from the UI so we will commit it. Doing stuff manually in an automatic world is IMHO an anti-pattern. While I recognize the rationale behind #10883 with regards to database vs. filesystem, there could nonetheless be a technique to export modified provisioned dashboards by way of API.
Saving edits in UI on provisioned dashboards can be a nice-to-have. This annotation can be added by default inside the brand new monitoring chart launched by Rancher v2.5.8, however nonetheless should be manually utilized for customers of earlier Rancher versions. To enable the Grafana dashboard to persist after the Grafana occasion restarts, add the dashboard configuration JSON right into a ConfigMap. ConfigMaps additionally enable the dashboards to be deployed with a GitOps or CD centered approach. This enables the dashboard to be put underneath mannequin control. By default, Grafana is configured to observe all ConfigMaps with the grafana_dashboard label inside the cattle-dashboards namespace. The dialog telling you that you just can't save over a provisioned dashboard appears. I am not infront of my laptop computer as of now so I cant share the precise files. However, the folders dashboards and provisioning include dashboard json statistics and two datasources in a provisioning.yml file. Starting grafana in growth mode and see this error message every time provisioning running. To create a persistent dashboard, you have to to get the JSON mannequin of the dashboard you wish to persist. To see the hyperlinks to the exterior monitoring UIs, such as Grafana dashboards, you have to no less than a project-member role.
But I agree, perhaps an choice in provisioning to "allow UI save" is value contemplating if that's what many customers want. I can replace the dashboard with /api/dashboards/db endpoint however cannot reserve it by means of the gui. How about with the ability to edit the dashboard in a "namespace" and as soon as the editor is proud of the change there's a "save/commit" step. Sign up for a free GitHub account to open a crisis and make contact with its maintainers and the community. So, yes, in a approach the official documentation-provided dashboards should not working. I go assess my dashboards, they're present, But as soon as I click, they load empty. Users with Editor position are capable of save over Provisioned dashboard. Just save as a draft and have one factor ballot these drafts and export it by means of the API and apply anything promotion-/provision-process we might like exterior of Grafana. We test to make use of grafana with docker container for equally improvement and deployment. I even have the identical problem.Wish that there's an choice to permit UI save by admin user. You can nonetheless use your workflow of adjusting it UI and backing it up in git however it's important to make use of API to export & import. Systemctl restart grafana-server does not appear to be working with my instance.
You have to have the cluster-admin ClusterRole permission. Dashboards which are continued employing ConfigMaps can't be deleted or edited from the Grafana UI. The ameliorations are one way or the other continued to Grafana's DB, and the ameliorations stay on the dashboard, even after refreshing. Click the "Save dashboard" button on the house dashboard to view the issue.
