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

[BUG] Uploading a dashboard to two different folders problem #57

Open
pallix opened this issue May 7, 2021 · 10 comments
Open

[BUG] Uploading a dashboard to two different folders problem #57

pallix opened this issue May 7, 2021 · 10 comments
Assignees
Labels
bug Something isn't working

Comments

@pallix
Copy link

pallix commented May 7, 2021

It's currently not possible to upload the same dashboard to two different folders. In my setup I would like to have one folder for each deployment environment of the app, thus I need to upload the dashboard to different folders. Each folder contains the dashboard of an environment.

When uploading first to buga folder (when the application starts) and then to bugb folder (when the application start), dashboards in the buga folder disappear (or are moved to bugb).

I have written a small application to reproduce the problem: https://github.com/pallix/bug_prom_ex_two_folders

First run:

GRAFANA_API_KEY="here-the-key" GRAFANA_HOST="here-the-host" DEPLOYMENT_ENV=buga iex -S mix

and observe that the dashboards are correctly in buga, then run:

GRAFANA_API_KEY="here-the-key" GRAFANA_HOST="here-the-host" DEPLOYMENT_ENV=bugb iex -S mix

Now the dashboard from buga are not there anymore:
Screenshot_2021-05-07 Dashboards Manage - Grafana(1)

@pallix pallix added the bug Something isn't working label May 7, 2021
@pallix
Copy link
Author

pallix commented May 18, 2021

@akoutmos did you get any chance to look at it?

@akoutmos
Copy link
Owner

I think I have come up with a solution to solve this problem without breaking backwards compatibility. Unfortunately I've been a bit swamped with work the past couple of weeks, and have this on the TODO list for next week.

@pallix
Copy link
Author

pallix commented May 19, 2021

Glad to hear that! I had a harddrive crash so stuffs got delayed on my side too :-)

@b1az
Copy link

b1az commented Oct 11, 2021

I think I have come up with a solution to solve this problem without breaking backwards compatibility. Unfortunately I've been a bit swamped with work the past couple of weeks, and have this on the TODO list for next week.

@akoutmos any chance you could publish this branch, even if in a WIP state? Maybe someone else will be able to take up the baton.

@herrnesto
Copy link

Same problem here. Looking forward to the fix :-)

@mwilsoncoding
Copy link

I am also running into this. Trying to leverage the same Grafana instance to view info on the same app, but in multiple environments. At the moment, we're looking at running a Grafana instance per environment. This is doable, but it would be nice to centralize if possible.

@pallix
Copy link
Author

pallix commented Sep 11, 2023

Trying to leverage the same Grafana instance to view info on the same app, but in multiple environments.

In the end I solve it differently: we now have only one dashboard type for each environment and we use the labels and drop down menu from the Grafana dashboard. Look for Grafana templating and labels if you are interested in such a solution.

@mwilsoncoding
Copy link

Ah- I see now. At least in GKE, this works when only one instance of the app deploys dashboards to the grafana instance. The dashboards are already able to toggle between the instances of the application through the configured dropdowns even with them existing on separate clusters.

@scudelletti
Copy link

It seems that this issue is related with #214 and there's a PR that could potentially handle it on #226.

@fbettag
Copy link
Contributor

fbettag commented Aug 8, 2024

happy to help :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

7 participants