Support multiple Grafana Instances

[satrox28]

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

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

[K-Phoen]

Hey,

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

Glad this little plugin can help!

[blakeromano-il]

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!

[K-Phoen]

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

[blakeromano-il]

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.

[iimnd]

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

[betorvs]

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.

[mrooding]

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

[chrissi517]

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

[Vity01]

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

[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.

[dweber019]

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...

[Vity01]

@dweber019 @mrooding @chrissi517
Here is my solution for this problem #76 , include updated documentation, config validation + my solution is backwards compatible.
I think it will be necessary to fork this project soon...

[dtemir]

+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 Is it possible to support jwt auth for embedding graphs? #74

@Vity01 what do you think?