Our great sponsors
-
Grafana
The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.
-
redpanda
Redpanda is a streaming data platform for developers. Kafka API compatible. 10x faster. No ZooKeeper. No JVM!
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Plugins don't seem to have been relicensed looking at https://github.com/grafana/grafana/blob/HEAD/LICENSING.md
"Amazon Announces Grafana Fork , Promises Amazing Things For the Community (2021/05/08)" [1]
On a more serious note: there is a bit of a trend in the licensing world. Mongo, ElasticSearch, cool new projects like redpanda [2] launching with BSL.
Open source is still a very young business model. One that has provided a tremendous amount of value over the past 1-2 decades, but we still need to figure out how to build sustainable business. Be it open core, more restrictive licenses, ...
[1] https://aws.amazon.com/grafana/
[2] https://github.com/vectorizedio/redpanda
This might be the case. However there is an additional risk and process component:
- you might not want to risk because you don't have lawyers etc in your company.
- even if you have lawyers etc in your company, if there are 2 alternatives one which is just an MIT license, you'll probably go for that one because you don't want to have a 1.5 month review of the use of this AGPL licensed alternative.
In general things like this https://github.com/xdspacelab/openvslam/wiki/Termination-of-... (repo with 3k stars), an effort terminated because of some traces of GPL code MIGHT be somewhere in there comes to light. Even though Grafana etc are mostly tools, for my startup I would probably not risk any of this (for my own sake and also for any kind of due diligence in case it ever gets acquired)
I fully support this statement. I'm core developer of open-source monitoring solution - VictoriaMetrics [1]. It is licensed under Apache 2 and we have no plans to change the license, since it may complicate user experience. VictoriaMetrics makes "value capture" by more future-proof means:
* By providing easy-to-setup-and-operate solution
* By focusing on the performance and minimal resource usage
* By providing good integration with other monitoring solutions
[1] https://github.com/VictoriaMetrics/VictoriaMetrics
> Why's that? If Kibana had been AGPL and Grafana had been AGPL from day 1, how would the growth and survival of Grafana have been any different?
Then Grafana would be forced to open all the source code for Grafana Cloud Dashboards [1] according to AGPL derived from Kibana. I don't think they would follow this path.
The same applies to Prometheus [2] source code, which is used by Grafana Cloud Metrics [3] (aka Cortex) developed by Grafana labs. If Prometheus had been licensed under AGPL, then Grafana labs would be forced to open all the derived source code for Grafana Cloud Metrics.
These examples prove that Apache 2 license is much better for users and for commercial companies compared to AGPL. That's why we at VictoriaMetrics stick with Apache 2 license and have no plans to change it.
[1] https://grafana.com/products/cloud/features/#cloud-dashboard...
[2] https://prometheus.io/
[3] https://grafana.com/products/cloud/features/#cloud-metrics
Related posts
- Is there a way to get performance statistics from my applications running on a k8s cluster?
- Tools for frontend monitoring with Prometheus
- Golang: out-of-box backpressure handling with gRPC, proven by a Grafana dashboard
- Monitoring, Observability, and Telemetry Explained
- Observability at KubeCon + CloudNativeCon Europe 2024 in Paris