Customer.ioAutomate Messaging Everywhere — Startups Get 12 Months Free
Promoted
Cerberus
Keep Grafana®. Swap the backend.
10 followers
Keep Grafana®. Swap the backend.
10 followers
Drop-in Prometheus / Loki / Tempo HTTP gateway for ClickHouse. Keep Grafana, alerting, and your CLI tooling. Swap the backend.
Love that this lets me swap the backend without touching Grafana or my alert rules. One thing that would help me actually roll this out: a small migration tool or CLI that ingests an existing Prometheus config and outputs the equivalent ClickHouse schema and sample queries, so I can sanity check what changes before flipping traffic.
@rzeliha54971 That's an amazing feature, it definitely earns a spot on the roadmap! Thanks for sharing!
@rzeliha54971 I've finally published a tooling that should help with migration. I do not have a better way to test it aside from synthetic tests on CI https://github.com/tsouza/cerberus/blob/main/docs/migration.md . If you face any issue please feel free to open an issue in github.
Replacing a backend without forcing teams to rebuild dashboards sounds valuable. What kinds of migrations have been the smoothest so far, and which have surprised you?
@aryan787544 Indeed a migration tool seems a quite compelling idea. I am designing one. Feel free to open a feature request at the project's github repo!
@tcostasouza That could remove a lot of migration friction if it's done well. I'm curious—do you see it eventually becoming a one-click migration, or more of an assistant that helps teams migrate incrementally while validating compatibility?
@aryan787544 I do not want to lean over too much on the actual migration procedure, because this is not a problem I have so it's difficult for me to design something end-to-end. What I am building right now are the low-level building blocks of it so teams can build their our migration path.
@tcostasouza That's an interesting distinction. It sounds like you're optimizing for flexibility over automation.
The question I'd keep coming back to is whether customers ultimately buy Cerberus because it replaces a backend, or because it gives them confidence to change infrastructure without breaking everything. Those can lead to very different positioning over time.
finally a way to ditch our custom clickhouse exporter setup without touching grafana. swapping in cerberus for loki queries was painless, and the prometheus endpoint just worked on the first try.
@erayrodoplu Thanks for the valuable feedback!