This post is an answer to the MCP Server Challenge :robot:
We’ve been making enormous use of the Dynatrace MCP, dtctl, and APIs for a while now - here are a few of our coolest use cases so far.
If you caught our chat at Dynatrace Perform, you will have seen how we’re connecting Slack to Dynatrace with our agent, IRIS. Using both the Dynatrace API and a combination of our own MCP and the official Dynatrace one, we can now gather incredible amounts of data into Slack via a simple query. It allows us to work in one spot with multiple tools and platforms - not just in the observability space - and simplifies how our users interact with discrete systems.
- mention @iris in Slack with your query
- kicks off an n8n workflow with connection to our AI engine, parsing the query and routing to tool calls
- tool calls Dynatrace, Google Cloud, our API gateway, change systems, and more
- final data is gathered and response is given in Slack
Since then, we’ve been having a great deal of fun with Claude Code and dtctl - it’s been a very powerful combination. Our first major breakthrough came a few weeks ago, and it solved a problem we’ve been noticing in our Kubernetes environment. So, we posed to Claude: why, if Dynatrace already has context of Kubernetes services, will it show raw IPs in trace context when the application pod back-ends are unavailable? After 45 minutes and minimal additional prompting, we had a solution built out which now has:
- a Dynatrace workflow which runs every six hours to enrich a data table with all current KUBERNTES_SERVICE entity names and IPs, and
- an OpenPipeline setup which takes all traces going through Kubernetes, and - if the IP in a particular span matches one of the KUBERNETES_SERVICE entity names from the workflow - enriches the span
So now, anytime a back-end is unavailable, we no longer just see a random IP as “request to unmonitored host” or “request to public networks” in the span, but see the Kubernetes service metadata already within Dynatrace, but never before added to span context in failure cases. For this effort, I had to write precisely zero DQL, workflows, or pipelines myself. Claude and dtctl did it all!
Just last week, I gave Claude another challenge. We have an environment where OneAgent installation isn’t possible, but we have OpenTelemetry and Prometheus capabilities. Given this setup, how can I validate the performance between hosts at the network level in particular? After about a minute, it suggested the Prometheus Blackbox Exporter for our use case - and, once I gave it a list of host pairs to test (stored in GitHub, I just copy-pasted our internal repo link and it handled the gh auth stuff) - it built out a set of configs to deploy.
The best part? It asked me on its own after that if I wanted a Dynatrace dashboard - and when I responded yes, it built out all the JSON and uploaded it to Dynatrace, based on similar dashboards for this project that we’ve already made (also with dtctl)!
If you have access to Claude Code, I highly recommend plugging the dtctl skill into it. It’s been a total game-changer for us.
