3 ms·
You should read this - https://openobserve.ai/blog/openobserve-vs-grafana https://openobserve.ai/blog/openobserve-vs-grafana
by prabhatsharma 2y ago
You should read this - https://openobserve.ai/blog/openobserve-vs-grafana https://openobserve.ai/blog/openobserve-vs-grafana
- viraptor 2y agoThat's an interesting take for OpenObserve, but for me in an ops role it misses the compatibility. I appreciate that with Grafana I can choose a specific backend and configure it as required in my environment. I know other systems can reach the same database because they have known APIs. I also know I can move to another store with the same front-end if the owners pull an Elastic/Redis. OO integration may save me a couple of days of setup, but long-term it's a dangerously limiting idea / lock-in.
- prabhatsharma 2y agoYou are in the same danger with Grafana (Front end, Elasic/Redis fate and lock in) as you are with OpenObserve. No difference there.
- viraptor 2y agoThe risk is more spread out between the projects though so the replacements required would be smaller.