Introduction to workflows
The Workflows app is a powerful tool that lets you automatically act on monitoring data.
Automatically react to Davis events or security problems.
Schedule reports in line with holidays and work hours.
Orchestrate IT processes across your entire IT landscape.
Connect to both cloud and locally gated services.
Combine out-of-the-box integrations with custom code.
Visualize automated processes in a graphical workflow interface.
Get live monitoring and a full audit trail of any automation execution.
Define flow logic with custom conditions, automatic retries, loops, and parallel processing.
For more information, see the quickstart example.
Explore in Dynatrace Hub
Automate tasks in your IT landscape, remediate problems, and visualize processes.
To access the Workflows and view workflows, you need at least the following permissions.
|Grants access to
|List all apps and read the app bundles.
To write and execute workflows, the following additional permissions are required.
|Grants access to
|Use the function executor.
You might need additional permissions to run certain tasks in the Workflows app.
The Dynatrace Hub entry for Workflows lists all the permissions on the Technical information tab, in the User permissions section.
For more information about Workflows security, see User permissions for workflows.
The Workflows app is your entry point to manage and monitor workflows. The app interacts with the automation service via its REST API. The automation service is responsible for processing your workflows and keeping track of the executions.
A workflow specifies a repeatable process by assembling a series of tasks.
The sequence of tasks is defined by their transitions, which allow for execution in series, in parallel, and with conditional paths.
Workflows can be edited and monitored in a visual graph.
Each step in a workflow is called a task.
A workflow keeps track of tasks and their order.
- A task defines a unit of work (for example,
Notify Ops in Slack, or
Get error log count), including the conditions, retry behavior, timeouts and, most importantly, the input configuration required to achieve the work and provide a result to be used by subsequent tasks.
An action is a generic, reusable function configured and triggered by tasks. For example, an action could be
Create Jira Issue, while a task would execute the action with a specific configuration to
Create Bug in Sample project.
Actions are the tools to be assembled in your workflows to fit your custom process.
Actions are provided out of the box by Dynatrace and partners and can be installed via Dynatrace Hub.
Workflows, tasks, and actions all define how work should be done. An execution represents a specific instance of running through that process.
An execution is triggered either by a schedule, by events, or manually via the Workflows app or the REST API.
Each execution of the same workflow might be different, depending on its parameters, inputs, and context.
- Each run of a workflow can be found as an individual entry in the Executions table.
To list all executions in your environment, select Executions in the Workflows app header.
- To filter the table, you can specify a combination of
- Keyword: a search string
- Workflow: the name of the workflow as displayed in the UI
- Execution state:
- Trigger type:
- Timeframe: a relative timeframe such as
Last 2 hoursor a custom timeframe with selectable From and To settings
- To list executions of a particular workflow, find the workflow in the table and select > View execution history in the Action column.
To list executions of the workflow you are editing, select Executions in the editor.
EdgeConnect allows you to reach your non-public services in workflow tasks. HTTP requests happening within any type of action or platform function can be proxied via EdgeConnect into the target network.