In episode 38 of o11ycast, Charity and Liz speak with Andy Davies of Reaktor. Their conversation covers the importance of instrumentation, the prevalence of structured logging, the potential risks of modifying database infrastructure.
Ep. #38, Infrastructure Changes with Andy Davies of Reaktor
Vendor Agnostic Instrumentation With The OpenTelemetry Collector
Achieving the best possible observability involves instrumenting your code with events and traces. This can be costly, and it's common for a large system to have components instrumented with different formats specific to different standards or vendors. Paul Osman walks through using the OpenTelemetry Collector to combine traces and metrics from services instrumented with different formats.
Observability Sheds Light on Dark’s Business Growth and Customer Scaling Needs
Dark’s engineering team relied on logs to understand how users interacted with their platform. But a desire for both deeper understandings of user behavior throughout the platform and a need for better visualizations drove the team away from Stackdriver and toward observability-driven development with the adoption of Honeycomb.
Fast and Simple: Observing Code Infra Deployment at Honeycomb
You don’t need Kubernetes to automatically push green builds to production – learn how Honeycomb has utilized CircleCI, Terraform, Chef, a collection of home-grown scripts, and Honeycomb itself to speed up its deployments and make them safer. We’ll talk about what went wrong along the way, and how we used our Service Level Objectives to evaluate and mitigate the risks.