Have you ever blown through your entire error budget in an incident, worked to fix the underlying issue, and then wished you could easily reset your SLO's Error Budget so you and your Burn Alerts can have a fresh start?
Users of our Service Level Objective (SLO) feature (included with Enterprise plans) can now do just that. To reset your SLO's Error Budget, click the new "Reset" button on the SLO page.
Learn more in our docs.
API keys now include a permission for creating datasets:
This new permission allows you to have finer-grained control over how datasets are created for your team, and reduces risk associated with embedding your API key in client code (both in browser and native apps).
The permission is enabled for all existing API keys and will default to on when new keys are created. You can disable this permission using the settings dialog pictured above.
We’ve improved the Dataset Overview page to give you a better idea of the dataset’s usage. Now you can see each dataset’s retention, daily event traffic, and event rate at a glance, and get more detailed information on rate limiting.
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.
