Before you start
- GitHub is connected and a default repository is selected in the GitHub connection settings. Auto Monitors works on that repository.
- Slack is connected.
- At least one observability source is connected, such as Sentry, Datadog, AWS CloudWatch, Azure Monitor, or Google Cloud. Ordyn creates monitors in these tools.
Setup
Open Detect and click Set up Auto Monitors.1
Environment
Name your production environment. Monitors are created when a change deploys here.Then choose how Ordyn learns about deploys: GitHub Deployments if your pipeline creates them, GitHub Workflow if you deploy from an Actions workflow that does not, or Other Webhook to have your deploy script tell Ordyn. See Deploys.
2
Provider access
Ordyn needs permission to create monitors in each provider you want it to use. The setup shows the exact grant for each one. Your existing read access stays as it is.
3
Slack routing
Choose the Slack channels alerts should post to, and describe in plain language what belongs in each one. You can create a new channel from here. Channels you leave off stay quiet.
4
Turn it on
Nothing happens until the next pull request opens. There is no backfill and no scan of existing code.
Settings you can change later
Open the settings from the Detect page.
You can also skip Auto Monitors for a single pull request from the review itself, or by adding the
struct:skip label. See Pull requests.