Podcast appearances and mentions of christine yen

Observability is expensive because traditional tools weren't designed for the complexity and scale of modern cloud-native systems, explains Christine Yen, CEO of Honeycomb.io. Logging tools, while flexible, were optimized for manual, human-scale data reading. This approach struggles with the massive scale of today's software, making logging slow and resource-intensive. Monitoring tools, with their dashboards and metrics, prioritized speed over flexibility, which doesn't align with the dynamic nature of containerized microservices. Similarly, traditional APM tools relied on “magical” setups tailored for consistent application environments like Rails, but they falter in modern polyglot infrastructures with diverse frameworks.Additionally, observability costs are rising due to evolving demands from DevOps, platform engineering, and site reliability engineering (SRE). Practices like service-level objectives (SLOs) emphasize end-user experience, pushing teams to track meaningful metrics. However, outdated observability tools often hinder this, forcing teams to cut back on crucial data. Yen highlights the potential of AI and innovations like OpenTelemetry to address these challenges.Learn more from The New Stack about the latest trends in observability:Honeycomb.io's Austin Parker: OpenTelemetry In-DepthObservability in 2025: OpenTelemetry and AI to Fill In GapsObservability and AI: New Connections at KubeConJoin our community of newsletter subscribers to stay on top of the news and at the top of your game. 

Christine Yen, CEO of Honeycomb.io, joins Dash0's Mirko Novakovic to discuss the code red moment that inspired Honeycomb, the importance and coining of the term "high cardinality data", how the modern understanding of observability was formed, and more.

In this episode of The Confident Commit, Rob sits down with Christine Yen, CEO of Honeycomb, to delve into the evolving role of observability in modern software development. They discuss how observability goes beyond traditional metrics and monitoring, and allows developers to be better prepared for the unknown and embrace the complexities of distributed systems. Christine shares insights on how observability not only boosts developer confidence but also enhances productivity by reducing toil and enabling teams to focus on delivering value for customers.The conversation shifts to the value of Service Level Objectives (SLOs) and why discussions around them often focus heavily on measurement tools and technical implementations. Christine offers valuable advice on steering these conversations towards healthier, more customer-centric perspectives. By reframing the conversation, developers and teams can focus on delivering real value, aligning technical goals with customer needs and driving meaningful outcomes.Have a guest you'd like to hear on the podcast? Reach out to us on X at @CircleCI!

OpenTelemetry is an open-source observability framework for collecting and managing telemetry data. OpenTelemetry has been more successful than expected, becoming the second fastest growing project in the CNCF. It allows for flexibility and avoids vendor lock-in, making it attractive to startups and large enterprises alike. On today's show, Eric (@ericmander) sits down with Austin Parker (@austinlparker), director of open-source at Honeycomb. Contributor is looking for a community manager! If you want to know more, shoot us an email at eric@scalevp.com. Subscribe to Contributor on Substack for email notifications! In this episode we discuss: How Austin's interest in complex systems led him to the observability field and developer relations An X argument that contributed to the merger of OpenTelemetry and OpenCensus Why foundations help maintainers to strike a balance with their contributors Austin's opinion on the secret to OpenTelemetry's success Links: OpenTelemetry Honeycomb People mentioned: Charity Majors (@mipsytipsy) Christine Yen (@cyen)

Christine Yen is not like other CEO's. She's an engineer, that co-founded a company that has gone onto become, not just a leader in an industry, but also a company that defined the industry category - Observability. I have watched and admired the rise of Honeycomb from a very close vantage point. Formerly in my role at Dynatrace, who is also a leader in this observability space, I saw them quietly go about their business, without really ruffling any feathers. The Datadog's, New Relic's, Appdynamics, and Dynatracers of the world would end up in head to head battles. We'd be quick to jibe back about each other's capabilities but Honeycomb seemed to be walking to the beat of it's own drum. It fascinated me to the point that I really wanted to know more. In this podcast, I had a long sit down, with Christine Yen, the companies co-founder and CEO. We talked about the companies origin and original idea, early success, through the challenges with Go To Market, and being a female tech leader. Enjoy. I certainly did.

