Cortex connects to many third-party vendors whose system interfaces frequently change. As a result, integration behavior or configuration steps may shift without notice. If you encounter unexpected issues, check with your system administrator or refer to the vendor’s documentation for the most current information. Additionally, integration sync times vary and are subject to scheduling overrides and timing variance.
- View errors on entity pages in Cortex, giving you insight into your entity’s operational maturity
- Create Scorecards that include rules relating to error data from Rollbar, motivating team members to improve their code quality
How to configure Rollbar with Cortex
Prerequisites
Before getting started:- Create a Rollbar access token.
- The token requires
readpermissions at minimum. This allows Cortex to automatically look up project tokens for each Rollbar project and attempt to reuse them to access project details. - Granting the token
readandwritepermissions enables Cortex to automatically create an access token if none exists for a given project.
- The token requires
Configure the integration in Cortex
- In Cortex, navigate to the Rollbar settings page:
- Click Integrations from the main nav. Search for and select Rollbar.
- Click Add configuration.
- Configure the integration form:
- Account access token: Enter the access token you generated in Rollbar.
- Account name: Enter your Rollbar account name, found in your Rollbar settings.
- The name also appears in the URL for your Rollbar instance, e.g.,
- Click Save.
How to connect Cortex entities to Rollbar projects
Discovery
By default, Cortex will use the Cortex tag (e.g.my-entity) as the “best guess” for Rollbar projects. For example, if your Cortex tag is my-entity, then the corresponding project in Rollbar should also be my-entity.
If your Rollbar projects don’t cleanly match the Cortex tag, you can override this in the Cortex entity descriptor.
Editing the entity descriptor
You can define projects under thex-cortex-rollbar block in an entity’s YAML:
Using the Rollbar integration
Viewing Rollbar errors on an entity
Error data from Rollbar will appear on an entity’s details page. In an entity’s sidebar, click Error tracking to view detected issues for each Rollbar project. At the top of the page, see the associated project tag and the project framework. Under Items, see a list of detected errors and their statuses. Next to the error name, you can also see badges for# seen and the type of event: error, warning, or info.
Scorecards and CQL
With the Rollbar integration, you can create Scorecard rules and write CQL queries based on Rollbar projects. See more examples in the CQL Explorer in Cortex.Check if Rollbar project is set
Check if Rollbar project is set
Check if entity has a registered Rollbar project.Definition: This is also a good way to confirm the integration is synced and reporting frequently.You could also query for entities that don’t have a registered Rollbar project to quickly identify those that need to be updated:
rollbar (==/!=) nullExampleYou can define a rule in an operational readiness Scorecard to make sure each entity has a registered Rollbar project.RQL query
RQL query
Evaluate an RQL query for the Rollbar project.If the entity does not have a Rollbar project set, the rule will fail. An empty result set will result in null.Definition: Or you can set a rule that gauges errors over time:This rule checks that entities have fewer than 5 new errors per day on average over the last 30 days.
rollbar.rql(<query>)ExampleAn operational maturity Scorecard, you can use this expression to make sure entities have fewer than 100 open errors.View integration logs
This feature is available in Cortex cloud.

Still need help?↗
The following options are available to get assistance from the Cortex Customer Engineering team:- Email: help@cortex.io, or open a support ticket in the in app Resource Center
- Slack: Users with a connected Slack channel will have a workflow added to their account. From here, you can either @CortexTechnicalSupport or add a
:ticket:reaction to a question in Slack, and the team will respond directly.