4 ms·
If you're just exposing your grafana instance, no - and probably not if you're iframing them or similar. If you're actually embedding grafana into your program
by lmm 6y ago
If you're just exposing your grafana instance, no - and probably not if you're iframing them or similar. If you're actually embedding grafana into your program then yes, but that would be a strange way to structure a system.
- lovasoa 6y agoYes, I was thinking about an iframe, but I don't think the technological details matter, do they? As long as grafana is a core part of your product, then your whole product has to be AGPL, according to the license...
- lmm 6y agoIf your product is integrated closely enough with grafana to constitute a derivative work under copyright law, yes. That's a complicated and murky area of law, but it's unlikely that just iframing in an otherwise separate webapp as a metrics page would be enough to trigger it. (Whereas if you integrate e.g. editing metrics and calling grafana's API to add them to a dashboard, at that point it seems far more likely your system would be considered a derivative of grafana - but at that point you really are implementing a grafana editor product (or at least a product that includes a grafana editor) rather than just using grafana to monitor a separate product).