MonoDuty integrations
Connect the tools that detect incidents with the people who respond
MonoDuty publishes integrations across monitoring, cloud, development, market alerts, and team chat—without requiring teams to replace their signal sources.
No credit card required
01 / Directory
Explore integration guides
Detailed pages cover seven high-intent integrations. MonoDuty also lists GitHub, Jenkins, TradingView in its verified directory.
Grafana
Connect Grafana-originated alerts to an on-call incident workflow.
MonitoringPrometheus Alertmanager
Route Prometheus alerting toward the people and channels responsible for response.
ObservabilityDatadog
Carry Datadog-originated signals into MonoDuty incident alerting.
CloudAWS CloudWatch
Connect AWS CloudWatch alerts with your on-call operating model.
ChatSlack
Use Slack as an incident alert channel on Pro and Business plans.
ChatDiscord
Add Discord to the alert channel mix on Pro and Business plans.
ChatMicrosoft Teams
Deliver incident alerts through Microsoft Teams on Pro and Business plans.
02 / Overview
Keep detection and response connected
The verified MonoDuty directory lists Grafana, Prometheus, Datadog, AWS CloudWatch, Slack, Discord, Microsoft Teams, GitHub, Jenkins, TradingView. These tools cover different signal and collaboration roles, so integration design should start with the role each one already plays in your operation.
Monitoring and cloud sources can feed the incident path; supported chat services can act as delivery channels on Pro and Business. On-call scheduling provides the ownership layer across all plans.
03 / Operating value
Integrate around clear system boundaries
A useful integration keeps each tool responsible for the job it already does well.
Preserve the source of truth for detection
Keep monitoring and cloud rules in their originating systems, then connect their alert path to MonoDuty.
Centralize response ownership
Use MonoDuty on-call scheduling and, on Pro or Business, escalation policies to define who responds.
Deliver into supported collaboration channels
Slack, Discord, and Microsoft Teams are both listed integrations and published Pro/Business alert channels.
04 / Workflow
A repeatable integration rollout
Use the same validation discipline for every source, even when configuration details differ.
- 01
Define the source and incident class
Document what the originating tool detects and which events should enter the on-call workflow.
- 02
Configure from current documentation
Use MonoDuty docs for current endpoints, fields, and source-specific setup details.
- 03
Test ownership and delivery
Verify the intended schedule, escalation policy where available, and plan channels with a safe test.
05 / Plans
Choose the response capacity around the integration
Plan selection should reflect incident volume, team size, channels, and retention—not just the integration name.
Free
One user, 50 incidents/month, email and push, and 7-day retention.
Pro
Up to 25 users, 5,000 incidents/month, seven channels, escalation policies, and 30-day retention.
Business
Unlimited users and incidents, seven channels, escalation policies, status pages, advanced analytics, and 90-day retention.
06 / Questions
Common questions
01Which integrations does MonoDuty list?
The verified directory lists Grafana, Prometheus, Datadog, AWS CloudWatch, Slack, Discord, Microsoft Teams, GitHub, Jenkins, TradingView.
02Are Slack, Discord, and Microsoft Teams alert channels?
Yes. All three are listed as channels on the published Pro and Business plans.
03Where can I find exact integration setup steps?
Use MonoDuty documentation for current setup details and validate the full route with a safe test before production.
MonoDuty / Start
Connect one alert path end to end
Choose an important source, configure it from current docs, and validate who receives the resulting incident.