Liz Fong-Jones

Nov 6, 2024 | honeycomb.io | Rox Williams |Jessica Kerr |Liz Fong-Jones |Mei Luo

In the software space, we spend a lot of time defining the terminology that describes our roles, implementations, and ways of working. These terms help us share fundamental concepts that improve our software and let us better manage our software solutions. To optimize your software solutions and help you implement system observability, this blog post will share the key differences between logs vs traces. Logs are time-stamped records generated by software applications, services, or network devices.

Oct 28, 2024 | honeycomb.io | Jessica Kerr |Liz Fong-Jones |Mei Luo |Rox Williams

Observability means you know what’s happening in your software systems, because they tell you. They tell you with telemetry: data emitted just for the people developing and operating the software. You already have telemetry–every log is a data point about something that happened. Structured logs or trace spans are even better, containing many pieces of data correlated in the same record. But you want to start from what you have, then improve it as you improve the software.

Oct 21, 2024 | honeycomb.io | Liz Fong-Jones |Mei Luo |Rox Williams

Let’s be real, we’ve never been huge fans of conventional unstructured logs at Honeycomb. From the very start, we’ve emitted from our own codestructured wide events and distributed traces with well-formed schemas. Fortunately (because it avoids reinventing the wheel) and unfortunately (because it doesn’t adhere to our standards for observability) for us, not all the software we run is written by us. And Kubernetes is a prime example of such a load-bearing part of our infrastructure.

Sep 20, 2024 | honeycomb.io | Rox Williams |Jessica Kerr |Liz Fong-Jones |Mei Luo

The best DevOps and SRE teams have shifted their approach to monitoring and logging their systems. These teams debug problems cohesively and rationally, regardless of the system’s complexity. Gone are the days of having a slew of logs that fail to explain the cause of alerts, system failures, and other unknowns. Implementing logging best practices is foundational for maintaining system integrity and performance in today’s complex IT environments.