Honeycomb changelog
Honeycomb changelog

Filter BubbleUp Results




You can now filter for specific fields in your BubbleUp results. Filter by field name in the search bar above your results in the Query Builder and SLOs page.


Data Ingested Times Available for Columns and Datasets via the API




The Datasets and Columns APIs now include the last_written_at and created_at timestamps as part of the responses. Thelast_written_at is the timestamp of when data was last ingested for the Dataset or Column. These attributes allow for investigations into stale datasets and columns or to double-check if data was successfully received.

Recipients API & PagerDuty Severity

The Recipients API is now available for all Honeycomb customers. This API allows for full management of email, Slack, PagerDuty, and webhook recipients. Terraform Provider support for the API is also available in v0.8.0 of the provider.

PagerDuty Severity

We’ve enhanced our PagerDuty integration. Now each PagerDuty recipient allows you to define the severity of notifications for Triggers and Burn Alerts. The severity can be set to Critical, Error, Warning, or Info using the UI, API, or the Honeycomb Terraform Provider. The default severity continues to be Critical if you do not set a value. Once set in Honeycomb, PagerDuty incidents originating from your Triggers and Burn Alerts can take advantage of custom rules and escalation policies based on the severity you've defined.






Boards Time Range Permalinks




You can now share Boards links that remember a pre-selected time range! Simply toggle the time selector on a Board to the desired time window and share the boards URL.

More links to Derived Columns




You can now quickly access Derived Columns from more places in the UI. Find direct links to Derived Columns in the Schema Sidebar where you can iterate on the expression next to your queries. These are currently only available for service/dataset specific queries.


The SLO Detail Page now links directly to your SLIs for easier SLO authoring and iteration.


Show Next/Previous Span Error




You can now quickly navigate between errors in the Trace Waterfall view! Traverse your trace by clicking on the error link above the waterfall and select the arrow buttons.

Note that Error Highlighting must be configured before you can jump between error spans! Learn how to configure them in our docs.


Shareable & Sticky Trace Fields




We've enhanced how you can share and view Trace Waterfall fields!

Shareable Trace Fields

Links will now persist your selected trace fields in the URL. Try this out by selecting fields in the trace waterfall view and then sharing the URL with a coworker — when they load your trace, they’ll be able to see the same fields you had selected in your view.

Sticky Trace Fields

Your selected trace waterfall fields will now be captured in your browser and will no longer reset whenever you view a trace.

Note that Shareable Trace Fields (as defined in the trace URL) will still take precedence. For example, if someone shares a trace link, you'll see the fields that they were looking at rather than the ones you last selected.


Keyboard Shortcut: Collapse & Expand Spans




You can now use the left and right arrow keys to collapse and expand selected spans in the Trace Waterfall view.

Type ? while on the Trace Waterfall view to see the full menu of keyboard shortcuts

Delete Environments




You can now delete environments that you no longer need.

With great power, comes great responsibility. Deleting an environment will permanently delete everything in that environment, including datasets, derived columns, queries, permalinks, SLOs, triggers and boards. All events sent to that environment will be immediately rejected.


Environments are now available for all Teams




Classic teams can now create Environments and Services. A migration process is still under development to help teams move their data and configurations from Classic into a specific Environment.

What is Classic in the UI?

If your team was created before the Environments and Services update, you had the datasets-only model which was called Honeycomb Classic.

env selector + fly out.png

All of your data is now grouped underneath a simplified environment called "Classic". You data is safe and sound, and you can continue to use Honeycomb in the same way as before. Some features associated with Environments and Services are not available for Classic.

To create an environment, go to "Manage Environments" in the Environment Flyout. Learn more about Environments and Services, minimum version requirements, and product features via docs and our Product Tour. (Select "Take Tour" in the Environment flyout)

What if I don't see Classic?

This update only applies to teams that didn't have Environments previously. For all others, you should not experience any changes in Honeycomb.

What about migrations?

Migrations are under development. Teams that need tooling and support to migrate their Honeycomb configurations from Classic into an Environment can wait for the process to be available. If your team does not need this, you can start over by sending data to an environment. Learn more about how to transition into Environments via docs.