dt-alerting
SolidEnd-to-end Dynatrace alerting lifecycle — anomaly detector setup and model selection (static threshold, adaptive baseline, seasonal baseline), alert event storage in Grail, problem grouping and denoising by root cause analysis, and workflow-based notification routing (email, Slack, ServiceNow, webhook). Use when configuring alerting, choosing between detector types, querying alert event history, understanding why alerts merged into a problem, or setting up problem-triggered notifications.
Install
Quality Score: 88/100
Skill Content
Details
- Author
- Dynatrace
- Repository
- Dynatrace/dynatrace-for-ai
- Created
- 3 months ago
- Last Updated
- 4 days ago
- Language
- Shell
- License
- Apache-2.0
Similar Skills
Semantically similar based on skill content — not just same category
dt-obs-problems
DAVIS problem analysis including root cause identification, impact assessment, and correlation with other telemetry. Use when querying or investigating detected problems. Trigger: "active problems", "root cause analysis", "problem impact", "affected users", "list problems", "P-12345 details", "recurring problems", "problem history", "problem trending", "blast radius", "which entity caused the problem", "problems affecting Kubernetes", "problems by service". Do NOT use for explaining existing queries, product documentation questions, generic log searching, distributed tracing, or host-level resource monitoring.
proactive-alerts
Set up proactive GTM alert systems — CRM pipeline alerts, buying signal notifications, Slack/email routing, risk scoring. Use when building alert systems, monitoring pipeline health, detecting buying signals, or setting up automated notifications for GTM teams. Triggers on: "alerts", "notifications", "pipeline alerts", "signal alerts", "monitor pipeline", "deal alerts", "Slack alerts", "pipeline monitoring", "proactive", "warning system", or any request about automated detection and notification.
monitoring-alerting
Monitoring and alerting design reviewer for production backend services. ALWAYS use when writing Prometheus alerting rules, designing Grafana dashboards, defining SLI/SLO, configuring alert routing (PagerDuty/OpsGenie/Slack), or reviewing existing monitoring setups. Covers SLI/SLO definition, alert rule quality (sensitivity/specificity tradeoff), burn-rate alerting, alert fatigue prevention, dashboard design principles, label cardinality management, and on-call routing configuration. Use even for "just add an alert" — a poorly designed alert either pages at 3AM for non-issues (alert fatigue) or stays silent during real outages (false confidence).