The first of two shows (the second will drop on Tuesday) featuring the views of speakers and leaders at Collision Conference in Toronto. Today we're meeting VoxNeuro's James Connolly, who is creating an objective system for measuring the health of your brain. Then as we tackle an increasingly complex world we meet Christine Yen, CEO of Honeycomb.io, who talks to us about the virtues of observability. Whilst there was a huge amount of Gen AI chatter at the show, and a focus on the challenges we face, it was clear that talking and sharing ideas can only help. We need to work together.

Applying and Maximizing Observability In this episode, Christine talks about her company, Honeycomb which runs on AWS, with the goal of promoting observability for clients interested in the performance of their code or those trying to identify problem areas that need to be corrected. Christine Yen is the Co-Founder and CEO of Honeycomb. Before founding Honeycomb, she built analytics products at Parse/Facebook and loved writing software to separate signals from noise. Christine delights in being a developer in a room full of ops folks. Outside of work, Christine is kept busy by her two dogs and wants your sci-fi & fantasy book recommendations. Notes Honeycomb is an observability platform that helps customers understand why their code is behaving differently from what they expected. The inspiration behind this software came after Christine's previous company was acquired by Facebook and they realized how software made it very easy to identify problems in large code data within a short time. This encouraged them to build the tool and make it available to all engineers. If the first wave of DevOps was Ops-people learning how to automate their working code, the second wave would be helping developers learn to operate their code. Honeycomb is designed intentionally to ensure that all types of engineers can make sense of the tool. Honeycomb has always come up with ways for customers to use AWS products and get the data reflected in Honeycomb to be manipulated. Over the last few months, they have ensured that it is possible for clients to plug into CloudWatch Log and CloudWatch metrics, and redirect data directly from AWS products into Honeycomb instead. Clients can also use Honeycomb to extract data based on what their applications are doing. This applies to performance optimization, experimentation, or any situation where a company wants to try a code to see how it performs on production. The focus remains on the application layer. Before Honeycomb, no one was using observability in this context. The pricing of Honeycomb is based on the volume of data, which makes it predictable and understandable. Unlike when the pricing scale is based on the fidelity of the data, which can be quite expensive. Challenges within the observability space: The question is how to help new engineers learn from the seasoned engineers on the team through paper trails left by the seasoned engineers. This is a problem that can only be solved by enabling teams to orient new engineers on their systems without having to create another question as part of the code. Building an AI Approach in Honeycomb may not be suitable because of the context involved, since training effective machine learning models relies on a vast amount of easily classifiable data and this does not apply in the world of software; every engineering team's systems are different from every other engineering team's systems. Honeycomb is interested in using Al to build these models in order to help users know what questions to ask. With Honeycomb, usage patterns are much more dependent on the curiosity and proficiency of the engineering team; while some engineers who are used to getting answers directly may just leave the software, those who have a culture of asking questions will benefit more from it. Top Quotes

