Observability and cloud costs · Available
Dynatrace for Claude, ChatGPT and Copilot
Dynatrace already works out the root cause of a problem. mcpbizapps lets people ask Claude, ChatGPT or Copilot about it, along with which problems are open, which services and hosts are affected and how SLOs are tracking. Queries run in DQL against Grail within each role's scope, and maintenance windows are approved before they take effect. Each request is logged. A guided pilot connects your Dynatrace environment with the observability team.
- Status
- Available
- Setup
- Guided pilot with your team
- AI assistants
- Claude, ChatGPT, Copilot Studio
- Access
- By role, view only or with approvals
Ask in a sentence
What can your team ask Dynatrace?
Questions from SRE, application owner, head of operations and others, answered from live Dynatrace data and only for the people allowed to see them.
Records it works with
- Problems
- Services
- Hosts
- Process groups
- SLOs
- Dashboards
- Notebooks
- Maintenance windows
- SRE
“Which problems are open in production, and what root cause does Dynatrace list for each?”
- Application owner
“How did response time for the claims-processing service change after Monday's release?”
- Head of operations
“Which SLOs for the customer portal are burning error budget fastest this week?”
- Infrastructure manager
“Which hosts in the Frankfurt data center ran above 90% memory for more than an hour yesterday?”
- On-call engineer
“Which services does the current checkout problem affect, according to Smartscape?”
- FinOps lead
“How much log data went into each Grail bucket last month?”
Changes, governed
What the assistant can prepare in Dynatrace
The assistant never saves on its own. It prepares the change, the person checks the preview and confirms, and anything above your limits waits for an approver.
- 1 Prepare The assistant drafts the change from the request.
- 2 Preview and confirm The person sees exactly what will change.
- 3 Approve Above your limits, a second person decides.
- 4 Saved and logged Written to Dynatrace under a named person.
-
Create a maintenance window for a patch weekend
The application owner confirms; windows longer than six hours on production need the SRE lead.
-
Add a comment to an open problem
Comments change nothing in monitoring, so the engineer posting it is the only check.
-
Close a problem that has recovered
The on-call engineer confirms after the preview shows the affected entities are healthy.
Example rules. During the pilot you set the limits, the approvers and which roles may prepare each change.
Why it needs care
Governance built for Dynatrace
Dynatrace sees every service, host and user session, so its data can reveal customer activity and internal architecture. Assistants stay inside the management zones or segments each role allows. A maintenance window is shown with the entities it covers, and long windows need approval. Every DQL query keeps the name of the person who asked.
-
Sign-in by work email
Only people you invite, with a one-time code. No shared logins.
-
Roles per tool
Each role reaches only the Dynatrace records it needs.
-
View only, if you prefer
Admins can keep a connection to lookups with one switch.
-
A preview first
Every change is shown in full before anything is saved.
-
Approval rules
Above your limits, a second person approves the change.
-
One audit log
Every request tied to a named person, ready for review.
Setup
How Dynatrace gets connected
We connect Dynatrace for your team in a guided pilot, on the same gateway every app uses. No code on your side.
- 01
Agree the questions
We list the Dynatrace questions and changes your team needs, and who may use each.
- 02
Connect with your admin
Your Dynatrace administrator creates a dedicated integration user with only that access.
- 03
Test with your people
A small group tries it in Claude, ChatGPT or Copilot while we tune the tools.
- 04
Roll out with rules
Roles, approval limits and the audit log are in place before everyone joins.
Then people use it from the assistant they already have
Dynatrace questions
Can ChatGPT explain a Dynatrace problem?
Yes. The assistant reads the problem, the root cause Dynatrace found and the affected entities, and explains them in a few sentences with links back to Dynatrace for the full analysis.
Does the assistant use DQL?
Yes. For questions about logs, metrics or events stored in Grail, the assistant writes a DQL query, runs it within your role's scope and time limit, and shows it alongside the answer.
How does this relate to the assistant built into Dynatrace?
The built-in assistant works inside Dynatrace. mcpbizapps lets people ask from Claude, ChatGPT or Copilot, so the access rules a person has hold the same way across Dynatrace and the other tools you connect.
Does mcpbizapps keep a copy of our Dynatrace data?
No. When someone asks a question, mcpbizapps reads the answer live from Dynatrace through a dedicated integration user and returns it without storing it. The audit log records who asked, which tool ran and the result, with personal fields and free text removed.
Dynatrace is a trademark of its owner. mcpbizapps is not affiliated with Dynatrace; the name describes the connection only.
Related
Often connected alongside Dynatrace
Part of IT, security and operations: Service desks, identity, monitoring and cloud costs.
Start
Bring Dynatrace into your AI assistant
Tell us how your team uses Dynatrace, and we will plan a guided pilot around your own questions.
- We agree the tools and approval rules with you
- Your admin creates the integration user; no code
- Business data is read live and not stored
Thank you
We received your request and will reply by email to find a time.
Last updated