dt-alerting

Manage Dynatrace alerting lifecycle from anomaly detection to notification routing.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/mf-dynatrace/dt-mcp-workspace --skill dt-alerting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dt-alerting
Source: https://github.com/mf-dynatrace/dt-mcp-workspace/tree/main/skills/dt-alerting
Command: npx skills add https://github.com/mf-dynatrace/dt-mcp-workspace --skill dt-alerting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill manages the full alerting lifecycle in Dynatrace, from anomaly detector setup to problem denoising and notification routing.

Core Features & Use Cases

  • Anomaly Detector Setup: Configure anomaly detectors for various scenarios, including static, adaptive, and seasonal baselines.
  • Problem Denoising: Understand and manage alert merging and problem grouping by root cause analysis.
  • Notification Routing: Set up notifications for email, Slack, ServiceNow, and webhook, ensuring alerts are routed to the right team.
  • Use Case: A team uses this Skill to configure an alerting rule for high CPU usage and set up a Slack notification for critical incidents.

Quick Start

To create an alert for high CPU usage on a specific host and send a Slack notification, run the following command: alert dt-alerting high-cpu-alert --send-notification-to slack

Frequently Asked Questions about dt-alerting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Dynatrace anomaly detection for high CPU usage and route alerts to Slack?

Dynatrace alerting lifecycle management covers configuring anomaly detectors for static, adaptive, and seasonal baselines, then setting up problem denoising and notification routing to target channels like Slack or email.

What are the five types of alert sources supported for Dynatrace notification routing?

Dynatrace notification routing supports five alert source types: DQL-based, Edge, Pipeline, Synthetic, and External, ensuring comprehensive coverage for various monitoring scenarios across your environment.

Do I need specific DQL permissions to manage the Dynatrace alerting lifecycle?

Yes, managing the Dynatrace alerting lifecycle requires active access to your Dynatrace environment and relevant DQL permissions to configure DQL-based anomaly detection and execute alerting queries successfully.

How does problem denoising work when merging Dynatrace alerts by root cause?

Problem denoising in Dynatrace works by managing alert merging and grouping alerts through root cause analysis, reducing noise so teams receive consolidated notifications for related underlying issues.

Can I set up Dynatrace alerting rules for adaptive and seasonal baseline anomalies?

Yes, you can configure Dynatrace anomaly detectors for various scenarios including static, adaptive, and seasonal baselines, allowing you to tailor alerting rules to your specific environmental patterns.

What is the best way to route Dynatrace problem notifications to ServiceNow and webhooks?

The best way to route Dynatrace problem notifications is by configuring notification routing within the alerting lifecycle to integrate directly with ServiceNow, email, Slack, or custom webhooks for targeted delivery.