Agentic AI integration for
Workflows is able to actively react to changes and analyze real-time data in your environment by using Dynatrace agentic tools.
By using agentic AI workflow integration, you can:
To use the Dynatrace Intelligence agentic AI workflow action, ensure that you have the following permissions:
ai:operator:executemcp-gateway:servers:invokemcp-gateway:servers:readdocument:documents:readDepending on the tools you use, you might need additional permissions. For more information about tool-specific permissions, see Server and server tools.
To use Dynatrace Intelligence (Preview), you need to
If you don't have a subscription, please reach out to your Customer Success Manager (CSM).
Dynatrace Hub, search for Dynatrace Intelligence (Preview).Standard usage limits for Agentic and generative AI are also applied to Dynatrace Intelligence (Preview):
| Item | Maximum limit |
|---|---|
Individual user requests | 25 requests per 15 minutes |
All user requests across the environment | 60 requests per 15 minutes |
Tools per request | 20 |
Duration of request to operator processing | 120 seconds |
If you schedule the automatic workflow execution to run frequently, all other Dynatrace Intelligence agentic and generative AI functionality might get throttled due to reaching the request limit. If you do run into the usage limit, please reach out to your CSM or let us know in the Agentic and generative AI Preview User Group in our Community.
To create a workflow with Dynatrace Intelligence (Preview) action
Workflows.Dynatrace Intelligence into the search field or select Dynatrace Intelligence > Prompt Agentic AI.You can enter a maximum of 10,000 characters in this field.
You can enter a maximum of 200,000 characters in this field.
You can enter a maximum of 5,000 characters in this field.
We highly recommend that you select only the tools relevant to your task or question. Choosing all of the tools might significantly increase the time agentic AI needs for executing your prompt.
In the Output format (JSON schema) field, provide a JSON schema describing fields be included in the output. The example below shows a schema describing serviceID field:
{"$schema": "http://json-schema.org/draft-07/schema#","type": "object","properties": {"serviceId": {"type": "string"}},"required": ["serviceId"]}
While the Output format (JSON schema) field is optional, it will be included in the workflow output regardless of whether it was filled or not.
If you left Output format (JSON schema) field empty, the output will look like this: jsonOutput: null.
In the Conversation ID field, provide the ID of another workflow action that called an agent before to continue a previous conversation with an agent. You can get the previous conversation ID by referencing the output of a previous workflow action that used an agentic tool. The example below uses a result of a workflow action invoke-agent-1 as an input for a conversationId:
{{ result("invoke-agent-1")["conversationId"] }}