4 ms·

Thanks for reading! Our goal was to create an out of the box solution that didn't require on-going maintenance. Another goal was to make something that all engi

Thanks for reading! Our goal was to create an out of the box solution that didn't require on-going maintenance. Another goal was to make something that all engineers on the team would know how to use. The amount of 1/2 broken prometheus/grafana setups we see is crazy. From a feature perspective there is some overlap (ex pod/node CPU and memory). But we have features that you can't get from the solutions you mentioned (ex service latency, latency by URL path (coming soon!). And have a lot more in the roadmap too. :) We are also housing and managing the data for our users.

sidcool 5y ago
Thanks for the reply. Is it available to self host? Or self manage in public cloud?
- NWMatherson 5y ago
  Currently no, not yet at least.
debarshri 5y ago
Half broken setup is a people problem. Prometheus and grafana is integrations is actually pretty solid and quite simple if you follow the docs [1]. If you are out there to replace existing monitoring stack like ELK, Prometheus-grafana, victoria metrics, i think it will be an uphill battle proving your value because there is high switching cost. Also, In most of the organisations, core resources that people care about are well monitored. Just my 2 cents. [1] https://grafana.com/grafana/plugins/grafana-kubernetes-app/ https://grafana.com/grafana/plugins/grafana-kubernetes-app/