Honeycomb changelog honeycomb.io

For periodic data captured at regular intervals, such as metric data, you can now set a minimum default granularity to ensure that queries don't drop below it (goodbye spiky graphs). You can also still override the default granularity on each individual query as needed.

The Honeycomb Management API is now generally available to all Honeycomb users. This is a set of endpoints that let you programmatically set up, configure, and delete queries, datasets, derived columns, and more.

With this release, you can now manage Honeycomb with configuration as code either directly via API or with third-party tools, like Terraform, using the community-contributed Honeycomb provider. These capabilities enable advanced automation of common Honeycomb tasks that can improve your workflow.

Read more in our blog post.

Queries now auto-run whenever you zoom into your charts! You can spend less time clicking and more time digging into your data. Find us in the ux-feedback channel in our Honeycomb Pollinators Slack if you have any feedback.

The public API for triggers includes a new field, triggered, that returns the current state. This addition allows you to more seamlessly integrate triggers into your workflow. The change is not yet available in Secure Tenancy, but will be included in the next release. You can find more information in our docs.

Based on customer requests, we've changed the available options in the date range picker for queries and boards. Visit us in the ux-feedback channel in Honeycomb's Pollinators Slack if you have any feedback.

This version of Secure Tenancy introduces support for receiving OpenTelemetry OTLP trace data.

Additionally, this version includes a bug fix for proxying the correct content-type header for requests being sent to Honeycomb.

If you are a Secure Tenancy customer, to access the new version of Secure Tenancy:

1. Log into Honeycomb
2. Go to Team Settings and click on the Secure Tenancy tab
3. Scroll to the bottom of the page - the new releases are listed there

Please contact support@honeycomb.io if you have any questions.

A new version of Secure Tenancy is available.

This release includes:

• Ability to get derived columns by alias and delete derived columns (Derived Column API - BETA)
• A correction to the masked output of column names inside of derived column expressions upon creation
• Golang updated to version 1.15.8
• Datasets API - BETA
• Introduction of tracing support in Secure Tenancy metrics: Proxy metrics now use traces for easier performance analysis and debugging
• A clearer error message and status code when decoding malformed JSON bodies

If you are a Secure Tenancy customer, to access the new version of Secure Tenancy:

1. Log into Honeycomb
2. Go to Team Settings and click on the Secure Tenancy tab
3. Scroll to the bottom of the page - the new releases are listed there

Please contact support@honeycomb.io if you have any questions.

A new version of Honeycomb's Secure Proxy is available.

This release has two important bug fixes that improve the reliability and security of interacting with the secure proxy from the Honeycomb UI:

• Fix user verification fallback behavior that is causing some sporadic “Oops” messages in the UI for Secure Tenancy users.
• Use a 302 redirect instead of a 301 for unhandled GET requests.

If you are a Secure Tenancy customer, to access the new version of Secure Tenancy:

• Log into Honeycomb
• Go to Team Settings and click on the Secure Tenancy tab
• Scroll to the bottom of the page
• The new releases are listed there

Please contact support@honeycomb.io if you have any questions.

Honeycomb now handles names and descriptions for saved queries with ease. This blog post details all of the improvements included in this update, which makes the experience of working with saved queries more powerful and intuitive than ever. We've also resolved a number of issues, such as queries on boards changing to "Untitled" when the date range is changed, and query names not appearing in browser tabs and history.

The new INGEST_TIMESTAMP() derived column function can help you find and debug event latency or inaccurate timestamps.

// How many seconds did it take for this event to arrive?
SUB(INGEST_TIMESTAMP(),EVENT_TIMESTAMP())

Honeycomb began storing ingestion times on January 28; events created before this will have INGEST_TIMESTAMP() == EVENT_TIMESTAMP().