With our Alert Source integrations, OpsLevel can surface the operational health of your services from external tools such as DataDog and PagerDuty.
To help standardize the configuration of your services, you can use an Alert Source Usage check to validate the presence of Alert Source(s) on them. You are able to define further constraints on the check, such as requiring it to be from a specific tool and/or be named in a particular fashion.
The Alert Source Usage Check
When you set up the alert source usage check without specifying any advanced options, it will validate the existence of an Alert Source on your service.
Just validating the presence of an alert source may be enough, but the check is even more powerful and specific with the advanced options described below.
Using an Alert Source Type
The Alert Source Type option will display all the integrations we support that provide Alert Sources. By choosing the type, the check will validate that an alert source of that type exists for the service.
Example: Check PagerDuty is configured
To ensure proper service ownership and standardized incident management, the check can be configured to ensure that every OpsLevel service is associated with a PagerDuty service.
Using an Alert Source Name
The alert source name can also be matched with certain conditions. This can help you enforce naming standards for your alert sources and/or validate that alert sources of a certain nature exist for the service.
Example: Verify that a DataDog CPU Usage monitor is attached to your service as an alert source
You may want to ensure that your services are monitoring CPU Usage. You can set up an alert source usage check that confirms an alert source from DataDog has been attached to your service whose name contains “CPU Usage”. This configuration is shown below. This can also be helpful for unifying naming conventions in your DataDog instance.