New Relic integration
Centralize New Relic user management and alerting to accelerate incident response and maintain secure access controls.
What it connects
- Sync organization accounts, users, and team memberships to keep your digital twin current with New Relic's access model.
- Retrieve authentication domain details to understand how users and teams are organized across your observability infrastructure.
- Access user lists and group memberships to correlate with incident response and on-call assignments.
- Pull muting rule status and alert configuration to coordinate with ticket escalation policies.
What it automates
- Assign users to groups in New Relic based on team changes, ensuring access is provisioned as teams scale.
- Remove users from groups when they change roles or leave teams, preventing orphaned permissions.
- Mute alerts during maintenance windows and attach silence records to change tickets for audit trails.
- Grant or revoke role-based access to teams, completing the provisioning lifecycle without manual user interaction.
In practice
When a new engineer joins the platform team, STLabs automatically assigns them to the DevOps group in New Relic and tags them with their cost center for billing correlation.
During a critical incident. STLabs mutes alert storms while the team investigates and logs the muting rule to the incident ticket for post-mortem review.
An engineer leaves the company; STLabs removes them from all New Relic groups and revokes their role-based access, with all changes recorded in the audit log.
STLabs synchronizes New Relic account admins with your identity provider, ensuring that team leads automatically gain the right permissions to manage their observability workspace.
