I suspect this is partially because internal efforts and agendas take priority over open source community at this point.
For example, I created an issue requesting a flamegraph visualization in grafana[1] and now it makes sense that they didn't initially respond because they were building it internally in secret and didn't want to spoil the big reveal (when they did respond they did mention that it was a secret).
They're also less incentivized now to tend to issues and PRs that help others outside of their ecosystem (i.e. competing logs, metrics, tracing, profiling, etc products).
>Sorry for this being a bit secret until now but we tried to quickly build and iterate something usable. There isn't much documentation for it as it is behind feature flag it's not a GA feature but hope that will come soon.
Secrets kinda conflict with the whole Open part of OSS.
>No it doesn’t. Open community doesn’t have to be open source. Open source doesn’t have to have an open community.
That's in direct contract with Grafana's own messaging. The following is from their OSS marketing page.
>Open Source is at the heart of what we do at Grafana Labs. We believe building software in the open, with thriving communities, helps leave the world a little better than we found it.
https://grafana.com/oss/
As I said, please stop conflating open source software with open communities. They’re part of a thriving and healthy project, but are not the same thing.
For example, I created an issue requesting a flamegraph visualization in grafana[1] and now it makes sense that they didn't initially respond because they were building it internally in secret and didn't want to spoil the big reveal (when they did respond they did mention that it was a secret).
They're also less incentivized now to tend to issues and PRs that help others outside of their ecosystem (i.e. competing logs, metrics, tracing, profiling, etc products).
[1] https://github.com/grafana/grafana/issues/53723