We know how important your integrations are. Getting that actionable data into your IDP is foundational to everything. This month we focused on making that process easier for AWS, updated documentation for the GitHub process, and added more context to help you get back up and running when an integration breaks. Plus more.

Bigs:

🔑 You can now configure relationship keys for AWS integrations 

Users are now able to customize the tags that define Infrastructure Objects’ relationships with services. Previously, pre-selected tags were defined by OpsLevel to enable users to associate infrastructure with services; now, admins can define these tags or use the ones available out of the box. This enables users to take advantage of pre-existing tags configured on their AWS infrastructure.

Account admins can configure the account-wide tags. This new section can be found under Account → Settings in the UI.

‍

Read more in the docs. 

Mediums:

🔧 Fix deactivated integrations faster

Integrations are an integral part of OpsLevel, and making sure that they remain active is key to making sure everything continues to run smoothly and accurately. We now provide more context as to why a particular integration was deactivated in all cases for all integrations. This additional context helps users to more quickly remediate any issues that lead to the deactivation to get it reconnected. 

Smalls:

✏️ GitHub integration permissions updated in docs

A section detailing the required permissions for GitHub integrations is now available in the docs. This will make the process of getting your GitHub integration up and running so you can start performing checks against your repos much smoother. 

View the full integration documentation here.

📣 Tweaks to Service Level Change Notifications

Users will no longer receive multiple notifications when a service level changes, then changes back to its original state within the consolidated time frame. This will cut down on alert noise and help devs more accurately prioritize issues that need to be addressed regarding level changes. Timestamps have also been removed to make the notifications cleaner and more readable. 

‍

⏰ Campaign reminders can now be sent to a default Slack channel if no service owner contact information is available

Users can now set up a default Slack channel to receive campaign notifications if a service associated with a campaign does not have an owner, or if the assigned service owner does not have a Slack channel set up. This new feature enables Campaign owners to identify which teams may not be aware of the campaign so they can follow up.

‍