Applying and Maximizing Observability In this episode, Christine talks about her company, Honeycomb which runs on AWS, with the goal of promoting observability for clients interested in the performance of their code or those trying to identify problem areas that need to be corrected. Christine Yen is the Co-Founder and CEO of Honeycomb. Before founding Honeycomb, she built analytics products at Parse/Facebook and loved writing software to separate signals from noise. Christine delights in being a developer in a room full of ops folks. Outside of work, Christine is kept busy by her two dogs and wants your sci-fi & fantasy book recommendations. Notes Honeycomb is an observability platform that helps customers understand why their code is behaving differently from what they expected. The inspiration behind this software came after Christine's previous company was acquired by Facebook and they realized how software made it very easy to identify problems in large code data within a short time. This encouraged them to build the tool and make it available to all engineers. If the first wave of DevOps was Ops-people learning how to automate their working code, the second wave would be helping developers learn to operate their code. Honeycomb is designed intentionally to ensure that all types of engineers can make sense of the tool. Honeycomb has always come up with ways for customers to use AWS products and get the data reflected in Honeycomb to be manipulated. Over the last few months, they have ensured that it is possible for clients to plug into CloudWatch Log and CloudWatch metrics, and redirect data directly from AWS products into Honeycomb instead. Clients can also use Honeycomb to extract data based on what their applications are doing. This applies to performance optimization, experimentation, or any situation where a company wants to try a code to see how it performs on production. The focus remains on the application layer. Before Honeycomb, no one was using observability in this context. The pricing of Honeycomb is based on the volume of data, which makes it predictable and understandable. Unlike when the pricing scale is based on the fidelity of the data, which can be quite expensive. Challenges within the observability space: The question is how to help new engineers learn from the seasoned engineers on the team through paper trails left by the seasoned engineers. This is a problem that can only be solved by enabling teams to orient new engineers on their systems without having to create another question as part of the code. Building an AI Approach in Honeycomb may not be suitable because of the context involved, since training effective machine learning models relies on a vast amount of easily classifiable data and this does not apply in the world of software; every engineering team's systems are different from every other engineering team's systems. Honeycomb is interested in using Al to build these models in order to help users know what questions to ask. With Honeycomb, usage patterns are much more dependent on the curiosity and proficiency of the engineering team; while some engineers who are used to getting answers directly may just leave the software, those who have a culture of asking questions will benefit more from it. Top Quotes

In the early 2000s, Charity Majors was a homeschooled kid who'd gotten a scholarship to study classical piano performance at the University of Idaho. “I realized, over the course of that first year, that music majors tended to still be hanging around the music department in their 30s and 40s,” she said. “And nobody really had very much money, and they were all doing it for the love of the game. And I was just like, I don't want to be poor for the rest of my life.” Fortunately, she said, it was pretty easy at that time to jump into the much more lucrative tech world. “It was buzzing, they were willing to take anyone who knew what Unix was,” she said of her first tech job, running computer systems for the university. Eventually, she dropped out of college, she said, “made my way to Silicon Valley, and I've been here ever since.” Majors, co-founder and chief technology officer of the six-year-old Honeycomb.io, an observability platform company, told her story for The New Stack's podcast series, The Tech Founder Odyssey, which spotlights the personal journeys of some of the most interesting technical startup creators in the cloud native industry. It's been a busy year for her and the company she co-founded with Christine Yen, a colleague from Parse, a mobile application development company that was bought by Facebook. In May, O'Reilly published “Observability Engineering,” which Majors co-wrote with George Miranda and Liz Fong-Jones. In June, Gartner named Honeycomb.io as a Leader in the Magic Quadrant for Application Performance Monitoring and Observability. Thus far Honeycomb.io, now employing about 200 people, has raised just under $97 million, including a $50 million Series C funding round it closed in October, led by Insight Partners (which owns The New Stack). This Tech Founder Odyssey conversation was co-hosted by Colleen Coll and Heather Joslyn of TNS. ‘Rage-Driven Development' Honeycomb.io grew from efforts at Parse to solve a stubborn observability problem: systems crashed frequently, and rarely for the same reasons each time. “We invested a lot in the last generation of monitoring technology, we had all these dashboards, we have all these graphs,” Majors said. “But in order to figure out what's going on, you kind of had to know in advance what was going to break.” Once Parse was acquired by Facebook, Majors, Yen and their teams began piping data into a Facebook tool called Scuba, which ”was aggressively hostile to users,” she recalled. But, “it did one thing really well, which is let you slice and dice in real time on dimensions that have very high cardinality,” meaning those that contain lots of unique terms. This set it apart from the then-current monitoring technologies, which were built around assessing low cardinality dimensions. Scuba allowed Majors' organization to gain more control over its reliability problem. And it got her and Yen thinking about how a platform tool that could analyze high cardinality data about system health in real time. “Everything is a high cardinality dimension now,” Majors said. “And [with] the old generation of tools, you hit a wall really fast and really hard.” And so, Honeycomb.io was created to build that platform. “My entire career has been rage-driven development,” she said. “Like: sounds cool, I'm gonna go play with that. This isn't working — I'm gonna go fix it from anger.” A Reluctant CEO Yen now holds the CEO role at Honeycomb.io, but Majors wound up with the job for roughly the first half of the company's life. Did Majors like being the boss? “Hated it,” she said. “Constitutionally what you want in a CEO is someone who is reliable, predictable, dependable, someone who doesn't mind showing up every Tuesday at 10:30 to talk to the same people. “I am not structured. I really chafe against that stuff.” However, she acknowledged, she may have been the right leader in the startup's beginning: “It was a state of chaos, like we didn't think we were going to survive. And that's where I thrive.” Fortunately, in Honeycomb.io's early days, raising money wasn't a huge challenge, due to its founders' background at Facebook. “There were people who were coming to us, like, do you want $2 million for a seed thing? Which is good, because I've seen the slides that we put together, and they are laughable. If I had seen those slides as an investor, I would have run the other way.” The “pedigree” conferred on her by investors due to her association with Facebook didn't sit comfortably with her. “I really hated it,” she said. “Because I did not learn to be a better engineer at Facebook. And part of me kind of wanted to just reject it. But I also felt this like responsibility on behalf of all dropouts, and queer women everywhere, to take the money and do something with it. So that worked out.” Majors, a frequent speaker at tech conferences, has established herself as a thought leader in not only observability but also engineering management. For other women, people of color, or people in the tech field with an unconventional story, she advised “investing a little bit in your public speaking skills, and making yourself a bit of a profile. Being externally known for what you do is really helpful because it counterbalances the default assumptions that you're not technical or that you're not as good.” She added, “if someone can Google your name plus a technology, and something comes up, you're assumed to be an expert. And I think that that really works to people's advantage.“ Majors had a lot more to say about how her outsider perspective has shaped the way she approaches hiring, leadership and scaling up her organization. Check out this latest episode of the Tech Founder Odyssey.

This week Adam is joined by Christine Yen, co-founder and CEO of Honeycomb. Christine and Adam recorded this show late last year, just after their Series C funding round. They talk about the superpower of observability for developers, how she and Charity Majors got to the place to found Honeycomb, the state of their platform today, what exactly observability is, and their goals for the future of Honeycomb.

This week Adam is joined by Christine Yen, co-founder and CEO of Honeycomb. Christine and Adam recorded this show late last year, just after their Series C funding round. They talk about the superpower of observability for developers, how she and Charity Majors got to the place to found Honeycomb, the state of their platform today, what exactly observability is, and their goals for the future of Honeycomb.

It does not matter if it runs on your machine.  Your code must run in the production environment and it must do so performantly.  For that, you need tooling to better understand your application's behavior under different circumstances.  In the earliest days of software development, all we had were logs, which are still around and The post Observability Using Honeycomb.io with Christine Yen appeared first on Software Engineering Daily.

It does not matter if it runs on your machine.  Your code must run in the production environment and it must do so performantly.  For that, you need tooling to better understand your application’s behavior under different circumstances.  In the earliest days of software development, all we had were logs, which are still around and

It does not matter if it runs on your machine.  Your code must run in the production environment and it must do so performantly.  For that, you need tooling to better understand your application’s behavior under different circumstances.  In the earliest days of software development, all we had were logs, which are still around and The post Observability Using Honeycomb.io with Christine Yen appeared first on Software Engineering Daily.

It does not matter if it runs on your machine.  Your code must run in the production environment and it must do so performantly.  For that, you need tooling to better understand your application’s behavior under different circumstances.  In the earliest days of software development, all we had were logs, which are still around and The post Observability Using Honeycomb.io with Christine Yen appeared first on Software Engineering Daily.

