Honeycomb changelog honeycomb.io

We have launched event-based pricing for all teams, including 60-day retention for all datasets (regardless of plan type). We've also made improvements to the Usage page and notifications about data volume and throughput. For more details see this blog post or visit our pricing page.

When you post a link to a single trace in Slack, you’ll now see a preview image of the trace in the Slack unfurl, just as you do for query results. Requires the Honeycomb Slack integration.

Operational rate limits for Free plans have been changed to 1,000 events per second. Rate limits for all other plans remain the same. In addition, Honeycomb will now send periodic emails when operational rate limiting occurs. You can learn more about rate limited events in the Usage section on your Team Settings page.

You can now find the email settings for who should receive Usage related emails on the Team Settings page.

To help you better understand how your ingest changes over time, we’ve expanded the Daily Ingest and Daily Event Traffic charts on the Usage page to 60 days from their original 30.

You can now rerun a trace query from the trace view! This is useful if you have missing spans that may have arrived after navigating to the trace query permalink. Rerunning the trace query will pick up these missing spans.

You can now copy the table value from the dropdown menu! This will strip the commas out of the numbers, making them easier to paste into other places.

Moving forward, when you switch datasets in the query builder, the query will be preserved. You can execute it by typing Shift + Enter or clicking the Run Query button. You can also clear the query by clicking the Clear link underneath the Run Query button.

This functionality is especially useful when switching between testing and production datasets, where much of the schema overlaps. It's also useful when you need to view a specific time range across multiple datasets (yes, the time range of the query is included when you switch datasets).

If there are fields in the query that do not exist in the new dataset, Honeycomb will display an informational notice letting you know that those fields were removed from the query.

On the Dataset Settings Overview page, you can now see which teammate created a dataset and when. If the dataset was created via an api key, it will show the creator as "API".

Community teams will now be able to configure two triggers! Read more about triggers.

Teams on this plan will now be able to see unlimited personal and team query history in the sidebar on the query builder.