TIP: Applications are a premium feature and not available on all TrackJS plans. Check the Pricing plans for details.
TrackJS Applications allow you to segment your error data by codebase or environment. Each codebase you want to protect should have it’s own application key, in addition to each deployed environment. This is done by creating application keys in the TrackJS Dashboard, and assigning them to the
application install option.
For example, let’s say your main web application is deployed to a “production” environment for real users, and a “test” environment for internal testing. You wouldn’t want noisy test data clouding your reports about production or setting off alerts. You would create 2 applications:
my-app-test. After creating the application keys, update your agent config with the
You may also want to protect other codebases with TrackJS, such as another application or your public website. You’ll want to create more applications for each of them to see which are having trouble. You would create additional applications:
You can filter the Dashboard to show data from All Applications or a Single Application using the Filtering Toolbar.
Setting this filter updates all screens in the Dashboard.
Application keys are nothing more than a filtering string. Deleting an application from your Dashboard only removes your ability to filter by that application. If you recreate an application with the same key, all of the errors recorded to the key will be filterable again.