Christine Yen joins host Brian Dawson on the latest episode of DevOps Radio to share her journey from engineer to co-founder and CEO of Honeycomb and why observability is so important in today’s software development. 

Welcome to The New Stack Context, a podcast where we discuss the latest news and perspectives in the world of cloud native computing. For this week's episode, we spoke with Christine Yen, CEO of Honeycomb.io, the observability platform vendor, about the company's pricing changes brought on by COVID-19 and more broadly how observability practices and tools are changing as more companies make the move to the cloud. TNS editorial and marketing director Libby Clark hosted this episode, alongside TNS senior editor Richard MacManus, and TNS managing editor Joab Jackson. Honeycomb this week changed its pricing structure to reflect the cost realities for businesses and the long term effect of COVID-19. The company also recently released the results of a survey that shows half of the developers surveyed aren't using observability currently, but 75% plan to do so in the next two years. And in April the company released an open source collector for OpenTracing that allows teams to import telemetry data from open source projects into any observability platform, including their own but also their competitors. Yen said of the pricing changes: Our old pricing was, you bought a certain amount of storage and gigabytes and paid for a certain amount of data ingest, also in gigabytes, over a period of time. We felt like that was a little bit harder for people to map to their existing workflows, harder for them to predict. So we shifted to an events-per-month ingest model, one axis, one way to scale your usage.

Welcome to The New Stack Context, a podcast where we discuss the latest news and perspectives in the world of cloud native computing. For this week's episode, we spoke with Christine Yen, CEO of Honeycomb.io, the observability platform vendor, about the company's pricing changes brought on by COVID-19 and more broadly how observability practices and tools are changing as more companies make the move to the cloud. TNS editorial and marketing director Libby Clark hosted this episode, alongside TNS senior editor Richard MacManus, and TNS managing editor Joab Jackson. Honeycomb this week changed its pricing structure to reflect the cost realities for businesses and the long term effect of COVID-19. The company also recently released the results of a survey that shows half of the developers surveyed aren't using observability currently, but 75% plan to do so in the next two years. And in April the company released an open source collector for OpenTracing that allows teams to import telemetry data from open source projects into any observability platform, including their own but also their competitors. Yen said of the pricing changes: Our old pricing was, you bought a certain amount of storage and gigabytes and paid for a certain amount of data ingest, also in gigabytes, over a period of time. We felt like that was a little bit harder for people to map to their existing workflows, harder for them to predict. So we shifted to an events-per-month ingest model, one axis, one way to scale your usage.

