Tasks Overview
Tasks are reusable, configurable execution units that run specific actions in DrDroid runbooks. They allow you to fetch logs, query metrics or databases, run commands, or trigger external systems — all through a consistent UI.
Whether you’re debugging a live issue or automating remediation, tasks are the building blocks of your incident workflows.
📋 Task Configuration
| Field | Description |
|---|---|
| Name | User-defined label for easy identification |
| Action Type | The type of operation (e.g., fetch logs, run command) |
| Integration | The connected platform (e.g., Datadog, PostgreSQL, EKS) |
| Integration Name | Specific instance of the integration configured in your account |
| Query/Command | The core input — log query, PromQL, SQL, bash command, or API body |
| Variables | Parameterized values used for dynamic input across environments |
🚀 Task Execution
You can test run a task directly from the UI before saving it into a runbook:
- Select a time range (e.g., last 15 minutes, past hour)
- Run the query or command against the selected integration
- View results immediately to validate correctness
This helps you iterate quickly and ensures reliability before automation.
⚙️ Supported Actions
DrDroid currently supports 15+ predefined action types. You can select the action while creating a task and configure it based on your need.
| Category | Example Actions | Learn More |
|---|---|---|
| Terminal Commands | Bash scripts, shell commands | Writing Terminal Commands |
| Fetch Metrics | PromQL, Cloudwatch, Datadog, New Relic, etc. | Writing Metric Queries |
| Fetch Logs | Loki, Cloudwatch, Elastic, GCP, etc. | Writing Log Queries |
| Fetch DB Results | PostgreSQL, ClickHouse, JDBC-based DBs | Writing SQL Queries |
| Custom Actions | API calls, EKS metadata, bash scripts | Writing Custom Actions |
Each guide above includes:
- What the action does
- Required fields and formats
- How to structure a valid query or command
- Examples to copy and tweak
💡 Best Practices
- Start with a test run using a short time window
- Use variables to make tasks reusable across services/environments
- Add clear task names to help during runbook execution
- Leverage provided examples as starting points and iterate
🧭 What’s Next?
Note: The “Learn More” links will direct you to detailed documentation for each action type.
Tasks Overview
Tasks are reusable, configurable execution units that run specific actions in DrDroid runbooks. They allow you to fetch logs, query metrics or databases, run commands, or trigger external systems — all through a consistent UI.
Whether you’re debugging a live issue or automating remediation, tasks are the building blocks of your incident workflows.
📋 Task Configuration
| Field | Description |
|---|---|
| Name | User-defined label for easy identification |
| Action Type | The type of operation (e.g., fetch logs, run command) |
| Integration | The connected platform (e.g., Datadog, PostgreSQL, EKS) |
| Integration Name | Specific instance of the integration configured in your account |
| Query/Command | The core input — log query, PromQL, SQL, bash command, or API body |
| Variables | Parameterized values used for dynamic input across environments |
🚀 Task Execution
You can test run a task directly from the UI before saving it into a runbook:
- Select a time range (e.g., last 15 minutes, past hour)
- Run the query or command against the selected integration
- View results immediately to validate correctness
This helps you iterate quickly and ensures reliability before automation.
⚙️ Supported Actions
DrDroid currently supports 15+ predefined action types. You can select the action while creating a task and configure it based on your need.
| Category | Example Actions | Learn More |
|---|---|---|
| Terminal Commands | Bash scripts, shell commands | Writing Terminal Commands |
| Fetch Metrics | PromQL, Cloudwatch, Datadog, New Relic, etc. | Writing Metric Queries |
| Fetch Logs | Loki, Cloudwatch, Elastic, GCP, etc. | Writing Log Queries |
| Fetch DB Results | PostgreSQL, ClickHouse, JDBC-based DBs | Writing SQL Queries |
| Custom Actions | API calls, EKS metadata, bash scripts | Writing Custom Actions |
Each guide above includes:
- What the action does
- Required fields and formats
- How to structure a valid query or command
- Examples to copy and tweak
💡 Best Practices
- Start with a test run using a short time window
- Use variables to make tasks reusable across services/environments
- Add clear task names to help during runbook execution
- Leverage provided examples as starting points and iterate
🧭 What’s Next?
Note: The “Learn More” links will direct you to detailed documentation for each action type.