Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> combine traces from frontend and backend

I'm scratching my head a little bit on what your expectation is here. Traces and real-user-monitoring are not the same thing here. Distributed tracing is specifically a microservices thing. Maybe all you're looking for is to just attach a UUID to each request and log it? Jaeger and Tempo aren't going to help you with frontend code.

> A lot of infrastructure

> Prometheus

You need something to tell you when your tiny app isn't running, so it can't be a library embedded into the app itself.

> Grafana

You need something with dashboards to help you understand what's going on. If your thing telling you your app has crashed is outside your app, the thing that helps visualize what happened before your app crashed also needs to be outside your app.

> Jaeger

Do you really need traces? Or just to log how long request times took, and have metrics for p50/p95/p99?

> Loki

If you're running only one instance of your app, you don't need it, just read through your logfiles with hl. If you have multiple machines, sending your logs to one place may not be necessary, but it's incredibly helpful; the alternative is basically ssh multiplexing...



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: