3 ms·
It's a really nice solution. I am using it to send traces and metrics via a standardised API in Go, and Node.js. During development I am sending without samplin
by wdb 5y ago
It's a really nice solution. I am using it to send traces and metrics via a standardised API in Go, and Node.js. During development I am sending without sampling it to Jaeger but in production I am sending ratio sampled traces to Google Trace but you can use Honeycomb or Lightstep. For metrics, I am sending them to local Prometheus during development, and cluster prometheus in production.
It's nice to see all the traces through all the different services of one API request and all its log items it generated. Using a custom span exporter to ensure PPI is stripped away as much as possible for span attributes.
Using W3C trace context and baggage to send some more data along, e.g. sending the trace id, span id etc into pub sub events to ensure to connect them with the trace.
Loving it! For now, I think it's worth the costs of adding tracing to services.