Ep. 3 See The Trace? Discover Errors, Latency & More across Distributed Systems
Distributed systems bring complexity for developer and ops teams. When incidents occur in production, expected and unexpected, you want to pinpoint which part of the service is giving problems. Distributed tracing illuminates distributed systems, making your logs easier to navigate. Quickly identify where there are errors or latency in your code or service, even within 3rd party services you use. Instrumentation is the key to the best tracing experience possible.
We will dive into the importance of tracing when debugging, and show how Honeycomb Beelines fast-track instrumenting code. You will learn:
* The importance of tracing when debugging production along with other types of analysis
* how to debug by analyzing patterns and trends in the data generated by traces
* how to work with OpenCensus or OpenTracing (yes you can with Honeycomb).
Join this exciting session and discover the value of tracing. Spoiler: it's easier than you may think.
RecordedMay 7 202060 mins
Your place is confirmed, we'll send you email reminders
Rachel "pie" Perkins, Honeycomb Wordsmith/Content, CJ Silverio, Eaze Principal Engineer, & Ben Gardella, Eaze Manager of Infr
On-call teams use Honeycomb’s analytics to discover exactly what is happening with code in production. While incident response is a key reason engineers rely on Honeycomb, observability also delivers unique value during the development process. Eaze takes observability a step further and uses Honeycomb to prioritize what’s needed to stabilize their existing service while informing how they build their new Go and Node.js microservices platform all at the same time.
Honeycomb can help you find the needles in your haystack. But it helps when you make the needles more findable! Beyond automatic instrumentation, adding custom telemetry to your events means thinking about how that data will be used when you and your team don’t even know what it is they’re looking for. How can you make the telemetry you’re adding today useful in an unpredictable future?
In this episode, we chat about how Honeycomb approaches considerations when adding instrumentation as we develop new code. Our Principal Developer Advocate and contributing software engineer covers how telemetry for Honeycomb’s SLO feature was developed in preparation for its release to production. We’ll show real examples of the telemetry we use in production, look at how different bits of telemetry code are represented in the Honeycomb UI, and talk about what considerations you can use to decide which bits of context to capture in our events. Thanks, past self!
See some of the powerful features that make Honeycomb the fastest way to visualize, understand and continuously debug software — all while freeing up Engineering and DevOps time. Check out our product demo.
Irving Popovetsky, Dir | Customer Engineering; Kelly C. Gallamore Demand Gen | Host
You’ve put in the time. You’ve done the work. You’ve instrumented your apps and learned how to use powerful Honeycomb features to start unlocking your observability superpowers. But what if you’re the only one playing on Team Observability? How can you share those same superpowers with the rest of your team? After that, how can you spread those to the rest of your org?
In this episode, we chat about how Honeycomb helps its customers onboard their teams. Our Director of Customer Engineering covers several approaches and tips to help you lower onboarding friction for new users while pouring fuel on the wow factor. We cover ways to give your teams a place to start, bring external system context into Honeycomb, run experiments with Service Level Objectives (SLOs), and other useful tips based on common trends we hear from our customers.
Writing software and operating it in production is a team sport. Join us to learn how Honeycomb helps customers get the whole team in the game.
CEO, Founder Erwin van der Koogh|Linc; Charity Majors; Shelby Spees
In episode 23 of O11ycast, Charity and Shelby speak with Erwin van der Koogh of Linc. They discuss the startup ecosystem in Australia, release engineering, and the relationship between safety and success.
Follow along as SRE leaders from Slack, Fastly, Catchpoint, and Autodesk discuss defining SRE, avoiding pitfalls, managing incident anxiety, informing the C-Suite, information silo-ing, managing 'at-home' distractions, and starting a career in SRE.
Chief Architect Jimmy Bogard|Headspring; Charity Majors; Liz Fong-Jones
In episode 22 of O11ycast, Liz and Charity speak with Jimmy Bogard of Headspring. They discuss maintaining balance for on-call engineers, what’s missing in the average engineer’s toolkit, and moving from monoliths to microservices.
Understand what happens as soon as you do a code push until long after your code lands in production. Observability is looking into your code as it runs in production, and understanding the impact of your changes in real-time. With the right understanding, you make informed decisions, spending less time fixing, and more time improving.
Taming the complex distributed systems we're responsible for requires changing not just the tools and technical approaches we use; it also requires changing who is involved in production, how they collaborate, and how we measure success.
In this talk, you'll learn about several practices core to production excellence: giving everyone a stake in production, collaborating to ensure observability, measuring with Service Level Objectives, and prioritizing improvements using risk analysis.
Pierre Tessier, Sales Engineer; Kelly C. Gallamore, Host
Do you know exactly what your builds are doing at every step of the way to prod and after they’ve been deployed? How do you identify changes that impact your build time? How do you verify your build did everything you expected? Successful CI/CD asks demanding questions and with observability, you can answer them!
In this episode, we chat about how Honeycomb uses Honeycomb to build better builds. We cover watching build pipelines with traces, using BubbleUp to find performance impacts/identify optimizations, and using markers with queries to verify deployment behavior.
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. In this session, I'll walk through using the OpenTelemetry Collector to combine traces and metrics from services instrumented with different formats. Use cases covered: * Interoperability between OpenTracing, OpenCensus, and other formats.
• Using processors to modify spans
• Migrating from one tracing solution to another without rewriting code
• Sending traces to two separate backends
DevOps teams: what is observability and how do you get started
Honeycomb Learn is a webcast series designed to educate DevOps teams about what observability is and how to get started. Observability-driven development is the ability to ask any question about your production systems so you better understand and debug when incidents occur. Teams ship code confidently, learn continuously, and spend more time innovating.
Ep. 3 See The Trace? Discover Errors, Latency & More across Distributed SystemsMolly Stamos, Customer Success Engineer and Ben Hartshorne, Senior Engineer[[ webcastStartDate * 1000 | amDateFormat: 'MMM D YYYY h:mm a' ]]60 mins