zjh1315 / coroot Goto Github PK

Coroot is a monitoring and troubleshooting tool for microservice architectures.

Thanks to eBPF, Coroot shows you a comprehensive map of your services without any code changes.

The most popular L7 protocols are already supported:

• HTTP
• Postgres
• Mysql
• Mongodb
• Redis
• Memcached
• Cassandra
• Kafka

Coroot has predefined SLOs with universal thresholds for availability and latency, but you can easily adjust these thresholds for any app.

That's it! Configure the Slack integration, and you will be notified of any significant SLOs violation.

Node-agent turns terabytes of logs into just a few dozen metrics by extracting repeated patterns right on the node. Using these metrics allows you to quickly and cost-effectively find the errors relevant to a particular outage.

Coroot uses cloud metadata to show which regions and availability zones each application runs in. This is very important to known, because:

• Network latency between availability zones within the same region can be higher than within one particular zone.
• Data transfer between availability zones in the same region is paid, while data transfer within a zone is free.

Coroot makes troubleshooting Postgres-related issues easier not only for experienced DBAs but also for engineers not specialized in databases.

Coroot uses Prometheus as a Time-Series Database (TSDB):

• The agents are Prometheus-compatible exporters
• Coroot itself is a Prometheus client (like Grafana)

The built-in Prometheus cache allows Coroot to provide you with a blazing fast UI without overloading your Prometheus.

You can run Coroot as a Docker container or deploy it into any Kubernetes cluster. Check out the Installation guide.

The Coroot documentation is available at coroot.com/docs/coroot-community-edition.

A live demo of Coroot is available at community-demo.coroot.com

• Community Slack
• GitHub Discussions
• GitHub Issues
• Twitter: @coroot_com

Coroot is licensed under the Apache License, Version 2.0.