Showing entries 1 to 3
Displaying posts with tag: honeycomb (reset)
On the Observability of Outliers

At work, I am in an ongoing discussion with a number of people on the Observability of Outliers. It started with the age-old question “How do I find slow queries in my application?” aka “What would I want from tooling to get that data and where should that tooling sit?”

As a developer, I just want to automatically identify and isolate slow queries!

Where I work, we do have SolarWinds Database Performance Monitor aka Vividcortex to find slow queries, so that helps. But that collects data at the database, which means you get to see slow queries, but maybe not application context.

There is also work done by a few developers which instead collects query strings, query execution times and query counts at the application. This has access to the call stack, so it can tell you which code generated the query that was slow.

It …

[Read more]
Percona Live Europe Featured Talks: Debugging with Logs (and Other Events) Featuring Charity Majors

Welcome to another post in our series of interview blogs for the upcoming Percona Live Europe 2017 in Dublin. This series highlights a number of talks that will be at the conference and gives a short preview of what attendees can expect to learn from the presenter.

This blog post is with Charity Majors, CEO/Cofounder of Honeycomb. Her talk is Debugging with Logs (and Other Events). Her presentation covers some of the lessons every engineer should know (and often learns the hard way): why good logging solutions are so expensive, why treating your logs as strings can be costly and dangerous, how logs can impact code …

[Read more]
451 CAOS Links 2011.03.25

Red Hat grows revenue 20%+. Google withholding Honeycomb source code. And more.

Follow 451 CAOS Links live @caostheory on Twitter and, and daily at
“Tracking the open source news wires, so you don’t have to.”

# Red Hat reported Q4 revenue up 25% to $245m, FY revenue up 22% to $909m

# Google is withholding the source code to Honeycomb for the foreseeable future.

# Rick Clark explained why he left Rackspace amid concerns that the company is exerting too much control over OpenStack.

# DataStax …

[Read more]
Showing entries 1 to 3