Latest Dynatrace
The Workflows app is a powerful tool that lets you automatically act on monitoring data.
For more information, see the quickstart example.
To access the Workflows and view workflows, you need at least the following permissions.
app-engine:apps:run
automation:workflows:read
To write and execute workflows, the following additional permissions are required.
app-engine:functions:run
automation:workflows:run
automation:workflows:write
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.
Each step in a workflow is called a task.
Create Incident
, 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
.
Workflows, tasks, and actions all define how work should be done. An execution represents a specific instance of running through that process.
To list all executions in your environment, select Executions in the Workflows app header.
Success
, Running
, Error
, or Warning
Manual
, Schedule
, or Event
Last 2 hours
or a custom timeframe with selectable From and To settingsTo 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.
Any HTTP request (from your custom app, workflow, or an ad-hoc JavaScript code) that matches a defined host pattern is handled by an EdgeConnect instance you specify in the platform configuration. For more information, see Configure and deploy EdgeConnect.