[🔌 Provider]: new provider — Coroot integration

[gecube]

Summary

Proposal: implement a new Coroot provider for KeepHQ
👉 https://coroot.com/

Coroot is a modern open-source monitoring system that takes a service-level objective (SLO)-based approach, rather than the traditional metric/dashboard-driven model.
It focuses on actionable insights, automatic service discovery, and topology visualization instead of overwhelming users with countless metrics and charts.

---

💡 Why Coroot?

1. SLO-driven monitoring

Unlike Grafana/Prometheus-style systems, Coroot organizes telemetry around SLOs and incidents, making it conceptually closer to KeepHQ’s model of alerting and service topology.

2. Service inventory

Coroot automatically maintains an inventory of all services, their relationships, dependencies, and external connections.
This makes it an excellent potential data source for KeepHQ’s service topology.

3. Automatic topology discovery

Coroot can render a real network map of all inter-service communications using eBPF data collection.
This overlaps directly with KeepHQ’s topology feature.

4. eBPF-based metrics collection

Metric completeness and low overhead are achieved through eBPF agents, meaning it can operate without intrusive instrumentation.

5. Built-in integrations

Coroot already integrates with:

• multiple databases (PostgreSQL, MySQL, Redis, etc.)
• external exporters
• alert channels such as Slack, Telegram, and generic Webhooks

6. Self-contained & reliable

Coroot is a stateful application, storing data in ClickHouse and Prometheus (optionally replaceable with VictoriaMetrics).
This makes it independent, easy to integrate, and predictable in data schema.

---

🧩 Why it fits KeepHQ

Integrating Coroot as a provider would allow:

• Importing service topology data (apps, dependencies, external connections)
• Importing SLO status and incident states
• Potentially syncing alerts and service metadata
• Leveraging Coroot’s eBPF metrics as a foundation for more accurate topology and health insights in KeepHQ

---

✅ Proposed next steps

1. Explore Coroot’s API / data model to determine which endpoints expose:
   • service inventory
   • topology structure
   • alerting state
2. Define a Coroot provider type with appropriate authentication options.
3. Implement a simple read-only integration that fetches topology and service health data.
4. Optionally, map Coroot alerts → KeepHQ incidents.

---

🧠 Rationale

• Coroot and KeepHQ have complementary goals — both aim to make complex observability data more understandable.
• Integrating Coroot would dramatically enrich KeepHQ’s topology and incident layers.
• This could also attract a shared user base from the modern observability ecosystem.

---

Labels: type:enhancement area:providers priority:medium proposal:new-provider