4 ms·

"We found that though there are many backend products - an open source product with UI custom-built for observability, which integrates metrics & traces, was mi

• spech 6y ago
  +1 for Grafana together with Loki and Prometheus. This saved us so much trouble. We thought about using DD first but the costs were so intransparent.
  • pranay01 6y ago
    Curious, do you use self-host Prom+Loki?
    • technics256 6y ago
      I do it with my clients, but we're not using a lot of clusters.
  • wdb 6y ago
    Grafana Tempo for the traces looks interesting too! Especially now that it doesn't require Elastic anymore
• ankitnayan 6y ago
  Grafana, for long, has been used to monitor time-series data and recently has been moving towards observability (including traces and logs). We are different in quite a few fronts. 1. There are specific observabilty specific UI widgets like serviceMap, SLOs and error budgets, I don't know whether Grafana provides it now. Also, last I used Grafana, linking and moving from one dashboard to another is still a pain. You can get a better idea of how different observability UI can get from Grafana by looking into LightStep demo. 2. We can run aggregated on filtered traces. Eg, I can get 99th percentile response time of a tag say payment_channel. am afraid this can be extracted from traces by Grafana. 3. SigNoz is easily extendible by adding your stream processing application to slice n dice data in your own way