backstage-plugin-grafana icon indicating copy to clipboard operation
backstage-plugin-grafana copied to clipboard

Published 20 hours ago • verified publisher icon K-Phoen

Support multiple Grafana Instances

Open satrox28 opened this issue 2 years ago • 13 comments

Hi, Thanks for the plugin, its awesome :).

Is there a way to configure multiple Grafana Instance on the app-config.yaml?.

satrox28 avatar Oct 20 '21 07:10 satrox28

Hey,

Nope, not at the moment. It's definitely a feature that I'm interested in though :)

Glad this little plugin can help!

K-Phoen avatar Nov 06 '21 00:11 K-Phoen

I am going to plus one this feature! 👍 We have several Grafana instances it would be great to have all of them available in Backstage!

blakeromano-il avatar Mar 02 '22 15:03 blakeromano-il

Any ideas/suggestions as to how you would like it to work?

K-Phoen avatar Mar 05 '22 22:03 K-Phoen

I would do something similar to the kubernetes plugin where the app-config.yaml supports an array of variables, then based when getting the dashboards for an entity in the catalog-info.yaml you could specify instance-name and if there isn't one in the annotation but there is a grafana/tag-selector you assume it is the first instance.

blakeromano-il avatar Mar 06 '22 00:03 blakeromano-il

hopefully this feature available soon, but thanks @K-Phoen , you're awesome

iimnd avatar Mar 15 '22 03:03 iimnd

thanks for this plugin @K-Phoen . Maybe a simple adjust similar to ArgoCD plugin and you just add multiples proxies and change kubernetes annotations. Just an idea.

betorvs avatar Mar 24 '22 16:03 betorvs

Hi @K-Phoen, this would be very useful. Can you use some help with the changes? Looking at your codebase, it should be quite trivial to extend but I'd like to hear what you had in mind in terms of the implementation

mrooding avatar Jul 06 '22 06:07 mrooding

For us it would be also very importent to have the support of multiple instances.

chrissi517 avatar Oct 13 '22 05:10 chrissi517

I am working on the PR solving this. Coming soon!

Vity01 avatar Jul 20 '23 08:07 Vity01

Since @K-Phoen does not respond at all, does it make a sense to fork this project completely? I also adopted several PRs and other ideas.

Vity01 avatar Jul 21 '23 11:07 Vity01

I currently downloaded the source and changed it to support this as we have a similar requirement. It's supported with multiple proxies like https://github.com/RoadieHQ/roadie-backstage-plugins/tree/main/plugins/frontend/backstage-plugin-prometheus.

Would be nice to see this here, as I think it's a awesome plugin. If there is no movement on this repo I have to probably open source my own version...

dweber019 avatar Sep 17 '23 17:09 dweber019

@dweber019 @mrooding @chrissi517 Here is my solution for this problem https://github.com/K-Phoen/backstage-plugin-grafana/pull/76 , include updated documentation, config validation + my solution is backwards compatible. I think it will be necessary to fork this project soon...

Vity01 avatar Sep 18 '23 07:09 Vity01

+1 this one. in my org, we have hundreds of Grafanas and setting up proxy for each of them is impossible.

We think the scalable solution should be:

  • Every Grafana should be registered as Resource entity in Backstage catalog with the appropriate link (we have a provider to fetch those from internal resource that spins up AWS ECS Grafanas for teams)
  • The Resource entity should be linked to System entity with dependsOn (this is how teams will say "Hey this is my Grafana")
  • The plugin should somehow use the currently logged in users Okta credentials to make API calls instead of Backstage maintainers keeping track of all the Service Tokens. This is partially brought up by #74

@Vity01 what do you think?

dtemir avatar Sep 21 '23 14:09 dtemir