---
title: "Dynatrace evidence-guided incident analyst: review, role & definition · Undominated.ai"
canonical: https://undominated.ai/agents/github-dynatrace-expert/
description: "A Dynatrace investigation reference connecting traces, exceptions, deployments and current security findings."
---

# Dynatrace evidence-guided incident analyst: review, role & definition · Undominated.ai

> A Dynatrace investigation reference connecting traces, exceptions, deployments and current security findings.

[← Explore all agents](/agents/)

OBSERVABILITY / GitHub community

# Dynatrace evidence-guided incident analyst

A Dynatrace investigation reference connecting traces, exceptions, deployments and current security findings.

 [Use this definition ↓](#setup)[Original source ↗](https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/agents/dynatrace-expert.agent.md)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 4 linked sources
 Publisher GitHub community
 Licence [MIT ↗](https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/LICENSE)
 Revision f25421d3f1b8
 [Read what was—and wasn’t—checked ↓](#review)

“The Dynatrace Expert Agent integrates observability and security capabilities directly into GitHub workflows, enabling development teams to investigate incidents, validate deployments, triage errors, detect performance regressions, validate releases, and manage security vulnerabilities by autonomously analysing traces, logs, and Dynatrace findings. This enables targeted and precise remediation of identified issues directly within the repository.”

 [GitHub community · upstream description ↗](https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/agents/dynatrace-expert.agent.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - It asks to inspect exception span events and correlate logs, metrics and traces rather than infer cause from one aggregate.
- The security example selects a scan identifier before retrieving findings, keeping scan state separate from accumulated historical rows.

### A good fit for

 - Supply the authorized tenant, bounded time window, service identity and investigation question.
- Receive reproducible query proposals and evidence-linked findings with explicit data coverage.

### Weigh up before choosing

 - The definition embeds a development-tenant URL; never send a real token there by copying it unchanged. DQL examples, latest-scan assumptions and wildcard MCP capabilities require validation against the actual tenant.
- Source-only component: inspect its upstream context and dependencies before adapting it; no standalone runnable bundle is offered.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - agents/dynatrace-expert.agent.md (pinned complete source retained)
- LICENSE
- Repository README and current official host configuration documentation

### Our findings

 - It asks to inspect exception span events and correlate logs, metrics and traces rather than infer cause from one aggregate.
- The security example selects a scan identifier before retrieving findings, keeping scan state separate from accumulated historical rows.

### Not established by this review

 - Source review only: no agent was installed or invoked. Task correctness, effective host restrictions and integration behaviour were not tested.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Use the role in your project.

[Upstream setup instructions ↗](https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/agents/dynatrace-expert.agent.md)
 - Read the pinned source and its licence, then configure an explicitly bounded host context.
- Replace the endpoint with the authorized environment URL, scope tokens/tools and test bounded queries; separate observation from any issue creation or remediation.
- Supply the authorized tenant, bounded time window, service identity and investigation question.

### Before you start

 - Authorized Dynatrace tenant and scoped authentication
- Configured MCP gateway and required telemetry access

### Compatibility

GitHub Copilot

### Implementation

Markdown

### Host-mediated agent profile

 - No tools allowlist is declared. GitHub Copilot can inherit or expose the host’s available tools by default; restrict file, shell and network access in the host.

### Cost model

The definition has the stated open-source licence. Model/host usage and any connected service or execution environment can incur separate costs.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Pinned upstream agent definition ↗](https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/agents/dynatrace-expert.agent.md) Checked 2026-10-14 https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/agents/dynatrace-expert.agent.md Supports: Workflow, inputs, outputs and stated boundaries
- [Applicable licence ↗](https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/LICENSE) Checked 2026-10-14 https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/LICENSE Supports: Redistribution and attribution
- [Host configuration and tool inheritance ↗](https://docs.github.com/en/copilot/reference/custom-agents-configuration) Checked 2026-10-14 https://docs.github.com/en/copilot/reference/custom-agents-configuration Supports: Host loading and effective permission boundaries
- [Official tenant-specific Dynatrace MCP setup ↗](https://docs.dynatrace.com/docs/dynatrace-intelligence/dynatrace-mcp) Checked 2026-10-14 https://docs.dynatrace.com/docs/dynatrace-intelligence/dynatrace-mcp Supports: Dependency setup and source-review limitations

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Find reusable instructions](/skills/)
- [Inspect connections](/mcp-servers/)
- [Build a toolkit](/tools/)
- [Choose the model](/compare/)
