3 ms·
Personally, I find local logs and tracing super useful. It allows you to debug tests and ensure you have right instrumentation to troubleshoot similar issues on
by jakozaur 5y ago
Personally, I find local logs and tracing super useful. It allows you to debug tests and ensure you have right instrumentation to troubleshoot similar issues on production. Design and write code that you can debug later.
E.g. we troubleshooted slow build times or analyse adoption of different internal tooling.
Minor nitpick, these days I would use OpenTelemetry for instrumentation instead of OpenCensus. Even on OpenCensus website (https://opencensus.io/ https://opencensus.io/) you can read "OpenCensus and OpenTracing have merged into OpenTelemetry!".
Disclaimer: I work at Sumo Logic (https://www.sumologic.com https://www.sumologic.com). We do logs, metrics and tracing.
- lawrjone 5y agoYou're totally right on the OC vs OT- we couldn't use OT when I first put this together, as the StackDriver plugin wasn't compatible. We also found it didn't work out-the-box with a load of our stuff (notably the GCP client libraries) while OC did. Another commenter has pointed out things have moved on quite a bit since then- that's really good to hear, and we'll revisit this when we get some time to make the shift :)
- wdb 5y agoWe have switched to Opentelemetry also using Google Trace with great success. I am really enjoying the Opentelemetry solution. Can't wait for metrics to be stable around Q1 of next year. The specs are frozen so it's all building the SDK/API libraries now. Tracing is also great to use as part of integration tests My main gripe with Cloud Trace is that its much harder to read than Jaeger.