3 ms·
They say: > if you want to have a seamless experience between metrics and traces, then current experience of stitching together Prometheus & Jaeger is not grea
by codetrotter 4y ago
They say:
> if you want to have a seamless experience between metrics and traces, then current experience of stitching together Prometheus & Jaeger is not great.
But I wonder if using Promscale https://github.com/timescale/promscale https://github.com/timescale/promscale would make Prometheus & Jaeger not such a big problem as SigNoz imply.
Promscale readme:
> Promscale is a unified metric and trace observability backend for Prometheus, Jaeger and OpenTelemetry built on PostgreSQL and TimescaleDB.
Either way, SigNoz seems interesting indeed. And am glad to see that SigNoz supports OpenTelemetry.
- pranay01 4y agoyeah, promscale is an interesting project with similar goal - trying to bring together different signals ( only metrics & traces for promscale) under one hood. I have not explored the project in detail, but as far as I understand it uses Grafana and Jaeger UI, so I am not sure how seamless is the UI interaction, while SigNoz has a UI built ground up for observability use cases.
- 0x457 4y agoYou don't even need Promscale for this. Grafana has support for displaying information from both plus logs. As long as log messages include TraceID is straightforward use Grafana for debugging.
- ankitnayan 4y agoBasically, the choice of DB is different, relational vs analytical DB. IMO clickhouse should be better at ingestion rate and aggregation queries.