Almost everything in Honeybadger is scoped to a project. We have some powerful configuration features to help you manage your errors.
You can make an error public by clicking “Share URL” in the actions area of the error you want to share. We provide you with a unique URL to give to collaborators. This is great but can be cumbersome when sharing multiple errors. Public Dashboards are a place where collaborators can view shared errors.
Once you enable the Public Dashboard (Project Settings > Advanced > Enable public dashboard), collaborators can find shared errors in a similar view as the error listing page (with some restrictions). This can be especially useful if you pair this feature with [project actions](/guides/
Project API keys grant access to our reporting APIs. The list of reporting endpoints is in our api docs. If an API key is leaked or misused, you can rotate your key by adding a new key and removing the old one.
Project API keys don’t grant access to our REST API. You will need to use your personal token for that.
Project Actions let you customize your errors as we receive them. Through actions, you can automatically:
- Assign errors to yourself or another team member
- Add tags
- Pause notifications
- Share errors publicly
One exciting usage example for Project Actions is assigning errors to specific code owners.
For example, Ben takes care of most of the billing code here at Honeybadger. It would make sense that he should be assigned any errors related to billing. Here is a simple setup to route
StripeController errors to Ben:
You can run all your incoming errors through the actions, or you can use queries to constrain which errors have actions applied to them.
We often get asked if users can have multiple languages in a project. While it is technically possible, we recommend that you create a separate project for each, as we customize the experience based on the chosen language (Project Settings > Language)