Links:HoneycombCharity's websiteChristine Yen: Co-founder of honeycombPost on engineering management: the pendulum or the ladderPaper about Scuba - Facebook's Scuba data management system for real-time analysis Show notes:We start of by Charity explaining why she founded honeycomb. It all happened during her time at Facebook. She actually thought she will - after leaving Facebook - go on to be an engineering manager. But when she thought about how to engineer systems without all the tools and systems they had at Facebook, she realized that there is a big gap in the market. At Facebook, she relied heavily on a tool called Scuba. Scuba is Facebook's data management system to analyze and understand real-time data. Well, turns-out, outside of Facebook such great tools aren't available, or are not affordable. And because investors literally knocked at her door to fund her - after leaving Facebook - Charity took this chance and started honeycomb. In the early beginnings they literally just had four slides, an understanding of a problem (debugging and troubleshooting highly complex systems), and the desire to make an impact.Over the next year, Charity and her co-founder Christine Yen went all heads-down and figure out what exactly they want to build and how to talk about it.It was a long and painful process, but at one point they decided that the term observability is what describes best what they have in mind. (6:30)Charity explains that through observing the output of a system an engineer can actually infer what is going on internally. So, finally they knew themselves what they want to build and how to talk about it: they tried to build a system they let's you understand any state the system has gotten itself into, even  if you have never seen this state before. And such systems can have a big impact on people's life - especially for Site Reliability Engineers, DevOps, and Developers. Charity and I talk about how to make on-call experiences better, and how developers are nowadays more and more needed in the operations phase of a system. (7:40)Because even though we have Q&A departments, manual testers, dedicated operations peoples, Charity explains that also the engineers have to spend their time operating the systems. She says that nowadays there is no way to build reliable and maintainable systems, if the developers do not spend time actually understanding and analyzing how the system behaves in production.  She also explains why staging areas are a bad idea, and how those falsified environments just contribute to us learning the wrong signals, and destroying our ability to make good judgments about the behavior of the system when actual in production. (15:00)Charity also tells me that she thinks almost every developer should try out management at least for some time. She says that this experience gives engineers a new perspective and many valuable skills that  make them better engineers, even when they go back to engineering. (25:07)Later Charity fills me in on their tech stack, and also explains why code reviews and communication are valued so highly at their company. (29:35)Charity is a big believer of transparency and openness when it comes to sharing incident reports (33:37). Sharing revenue numbers on the other hand isn't something that's common in her market, and so, it would be a competitive disadvantage, she says (35:19).In the last bit of the interview, Charity shares with me how she found her first investors, and how they feel much more stable, secure and on the right track with this second round of funding. Well, I really enjoyed talking to and learning from Charity and really admire her openness. Thank you Charity for being on my show.  

Christine Yen (co-founder and CEO of Honeycomb) joined the show to talk about her upcoming talk at Strange Loop titled “Observability: Superpowers for Developers.” We talk practically about observability and how it delivers on these superpowers. We also cover the biggest hurdles to observability, the cultural shifts needed in teams to implement observability, and even the gains the entire organization can enjoy when you deliver high-quality code and you’re able to respond to system failure with resilience.

Christine Yen (co-founder and CEO of Honeycomb) joined the show to talk about her upcoming talk at Strange Loop titled “Observability: Superpowers for Developers.” We talk practically about observability and how it delivers on these superpowers. We also cover the biggest hurdles to observability, the cultural shifts needed in teams to implement observability, and even the gains the entire organization can enjoy when you deliver high-quality code and you’re able to respond to system failure with resilience.

Honeycomb co-founder and CEO Christine Yen spent a decade as a software engineer before creating her own company. She describes how her deep domain knowledge and relationships with like-minded software developers propelled her startup’s launch, and shares how she built an energetic human architecture around a highly technical B2B product.

Honeycomb co-founder and CEO Christine Yen spent a decade as a software engineer before creating her own company. She describes how her deep domain knowledge and relationships with like-minded software developers propelled her startup's launch, and shares how she built an energetic human architecture around a highly technical B2B product.

Honeycomb co-founder and CEO Christine Yen spent a decade as a software engineer before creating her own company. She describes how her deep domain knowledge and relationships with like-minded software developers propelled her startup’s launch, and shares how she built an energetic human architecture around a highly technical B2B product.

Monitoring and observability is something near-and-dear to my own heart, so this week’s episode is exciting: Christine Yen, Cofounder & CEO of Honeycomb, joins me to talk about observability, why dashboards aren’t as helpful as you think, and the value of being able to ask questions of your own application and infrastructure when you’re troubleshooting.

How do you measure the success of a feature in your application? While at NDC in London, Carl and Richard talked to Christine Yen about her experiences building instrumentation systems for applications both to diagnose problems and to understand how to make software better. The conversation digs into the scientific method of hypothesizing a potential feature, exploring different ways to build it and deciding on measurements of success - know when something works!Support this podcast at — https://redcircle.com/net-rocks/donations

