Connect Datadog
The Datadog connector lets qbash Tasks inspect monitors, dashboards, logs, metrics, events, incidents, hosts, notebooks, spans and Software Catalog entities through Datadog's native REST API. It authenticates with an API key and an application key.
Prepare the key pair
- Sign in to your Datadog account on the site that holds your organization. If you need a new account, sign up on Datadog, review its terms and choose a plan.
- Open Organization Settings → API Keys. Use an API key created for this connector.
- Open Organization Settings → Application Keys. Create a scoped application key for the same organization. A service account avoids tying Task access to an individual employee.
- Grant only the read permissions your Tasks require. The application key's owner must also have permission to read those resources. Some products and datasets depend on your Datadog plan.
Application keys in newer organizations are shown only at creation time. Store the key through the credential form and keep it out of Task code and messages. API and application keys belong to one organization and site. New keys may need a few seconds to propagate.
See Datadog's API and Application Keys for key ownership, scoping and one-time visibility.
Choose read permissions
| Operations | Permissions to check on the application key and its owner |
|---|---|
| List, get and search monitors | monitors_read |
| List and get dashboards | dashboards_read |
| Search and aggregate logs | logs_read_data, with access to the required indexes |
| List metrics | metrics_read |
| Query metric timeseries | timeseries_query |
| List and get events | events_read |
| List and get incidents | incident_read |
| List hosts | hosts_read |
| List and get notebooks | notebooks_read |
| Search and aggregate spans | apm_read |
| List Software Catalog entities | apm_service_catalog_read |
Log restriction queries, index permissions and resource restrictions can further narrow results. A valid key pair does not guarantee that every operation is available. Consult Datadog's Role Permissions and the endpoint's API Reference when a request is refused.
Add the credential in qbash
Open Connectors → Datadog → Connect. Enter a name, choose your Datadog site and enter both keys. Saving sends the key pair to the selected Datadog API to validate it.
| Site | Site parameter |
|---|---|
| US1 | datadoghq.com |
| US3 | us3.datadoghq.com |
| US5 | us5.datadoghq.com |
| EU1 | datadoghq.eu |
| AP1 | ap1.datadoghq.com |
| AP2 | ap2.datadoghq.com |
| UK1 | uk1.datadoghq.com |
| US1-FED | ddog-gov.com |
| US2-FED | us2.ddog-gov.com |
Datadog's Getting Started with Datadog Sites explains how to find your site's parameter. The selector accepts these official sites. Custom domains must use the underlying site's parameter.
When editing, leave either secret blank to retain it. A name-only change preserves the existing credential data. Changing the site checks the saved or replacement keys against the newly selected site.
Use the credential in a Task
Select the credential under the Task's Tools → Integrations, then call the connector:
page = qbash.integrations.datadog.list_monitors(limit=20)
qbash.output(page)
List and search operations make one bounded page request. Use the returned next_cursor with the same operation and filters to continue, and stop when it is None. Some Datadog APIs return a complete non-paginated response instead. The SDK Reference describes each method's parameters and result shape.
Keep query windows short and result limits small during testing. Metrics can aggregate points over longer periods, and spans and logs reflect the data retained and accessible in your account. An empty result means the chosen query returned no accessible data.
A 401 means authentication failed. A 403 can mean that the key, its owner or the selected product lacks access. Rate-limit errors need backoff before a new attempt. The connector does not retry requests automatically or follow redirects.
Scope
The selected operations support read-only diagnosis based on Datadog's MCP Server Tools and public REST endpoint contracts. The connector calls REST endpoints directly. It covers part of the core toolset and does not claim full MCP parity.
Writes, account and key management, ingestion, OAuth setup, hosted MCP access, synthetics, security products and deployment workflows are outside this connector's scope. These need separate permissions or product flows.
Read one event
Use items[].attributes.attributes.evt.uid from list_events as the event_id for get_event. The top-level list item id is a search-result identifier and may return 404 when used for event lookup. The returned event can retain a different top-level identifier; compare attributes.attributes.evt.uid to confirm identity. See the official event response fields.