Datadog API
Arcade Unoptimized
Tools that enable LLMs to interact directly with the Datadog API.
Author:Arcade
Version:
0.2.1Auth:No authentication required
588tools
588require secrets
The Arcade toolkit for DatadogApi empowers developers to interact seamlessly with the Datadog API to manage monitoring, analytics, and incident responses. This toolkit enhances the ability to automate workflows, streamline operations, and effectively manage cloud resources.
Capabilities:
- Efficiently manage Datadog integrations, monitor resources, and handle alerts.
- Automate operational workflows, including on-call management and incident response.
- Support configuration management for AWS, Azure, and GCP services.
- Streamline security monitoring and logging capabilities.
- Facilitate role and permissions management across teams.
Secrets:
- Configuration includes various secrets like
DATADOG_API_KEY,DATADOG_APPLICATION_KEY, and others essential for API access.
Available tools(588)
588 of 588 tools
| Tool name | Description | Secrets | |
|---|---|---|---|
Acknowledge an On-Call Page alert in Datadog.
Use this tool to acknowledge an On-Call Page alert for a specified page in Datadog. This can be used to indicate that an alert is being addressed. | 2 | ||
Activate Agentless scan options for an AWS account. | 2 | ||
Activate Agentless scan options for Azure subscriptions.
Use this tool to activate Agentless scan options for a specified Azure subscription. This is useful for enabling security scans without deploying agents. | 3 | ||
Activate Agentless scan options for a GCP project.
Use this tool to enable Agentless scanning for a Google Cloud Platform project. This is useful for setting up security scans without deploying agents. | 3 | ||
Add a comment to a specific case in Datadog.
Use this tool to post a comment to a particular case within the Datadog system by providing the case ID. | 3 | ||
Add dashboards to an existing list in Datadog.
Use this tool to append dashboards to a specified existing dashboard list in Datadog. Ideal for organizing and managing dashboards effectively.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 3 | ||
Add a member team to a super team.
Use this tool to add a specified team as a member of an existing super team by providing the super team's ID. | 2 | ||
Assigns a specific permission to a given role.
Use this tool to add a permission to a specific role within Datadog. It should be called when you need to assign new permissions to a role to adjust user access and capabilities. | 2 | ||
Adds a read role to a specified archive.
Use this tool to grant read access to a specific archive by adding a read role. Ideal for managing permissions and ensuring the right users or groups have access to log data archives. | 2 | ||
Adds a role to a restriction query for logs configuration.
This tool is used to add a specific role to an existing restriction query in Datadog's logs configuration. Call this tool when you need to update restriction queries by including additional roles. | 3 | ||
Add a new link to a Datadog team.
Use this tool to add a new link to a specific team's page in Datadog. Suitable for enhancing team resources or documentation by linking additional references. | 2 | ||
Adds a user to a specific role in Datadog.
Use this tool to add a user to a specific role in Datadog's system. It is called when you need to assign user permissions via roles. | 3 | ||
Add a user to a team in Datadog.
Use this tool to add a specified user to an existing team within Datadog by providing the team ID. | 3 | ||
Aggregate logs to compute metrics and timeseries.
This tool aggregates log events into buckets to compute relevant metrics and timeseries. It's useful for analyzing large volumes of log data to extract meaningful insights.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
If you need the schema, call with mode='get_request_schema' ONCE, then execute. | 3 | ||
Aggregate CI pipeline event metrics and timeseries.
This tool aggregates CI Visibility pipeline events into buckets of computed metrics and timeseries. Use it when you need to analyze CI pipeline performances and trends.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
If you need the schema, call with mode='get_request_schema' ONCE, then execute. | 3 | ||
Aggregate RUM events into computed metrics and timeseries.
This tool aggregates Real User Monitoring (RUM) events into buckets of computed metrics and timeseries. It is used when there is a need to analyze and visualize RUM data effectively.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
If you need the schema, call with mode='get_request_schema' ONCE, then execute. | 3 | ||
Aggregate spans to compute metrics and timeseries.
Use this tool to aggregate spans into buckets and compute metrics and timeseries data. This is useful for analyzing performance and trends in systems. Note: Limited to 300 requests per hour.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
If you need the schema, call with mode='get_request_schema' ONCE, then execute. | 3 | ||
Aggregate CI Visibility test events into metrics and timeseries.
Use this tool to aggregate CI test events into buckets for computed metrics and timeseries insights.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
If you need the schema, call with mode='get_request_schema' ONCE, then execute. | 3 | ||
Archive an Azure Cloud Cost Management account in Datadog.
Use this tool to archive a Cloud Cost Management account associated with Azure in Datadog. This action is irreversible and should be performed when you need to remove cost management configurations for a specific Azure account. | 2 | ||
Archive a specific case in Datadog.
This tool is used to archive a case in Datadog by specifying the case ID. Call this tool when you need to move a case to the archive for record-keeping or compliance. | 2 | ||
Archive a Cloud Cost Management Account.
Use this tool to archive a Cloud Cost Management Account in Datadog, specifically for AWS CUR configurations. Useful for managing or removing outdated or unnecessary cost configurations. | 2 | ||
Archive a Cloud Cost Management account.
Use this tool to archive a Google Cloud Platform (GCP) cost management account in Datadog. | 3 | ||
Assign a case to a specific user.
Use this tool to assign a case to a specific user by providing the case ID. It should be called when you need to allocate a case to an appropriate team member or user. | 2 | ||
Delete multiple items from a datastore at once.
Use this tool to delete multiple items from a specified datastore by their keys in a single operation. It's ideal for efficiently removing batches of entries when managing datastore contents. | 3 | ||
Perform bulk creation or replacement of datastore items.
Use this tool to create or replace multiple items in a Datadog datastore in a single operation by specifying their keys.
Note: Understanding the request schema is necessary to properly create
the stringified JSON input object for execution.
This operation also requires path parameters.
Modes:
- GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't
already have it. Do NOT call repeatedly if you already received
the schema.
- EXECUTE: Performs the operation with the provided request body
JSON.
Note: You must also provide the required path parameters when executing.
If you need the schema, call with mode='get_request_schema' ONCE, then execute.
| 2 |
Page 1 of 24(25 of 588)
Last updated on