How do you measure the success of a feature in your application? While at NDC in London, Carl and Richard talked to Christine Yen about her experiences building instrumentation systems for applications both to diagnose problems and to understand how to make software better. The conversation digs into the scientific method of hypothesizing a potential feature, exploring different ways to build it and deciding on measurements of success - know when something works!Support this podcast at — https://redcircle.com/net-rocks/donations

Joining us this week is Christine Yen, Co-founder at Honeycomb coming from a recording at SRECon Americas in March 2018 at Santa Clara Convention Center Hyatt. Highlights • Understanding of what developer tools are today • Observability vs Monitoring • Instrumenting Apps for Diagnostics to help Developers do More • Tool to build not just better engineers but teams as well to support customers • Brief history of Honeycomb and where it came from (Parse and Facebook) • How debug containers that are most likely gone by time problem arises? • AI / Machine Learning – can it really help today? • 2nd Wave of DevOps • Impact of listening to users at a startup – people problems vs technology

Brian talks with Christine Yen (@cyen, Co-Founder at @honeycombio) about the concept of Observability, why it's needed with new application and failure patterns, how to think about testing in production, and how to manage the collection of Observability data. Show Links: Honeycomb Homepage Honeycomb Blog [Velocity Conf] “End-to-End Observability for Fun and Profit” Use promo-code CLOUD for 20% off tickets to Velocity Conf [PODCAST] @PodCTL - Containers | Kubernetes | OpenShift - RSS Feed, iTunes, Google Play, Stitcher, TuneIn and all your favorite podcast players [A CLOUD GURU] Get The Cloudcast Alexa Skill [A CLOUD GURU] A Cloud Guru Membership - Start your free trial. Unlimited access to the best cloud training and new series to keep you up-to-date on all things AWS. [A CLOUD GURU] FREE access to AWS Certification Exam Prep Guide - At A Cloud Guru, the #1 question received from students is "I want to pass the AWS cert exam, so where do I start?" This course is your answer. [FREE] eBook from O'Reilly Show Notes Topic 1 - Welcome to the show. Before we get into the topic of Observability, tell us about your background and how you ultimately came to founding Honeycomb? Topic 2 - Let’s start with the basics - what is “Observability” and is this new or different from the thing we’ve called “Monitoring” for a long time? What’s changing that is driving the need for Observability? Topic 3 - Digging into Observability, there seems to be this question of “how do we know if something is up?”. That seems both simple and complex (in context). Let’s talk about what that means in a distributed system. Topic 4 - So Honeycomb collects data about applications in a bunch of different ways - logs, agents, monitoring APIs, etc. - What does Honeycomb do to all that information to start making it useful? Topic 5 - I’ve heard your co-founder Charity Majors (@mipsytipsy) talk about this idea that Honeycomb allows people ask questions of the data. What does this mean? Topic 6 - I was reading your blog about Fender Guitars using Honeycomb for their applications. Fender isn’t a Silicon Valley company. How are non-Valley companies beginning to use these Observability models? Feedback? Email: show at thecloudcast dot net Twitter: @thecloudcastnet and @ServerlessCast

Charity Majors has been on-call in one form or another since she was 17. She knows how to get to the bottom of system performance problems. After stints at Parse and Facebook, Charity and co-founder Christine Yen started Honeycomb, whose mission is to help software engineers use event data to explore and better understand their production systems. In this episode of Pivotal Insights, Charity joins Jeff and Dormain to talk about the challenges of debugging distributed systems, why a data-driven approach is the best way to get to the bottom of performance issues, and how software engineers can get their atrophied debugging muscles back into shape.

Charity Majors has been on-call in one form or another since she was 17. She knows how to get to the bottom of system performance problems. After stints at Parse and Facebook, Charity and co-founder Christine Yen started Honeycomb, whose mission is to help software engineers use event data to explore and better understand their production systems. In this episode of Pivotal Insights, Charity joins Jeff and Dormain to talk about the challenges of debugging distributed systems, why a data-driven approach is the best way to get to the bottom of performance issues, and how software engineers can get their atrophied debugging muscles back into shape.