Software Engineering   Observability   Logging  

The Path from Unstructured Logs to Observability

By Rachel Perkins  |   Last modified on September 12, 2019

Are you starting out on your journey toward observability? Do you have a mandate from management, or are you a lone warrior in the matrix? From your starting point, how will you make the right decisions about how to implement changes to your logging and aim for the right path through the various choices in front of you?

screenshot from the Matrix movie

A map can help: The Path from Unstructured Logs to Observability offers concrete guidance on how to get started and where you should think about heading.

Whether you're ready to pick your first logging library or are thinking about tracing, Honeycomb is here to help you on your path to observability.

Download The Path from Unstructured Logs to Observability and make the future a better, more observable one :).

 

 

 

 

 

 

Related Posts

Software Engineering   Culture  

The CoPE and Other Teams, Part 1: Introduction & Auto-Instrumentation

The CoPE is made to affect, meaning change, how things work. The disruption it produces is a feature, not a bug. That disruption pushes things...

Software Engineering   Dogfooding  

Destroy on Friday: The Big Day 🧨 A Chaos Engineering Experiment - Part 2 

In my last blog post, I explained why we decided to destroy one third of our infrastructure in production just to see what would happen....

Teams & Collaboration   Software Engineering   Culture  

What Makes for a 'Good' Pair Programming Session?

Software changes so rapidly that developing on the cutting edge of it cannot fall to a single person. When it comes to asynchronously disseminating information...