Apache Kylin vs. Grafana

Just about any organization with more than one server and more than one cluster as it scales very well. Configuration of the application takes time and finesse to fine tune to where the balance of load time and getting data quickly meets. The plugins add load time but fine tuning for the application to meet demand needs nailed down at implementation

Incentivized

• Alerting through many different medium as Slack, Email, Webhook etc
• Beautiful and unlimited number of dashboards to view your metrics and tweak them as you please
• Log aggregation and powerful Logql to filter and view your logs
• Microservices monitoring
• Large number of plugins and data sources to collect your metrics from almost anywhere

Incentivized

• Documentation needs to be more clarified since it can be confusing for beginners
• Notification alert message templates need to be simplified

Incentivized

Great usage in terms of monitoring of any application from backend to frontend and even any AWS resource via cloud watch and other connectors. Easy to use and configure personalised dash boarding and alerting features. Cost efficient and easy to setup and run, no mazor scaling challenges in terms of managing and maintaining the stack, easy to configure via Prometheus, influx and other connectors

Incentivized

Grafana is more flexible, readily adopts other tools frameworks instead of forcing you to use their agent, doesn't force you into Vendor lock-in, and embraces open source, self-hosted, and Enterprise. Similar companies would like you to use their specific tooling and don't offer nearly as much flexibility. The other thing I like about Grafana is their storage usage is much lower compared to similar tools and competitors

Incentivized

• It has kicked out some of our paid monitoring and visualization tools.
• Now Monitoring, Visualization and Alerting is being done in a single platform.
• It made monitoring and visualization very easy for us.