Honeycomb changelog honeycomb.io

You can now use either Boolean or String type fields in the Error breakdown on Home!

If your dataset has an Error field that receives error messages as the value, the Error Rate will be calculated based on that field, and you will also be able to breakdown your data based on that field.

Hi-de-ho neighbors! We have some Home Improvements for you.

Markers on the graphs

You can now see your range and point markers on the Home graphs.

Have a tracing dataset? We filter out undefined values by default.

You asked and we listened! Many of you wanted to filter out undefined field values from the breakdowns on your tracing datasets. Now we do! Click a breakdown, and we only show you the events where that field exists.

Hover over a table row to see the data for that group in the charts

We're all used to this interaction in our main query builder, and now it's available on Home too.

Do you love .NET? When you go through the new dataset flow, you'll now be offered .NET Core as an integration! This is Honeycomb's first community-contributed integration, from Martin Thwaites. Check it out here or go straight to the github repo.

With the new Honeycomb Home, get an instant introduction to key system metrics and find access to Honeycomb's deeper introspective views of your production data just a click away.

Learn more by visiting the official docs for Home: https://docs.honeycomb.io/working-with-your-data/home/

Derived column enthusiasts just leveled up further! (If you aren't one yet, start with the blog series "Level Up with Derived Columns").

BUCKET lets you bucket a column into groups.

For example, BUCKET($app.batch_total_datapoints,1000,0,10000)

EVENT_TIMESTAMP returns the timestamp for an event; and IF now can take two arguments, in which case it returns null if false.

Sometimes, a trace can have missing or async spans - which means the parent will be shorter than its children. Now, parent nodes have a visual cue to show how far out their children reach, making it easier to collapse and scroll them.

Distributed systems make for distributed knowledge — and we know team Owners may not be the experts on every field in a dataset. That’s why we’re making schema editing features open to all team members. You’ll still need Owner permissions to change dataset quotas or JSON unfurl settings, but Members will now be able to show or hide columns, add aliases, set column maximum lengths, and edit field types.

Trace filtering is now available! Take it for a whirl in order to search the full text of a span tree. Check it out on your favorite baffling trace!

The Tracing sidebar now has query menus for each field, so you can run queries from span details!

We now support Okta as an Identity Provider. If you're using Okta, head to the setup guide here to get things hooked up.

As a team owner, you can also now turn off SSO.