Rollbar requires the
environment property on all errors to indicate where they occurred (
qa , etc.).
The choice of which
environment values to use is very important due to the following considerations:
- Items cannot be merged if they are in different environments
- The Dashboard, Items, and Deploys views can only show information from a single environment or all environments.
Many of our customers deploy their apps to multiple production systems, e.g. multiple zones in Amazon Web Services, Google Cloud Platform, Azure, etc.
In this case, you might want to see all the items and deploys to any of your production environments at once, but also be able to track which system a particular error occurred in. You probably will want to merge items that occurred in different production environments if they have the same root cause.
- Use the environment value
productionfor all errors from and deploys to any production environment, even if you have multiple production environments.
- Use the
hostproperty in your error payloads to include the 'full path' of the server where an error occurred, including the name of the region/zone, e.g.
us-east-1-web02for the server
web-02that is hosted in the
If you follow this approach, you can then merge any items that occur in a production environment, regardless of which region/host it occured in.
To find the items that are only occurring in a particular region, you can use the host advanced search option, which supports prefix search:
To find items that occurred on a specific server within the region, you can enter the fully-qualified host name:
It's likely that you care more about errors coming from your production environment than from non-production environments, and that you don't want a non-production error to consume too many Rollbar events.
In order to ensure that you can use Rollbar in all your environments but limit event consumption in non-production environments, we recommend the following:
- Create a set of access tokens for your non-production environments, and apply a rate limit that makes sense for you.
- Create a set of access tokens for your production environments, and don't apply rate limits, unless you can accept losing some error data from production.
Updated 9 months ago