-
Notifications
You must be signed in to change notification settings - Fork 20
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
Allow user to provide their own Grafana instance #347
Comments
Hi, is this something you are planning to work on soon? For example for 2.3 release? It would be nice if collected data can be published to external Grafana instance - for example to Grafana Cloud and then just link to such instance from cryostat UI. |
Hi @petr-postulka, sorry for the late response. I can't say for sure if we can prioritize this for 2.3, but I'll ensure we discuss it when planning our tasks for 2.3 in a couple weeks. |
hi @ebaron, thank you for the reply ... I see that 2.3 works already started, was this feature discussed and is there any chance to be included into the release? |
Hi all, we did discuss this feature yesterday during our planning meeting for 2.3. We decided to prioritize work on multi-namespace support https://github.com/cryostatio/cryostat/issues/760, which will require substantial changes both in Cryostat and the operator. We do see the value in supporting existing Grafana instances, but one difficulty is that we would want to ensure that it's easy for users to install our customized dashboard and datasource configurations into their Grafana instance. I think this would take the form of a Grafana plugin. This is something we want to do, but we may not have the available cycles to deliver it for 2.3. |
hi, any update on this item ? |
No real updates at this point. I think we would need to tackle these two issues first before we can do anything meaningful here: |
It would be useful to have the option to integrate with an existing Grafana pod. The user would have to ensure that the datasource and Cryostat Dashboard are installed. Perhaps this can be improved by making our customizations into a Grafana plugin. Since this would involve datasource traffic leaving the pod, we'd have to set up TLS for the datasource container as well.
The text was updated successfully, but these errors were encountered: