OBSERVABILITY / GitHub community
Dynatrace evidence-guided incident analyst
A Dynatrace investigation reference connecting traces, exceptions, deployments and current security findings.
“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.”
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.
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.
- 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
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/agents/dynatrace-expert.agent.md
Supports: Workflow, inputs, outputs and stated boundaries
- Applicable licence ↗Checked
https://github.com/github/awesome-copilot/blob/f25421d3f1b8b3bb217f78a7c0567cf7ec117cd8/LICENSE
Supports: Redistribution and attribution
https://docs.github.com/en/copilot/reference/custom-agents-configuration
Supports: Host loading and effective permission boundaries
https://docs.dynatrace.com/docs/dynatrace-intelligence/dynatrace-mcp
Supports: Dependency setup and source-review limitations