MCP Datadog Server
The MCP Datadog Server is a comprehensive Model Context Protocol (MCP) compatible server that provides LLMs with 351 tools for complete Datadog integration through schema auto-discovery and validation.
Core Capabilities:
Full CRUD Operations: Create, read, update, delete, and list all Datadog resources including monitors, dashboards, downtimes, users, teams, and organizations
Data Analytics & Aggregation: Process and aggregate data from CI pipelines, logs, RUM events, spans, network connections, and DNS traffic
Infrastructure Monitoring: Configure diverse monitor types (metric, logs, APM, synthetics, SLO, audit, database, network performance, cost) with automated alerting
Cloud Integrations: Manage AWS, Azure, GCP integrations plus third-party services like Slack, PagerDuty, Opsgenie, Microsoft Teams, Cloudflare, and Okta
Security & Compliance: Handle WAF rules, workload protection policies, agentless AWS scanning, and resource restriction policies
Log Management: Configure archives, pipelines, indexes, custom destinations, and log-based metrics
User Administration: Manage users, roles, permissions, authentication mappings, API keys, and child organizations
Incident Management: Handle cases, priorities, status updates, on-call schedules, and escalation policies
Performance Monitoring: Create span-based metrics, retention filters, RUM applications, and DORA metrics
Advanced Features:
LLM-Native Design: Automatic tool discovery with JSON schemas, type safety, and robust validation
Smart Filtering: Categorize tools by service type to reduce complexity
Real-time Tracking: Monitor long-running operations with progress updates
CLI Interface: Comprehensive command-line tools for management, debugging, and troubleshooting
Error Handling: Automatic retry mechanisms with configurable timeout and retry settings
Provides comprehensive tools for interacting with Datadog's API, enabling management of monitors, logs, metrics, dashboards, and incidents. Supports creating and updating monitors, sending logs, submitting metrics, querying timeseries data, and performing analytics operations.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Datadog Server show me the top 5 monitors by alert count from the last 24 hours"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Datadog Server
Servidor MCP (Model Context Protocol) completo e robusto para integração com APIs do Datadog
Um servidor MCP de produção que oferece 351 tools para interagir com todas as APIs do Datadog através de LLMs, incluindo operações CRUD completas, tools curadas e ferramentas geradas automaticamente do schema.
🚀 Características Principais
📊 Tools Disponíveis (351 total)
9 Tools Curadas 🎯 - Handcrafted, otimizadas para casos específicos
25 Tools CRUD ⚡ - Operações CREATE, READ, UPDATE, DELETE para recursos principais
319 Tools Geradas 🔧 - Geradas automaticamente do schema oficial do Datadog
🔍 Recursos Avançados
✅ Autodescoberta de Schema - LLMs descobrem parâmetros automaticamente
✅ Validação Robusta - Zod schemas com validação completa
✅ Progress Tracking - Acompanhamento em tempo real para operações longas
✅ Error Handling - Tratamento inteligente de erros e retry automático
✅ CLI Rica - Interface completa para gestão e debugging
🛡️ Conformidade MCP
✅ 100% Compatível com TypeScript SDK oficial
✅ JSON Schema completo para todas as tools
✅ Metadata Annotations detalhadas
✅ Type Safety com validação Zod
Related MCP server: Datadog MCP Server
📦 Instalação
Requisitos
Node.js 18+
Chaves de API do Datadog (API Key + Application Key)
Instalação via npm
npm install -g mcp-datadog-serverInstalação Local
git clone https://github.com/ClaudioLazaro/mcp-datadog-server.git
cd mcp-datadog-server
npm install⚙️ Configuração
1. Variáveis de Ambiente
Obrigatórias
DD_API_KEY=your_api_key # Chave da API Datadog
DD_APP_KEY=your_app_key # Chave da aplicação DatadogOpcionais
DD_SITE=datadoghq.com # Site Datadog (padrão: datadoghq.com)
DD_SUBDOMAIN=api # Subdomínio (padrão: api)
MCP_DD_FOLDERS=Dashboards,Logs # Categorias permitidas (padrão: todas)
MCP_DD_SCHEMA_PATH=./schema.json # Caminho do schema (padrão: incluído)
MCP_DD_MAX_RETRIES=3 # Máximo de tentativas (padrão: 3)
MCP_DD_RETRY_BASE_MS=1000 # Base para retry em ms (padrão: 1000)
MCP_DD_TIMEOUT_MS=30000 # Timeout das requisições (padrão: 30000)
MCP_DD_USER_AGENT=mcp-datadog # User agent customizado2. Arquivo .env (Recomendado)
# .env
DD_SITE=\"us3.datadoghq.com\"
DD_API_KEY=\"xxxxxxxxxxxxxxxxxxxxxxxx\"
DD_APP_KEY=\"xxxxxxxxxxxxxxxxxxxxxxxxxxxx\"
MCP_DD_FOLDERS=\"Dashboards,Monitors,Logs\"3. Sites Datadog Suportados
datadoghq.com(US1)datadoghq.eu(EU)us3.datadoghq.com(US3)us5.datadoghq.com(US5)ap1.datadoghq.com(AP1)ddog-gov.com(US Gov)
🎮 Uso
Servidor MCP (Padrão)
# Iniciar servidor MCP
mcp-datadog-server serve
# ou
npm start
# Com filtros
mcp-datadog-server serve --folders=Dashboards,MonitorsInterface CLI
Listar Tools
# Lista básica
mcp-datadog-server list-tools
# Lista detalhada ordenada
mcp-datadog-server list-tools --detailed
# JSON output
mcp-datadog-server list-tools --jsonInspeção de Tools
# Ver detalhes de uma tool
mcp-datadog-server get-tool create_monitor
# Ver schema completo de uma tool
mcp-datadog-server show-schema create_monitor
# JSON output
mcp-datadog-server show-schema create_monitor --jsonValidação e Análise
# Validar configuração
mcp-datadog-server validate
# Analisar schema da API
mcp-datadog-server analyze-schema
# Ajuda
mcp-datadog-server help🔧 Tools CRUD Disponíveis
⚡ Monitors (5 operações)
create_monitor # Criar novo monitor
get_monitor # Obter monitor por ID
update_monitor # Atualizar monitor existente
delete_monitor # Deletar monitor
list_monitor # Listar todos os monitors📊 Dashboards (5 operações)
create_dashboard # Criar novo dashboard
get_dashboard # Obter dashboard por ID
update_dashboard # Atualizar dashboard existente
delete_dashboard # Deletar dashboard
list_dashboard # Listar todos os dashboards⏰ Downtimes (5 operações)
create_downtime # Agendar downtime
get_downtime # Obter downtime por ID
update_downtime # Atualizar downtime
delete_downtime # Cancelar downtime
list_downtime # Listar todos os downtimes👥 Users (5 operações)
create_user # Criar usuário
get_user # Obter usuário por ID
update_user # Atualizar usuário
delete_user # Deletar usuário
list_user # Listar todos os usuários🏗️ Teams (5 operações)
create_team # Criar equipe
get_team # Obter equipe por ID
update_team # Atualizar equipe
delete_team # Deletar equipe
list_team # Listar todas as equipes📋 Como o LLM Descobre os Parâmetros
🔍 Autodescoberta Automática
O LLM NÃO precisa saber os parâmetros antecipadamente. Através do protocolo MCP, ele:
Lista todas as tools disponíveis
Obtém o schema JSON Schema completo de cada tool
Entende todos os parâmetros, tipos e validações
Constrói chamadas válidas automaticamente
📄 Schema Exemplo - create_monitor
{
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "Monitor name"
},
"type": {
"type": "string",
"enum": ["metric alert", "service check", "event alert", "query alert", "composite", "log alert"],
"description": "Monitor type"
},
"query": {
"type": "string",
"description": "Monitor query"
},
"message": {
"type": "string",
"description": "Notification message"
},
"tags": {
"type": "array",
"items": {"type": "string"},
"description": "Monitor tags"
},
"priority": {
"type": "number",
"minimum": 1,
"maximum": 5,
"description": "Priority (1-5)"
},
"options": {
"type": "object",
"properties": {
"thresholds": {
"type": "object",
"properties": {
"critical": {"type": "number"},
"warning": {"type": "number"},
"ok": {"type": "number"}
}
},
"notify_audit": {"type": "boolean"},
"require_full_window": {"type": "boolean"}
}
}
},
"required": ["name", "type", "query"]
}🎯 Exemplo de Uso pelo LLM
Input do usuário:
"Create a monitor to alert when CPU usage is above 90%"
Chamada automática do LLM:
await use_tool("create_monitor", {
"name": "High CPU Usage Alert",
"type": "metric alert",
"query": "avg(last_5m):avg:system.cpu.user{*} > 0.9",
"message": "CPU usage is high! Please investigate @ops-team",
"tags": ["alert", "cpu", "infrastructure"],
"priority": 3,
"options": {
"thresholds": {
"critical": 0.9,
"warning": 0.8
},
"notify_audit": true,
"require_full_window": false
}
})O LLM automaticamente:
✅ Descobriu todos os parâmetros disponíveis
✅ Preencheu campos obrigatórios (name, type, query)
✅ Adicionou campos opcionais relevantes
✅ Estruturou objetos complexos (options.thresholds)
✅ Validou tipos e constraints
🎯 Tools Curadas Especiais
🎯 Dashboards
list_dashboards # Lista com filtros avançados e paginação🎯 Logs
search_logs # Busca avançada de logs com filtros🎯 Metrics
query_metrics # Query de métricas timeseries🎯 Incidents
manage_incidents # Gerenciamento completo de incidentes🎯 Synthetics
manage_synthetics # Testes sintéticos completos🏗️ Integração com LLMs
Claude Desktop (Recomendado)
Adicione ao arquivo de configuração do Claude:
{
"mcpServers": {
"datadog": {
"command": "mcp-datadog-server",
"args": ["serve"],
"env": {
"DD_API_KEY": "your_api_key",
"DD_APP_KEY": "your_app_key",
"DD_SITE": "datadoghq.com"
}
}
}
}Via npx (Global)
{
"mcpServers": {
"datadog": {
"command": "npx",
"args": ["-y", "mcp-datadog-server", "serve"],
"env": {
"DD_API_KEY": "your_api_key",
"DD_APP_KEY": "your_app_key"
}
}
}
}Local Development
{
"mcpServers": {
"datadog": {
"command": "node",
"args": ["/path/to/mcp-datadog-server/src/index.js", "serve"],
"env": {
"DD_API_KEY": "your_api_key",
"DD_APP_KEY": "your_app_key"
}
}
}
}🛠️ Desenvolvimento
Scripts Disponíveis
npm test # Executar testes
npm run serve # Iniciar servidor
npm run list-tools # Listar tools
npm run validate # Validar configuração
npm run analyze-schema # Analisar schema da APIMakefile
make install # Instalar dependências
make start # Iniciar servidor
make test # Executar testes
make list-tools # Listar tools
make validate # Validar configuraçãoEstrutura do Projeto
src/
├── index.js # CLI principal
├── server.js # Servidor MCP principal
├── core/
│ ├── config.js # Sistema de configuração
│ ├── http-client.js # Cliente HTTP com retry
│ ├── schema-parser.js # Parser do schema Datadog
│ └── validation.js # Validações robustas
└── tools/
├── core-tools.js # Ferramentas base
├── curated-tools.js # Tools curadas otimizadas
└── crud-tools.js # Tools CRUD automáticas🔍 Debugging e Troubleshooting
Verificar Tools Carregadas
# Ver resumo
mcp-datadog-server list-tools
# Ver lista completa ordenada
mcp-datadog-server list-tools --detailed
# Ver schema de uma tool específica
mcp-datadog-server show-schema create_monitorValidar Configuração
# Validar tudo
mcp-datadog-server validate
# Ver configuração resumida
mcp-datadog-server validate --jsonTestar Conectividade
# Analisar schema carregado
mcp-datadog-server analyze-schema
# Testar servidor básico
timeout 5s mcp-datadog-server serveLogs e Debugging
# O servidor gera logs estruturados:
[2025-01-20T10:30:00.000Z] [INFO] Starting server with config: {...}
[2025-01-20T10:30:01.000Z] [INFO] Registered 9 curated tools
[2025-01-20T10:30:02.000Z] [INFO] Registered 25 CRUD tools
[2025-01-20T10:30:03.000Z] [INFO] Registered 319 generated tools
[2025-01-20T10:30:04.000Z] [INFO] Registered 351 tools total🚨 Solução de Problemas Comuns
1. "Tool não encontrada"
# Verificar se a tool existe
mcp-datadog-server list-tools --detailed | grep nome_da_tool
# Ver todas as categorias disponíveis
mcp-datadog-server analyze-schema2. "API Key inválida"
# Validar credenciais
mcp-datadog-server validate
# Verificar variáveis de ambiente
echo $DD_API_KEY
echo $DD_APP_KEY3. "Schema não carregado"
# Verificar se o schema existe
mcp-datadog-server analyze-schema
# Forçar recarregamento
rm -f datadog-api-collection-schema.json
mcp-datadog-server serve4. "Muitas tools carregadas"
# Filtrar apenas categorias necessárias
export MCP_DD_FOLDERS="Dashboards,Monitors,Logs"
mcp-datadog-server list-tools📈 Performance e Limites
Rate Limiting
✅ Automático - Respeita headers
retry-after✅ Configurável - Ajuste via
MCP_DD_MAX_RETRIES✅ Inteligente - Backoff exponencial
Timeouts
✅ Padrão: 30 segundos por requisição
✅ Configurável via
MCP_DD_TIMEOUT_MS✅ Progress Tracking para operações longas
Memory Usage
✅ Otimizado - Schema carregado uma vez na inicialização
✅ Streaming - Não mantém responses grandes em memória
✅ Filtros - Use
MCP_DD_FOLDERSpara reduzir footprint
🔐 Segurança
Credentials
✅ Environment Only - Chaves apenas via variáveis de ambiente
✅ No Logging - Credentials nunca aparecem em logs
✅ Validation - Formato das chaves validado na inicialização
Network
✅ TLS Only - Todas as chamadas via HTTPS
✅ Corporate Proxy - Suporte via
NODE_EXTRA_CA_CERTS✅ Headers Security - User-Agent e headers apropriados
Input Validation
✅ Zod Schemas - Validação rigorosa de entrada
✅ Sanitization - Limpeza automática de inputs
✅ Type Safety - TypeScript + runtime validation
📊 Monitoramento
Health Checks
# Status do servidor
mcp-datadog-server validate
# Análise das tools
mcp-datadog-server list-tools --json | jq '.total'Metrics Disponíveis
✅ Tools Count - Total de tools carregadas
✅ API Calls - Tracking de chamadas por tool
✅ Error Rate - Rate de erros por categoria
✅ Response Time - Tempos de resposta médios
🎓 Exemplos Práticos
Criar Monitor de CPU
O LLM pode automaticamente executar:
await use_tool("create_monitor", {
name: "High CPU Alert",
type: "metric alert",
query: "avg(last_5m):avg:system.cpu.user{*} > 0.9",
message: "CPU high @ops-team"
});Listar Dashboards Filtrados
await use_tool("list_dashboard", {
filter_shared: false,
count: 50
});Criar Downtime para Manutenção
await use_tool("create_downtime", {
scope: ["host:web-server-01"],
start: Math.floor(Date.now() / 1000),
end: Math.floor(Date.now() / 1000) + 3600,
message: "Planned maintenance window"
});📚 Documentação Adicional
🔍 SCHEMA_DISCOVERY.md - Como o LLM descobre parâmetros
📋 REFACTOR_CHECKPOINT.md - Histórico da refatoração
⚙️ TOOLS.md - Documentação completa das tools
🤝 Contribuição
Reportar Bugs
# Gerar relatório de debug
mcp-datadog-server validate --json > debug-info.json
mcp-datadog-server list-tools --json >> debug-info.jsonAdicionar Tools Curadas
Edite
src/tools/curated-tools.jsAdicione schema Zod completo
Implemente função
executeTeste com
npm test
Melhorar Tools CRUD
Edite
src/tools/crud-tools.jsAdicione novos recursos ao
DATADOG_RESOURCESDefina schemas e operações
Teste todas as operações CRUD
📝 Changelog
v0.3.0 - Current
✅ 351 tools (9 curadas + 25 CRUD + 319 geradas)
✅ CRUD completo para recursos principais
✅ Schema autodescoberta via MCP
✅ Progress tracking para operações longas
✅ CLI rica com comandos de debugging
✅ 100% conformidade com padrões MCP
v0.2.x - Previous
✅ Refatoração completa da arquitetura
✅ Validação robusta com Zod
✅ Cliente HTTP com retry automático
✅ Sistema de configuração limpo
📄 Licença
Apache License 2.0 - Veja LICENSE para detalhes.
🙏 Agradecimentos
Model Context Protocol - Framework base
Datadog - APIs e documentação
Zod - Schema validation
Undici - HTTP client
🎉 Pronto para usar com qualquer LLM compatível com MCP!
Para suporte e discussões, veja as Issues do repositório.
Available Tools
670 toolsaggregate_ci_pipelines_analyticsB
Use this API endpoint to aggregate CI Visibility pipeline events into buckets of computed metrics and timeseries.
Inputs: no named parameters.
aggregate_ci_tests_analyticsB
The API endpoint to aggregate CI Visibility test events into buckets of computed metrics and timeseries.
Inputs: no named parameters.
aggregate_logs_analyticsC
The API endpoint to aggregate events into buckets and compute metrics and timeseries.
Inputs: no named parameters.
aggregate_network_connectionsB
Get all aggregated connections.
Inputs: no named parameters.
aggregate_network_dnsC
Get all aggregated DNS traffic.
Inputs: no named parameters.
aggregate_rum_analyticsB
The API endpoint to aggregate RUM events into buckets of computed metrics and timeseries.
Inputs: no named parameters.
aggregate_spans_analyticsB
The API endpoint to aggregate spans into buckets and compute metrics and timeseries.
This endpoint is rate limited to 300 requests per hour.
Inputs: no named parameters.
can_delete_monitorsB
Check if the given monitors can be deleted.
Inputs: no named parameters.
can_delete_slosA
Check if an SLO can be safely deleted. For example, assure an SLO can be deleted without disrupting a dashboard.
Inputs: no named parameters.
create_actions_connectionsB
Create a new Action Connection. This API requires a registered application key.
Inputs: no named parameters.
create_agentless_scanning_accounts_awsB
Activate Agentless scan options for an AWS account.
Inputs: no named parameters.
create_agentless_scanning_ondemand_awsB
Trigger the scan of an AWS resource with a high priority. Agentless scanning must be activated for the AWS account containing the resource to scan.
Inputs: no named parameters.
create_api_keysC
Create an API key.
Inputs: no named parameters.
create_apm_config_metricsB
Create a metric based on your ingested spans in your organization. Returns the span-based metric object from the request body when the request is successful.
Inputs: no named parameters.
create_apm_config_retention_filtersB
Create a retention filter to index spans in your organization. Returns the retention filter definition when the request is successful.
Inputs: no named parameters.
create_app_builder_app_deploymentA
Publish an app for use by other users. To ensure the app is accessible to the correct users, you also need to set a Restriction Policy on the app if a policy does not yet exist.
Inputs: no named parameters.
create_app_builder_appsB
Create a new app, returning the app ID.
Inputs: no named parameters.
create_application_keysB
Create an application key with a given name.
Inputs: no named parameters.
create_authn_mappingsC
Create an AuthN Mapping.
Inputs: no named parameters.
create_case_archiveC
Archive case
Inputs: no named parameters.
create_case_assignC
Assign case to a user
Inputs: no named parameters.
create_case_attributesC
Update case attributes
Inputs: no named parameters.
create_case_priorityC
Update case priority
Inputs: no named parameters.
create_casesC
Create a Case
Inputs: no named parameters.
create_cases_projectsC
Create a project.
Inputs: no named parameters.
create_case_statusD
Update case status
Inputs: no named parameters.
create_case_unarchiveC
Unarchive case
Inputs: no named parameters.
create_case_unassignC
Unassign case
Inputs: no named parameters.
create_catalog_entitiesB
Create or update entities in Software Catalog.
Inputs: no named parameters.
create_catalog_kindsC
Create or update kinds in Software Catalog.
Inputs: no named parameters.
create_check_runsB
Submit a list of Service Checks.
Notes:
A valid API key is required.
Service checks can be submitted up to 10 minutes in the past.
Inputs: no named parameters.
create_ci_pipelinesA
Send your pipeline event to your Datadog platform over HTTP. For details about how pipeline executions are modeled and what execution types we support, see Pipeline Data Model And Execution Types.
Pipeline events can be submitted with a timestamp that is up to 18 hours in the past.
Inputs: no named parameters.
create_cloud_security_management_custom_frameworksC
Create a custom framework.
Inputs: no named parameters.
create_cost_aws_cur_configsB
Create a Cloud Cost Management account for an AWS CUR config.
Inputs: no named parameters.
create_cost_azure_uc_configsB
Create a Cloud Cost Management account for an Azure config.
Inputs: no named parameters.
create_cost_gcp_uc_configsB
Create a Cloud Cost Management account for an GCP Usage Cost config.
Inputs: no named parameters.
create_current_user_application_keysC
Create an application key for current user
Inputs: no named parameters.
create_dashboard_lists_manual_dashboardsB
Add dashboards to an existing dashboard list.
Inputs: no named parameters.
create_dashboard_lists_manualsB
Create an empty dashboard list.
Inputs: no named parameters.
create_dashboard_public_invitationA
Send emails to specified email addresses containing links to access a given authenticated shared dashboard. Email addresses must already belong to the authenticated shared dashboard's share_list.
Inputs: no named parameters.
create_dashboard_publicsB
Share a specified private dashboard, generating a URL at which it can be publicly viewed.
Inputs: no named parameters.
create_dashboardsC
Create a dashboard using the specified options. When defining queries in your widgets, take note of which queries should have the as_count() or as_rate() modifiers appended.
Refer to the following documentation for more information on these modifiers.
Inputs: no named parameters.
create_dashboard_v1C
Create a dashboard
Inputs: no named parameters.
create_dora_deployments_v2C
Use this API endpoint to provide data about deployments for DORA metrics.
This is necessary for:
Deployment Frequency
Change Lead Time
Change Failure Rate
Inputs: no named parameters.
create_dora_deployments_v2_2C
Use this API endpoint to get a list of deployment events.
Inputs: no named parameters.
create_dora_failures_v2B
Use this API endpoint to provide failure data for DORA metrics.
This is necessary for:
Change Failure Rate
Time to Restore
Inputs: no named parameters.
create_dora_failures_v2_2C
Use this API endpoint to get a list of failure events.
Inputs: no named parameters.
create_downtimesC
Schedule a downtime.
Inputs: no named parameters.
create_eventsC
This endpoint allows you to post events to the stream. Tag them, set priority and event aggregate them with other events.
Inputs: no named parameters.
create_graph_embedsA
Creates a new embeddable graph.
Note: If an embed already exists for the exact same query in a given organization, the older embed is returned instead of creating a new embed.
If you are interested in using template variables, see Embeddable Graphs with Template Variables.
Inputs: no named parameters.
create_integration_awsB
Create a Datadog-Amazon Web Services integration.
Using the POST method updates your integration configuration
by adding your new configuration to the existing one in your Datadog organization.
A unique AWS Account ID for role based authentication.
Inputs: no named parameters.
create_integration_aws_event_bridgesB
Create an Amazon EventBridge source.
Inputs: no named parameters.
create_integration_aws_filteringsB
Set an AWS tag filter.
Inputs: no named parameters.
create_integration_aws_logsB
Attach the Lambda ARN of the Lambda created for the Datadog-AWS log collection to your AWS account ID to enable log collection.
Inputs: no named parameters.
create_integration_aws_logs_check_asyncsA
Test if permissions are present to add a log-forwarding triggers for the given services and AWS account. The input is the same as for Enable an AWS service log collection. Subsequent requests will always repeat the above, so this endpoint can be polled intermittently instead of blocking.
Returns a status of 'created' when it's checking if the Lambda exists in the account.
Returns a status of 'waiting' while checking.
Returns a status of 'checked and ok' if the Lambda exists.
Returns a status of 'error' if the Lambda does not exist.
Inputs: no named parameters.
create_integration_aws_logs_servicesA
Enable automatic log collection for a list of services. This should be run after running CreateAWSLambdaARN to save the configuration.
Inputs: no named parameters.
create_integration_aws_logs_services_asyncsA
Test if permissions are present to add log-forwarding triggers for the
given services and AWS account. Input is the same as for EnableAWSLogServices.
Done async, so can be repeatedly polled in a non-blocking fashion until
the async request completes.
Returns a status of
createdwhen it's checking if the permissions exists in the AWS account.Returns a status of
waitingwhile checking.Returns a status of
checked and okif the Lambda exists.Returns a status of
errorif the Lambda does not exist.
Inputs: no named parameters.
create_integration_azure_host_filtersB
Update the defined list of host filters for a given Datadog-Azure integration.
Inputs: no named parameters.
create_integration_azuresA
Create a Datadog-Azure integration.
Using the POST method updates your integration configuration by adding your new
configuration to the existing one in your Datadog organization.
Using the PUT method updates your integration configuration by replacing your
current configuration with the new one sent to your Datadog organization.
Inputs: no named parameters.
create_integration_gcp_accountsB
Create a new entry within Datadog for your STS enabled service account.
Inputs: no named parameters.
create_integration_gcp_sts_delegatesB
Create a Datadog GCP principal.
Inputs: no named parameters.
create_integration_ms_teams_configuration_tenant_based_handlesB
Create a tenant-based handle in the Datadog Microsoft Teams integration.
Inputs: no named parameters.
create_integration_ms_teams_configuration_workflows_webhook_handlesB
Create a Workflows webhook handle in the Datadog Microsoft Teams integration.
Inputs: no named parameters.
create_integration_opsgenie_servicesB
Create a new service object in the Opsgenie integration.
Inputs: no named parameters.
create_integration_pagerduty_configuration_servicesB
Create a new service object in the PagerDuty integration.
Inputs: no named parameters.
create_integrations_cloudflare_accountsC
Create a Cloudflare account.
Inputs: no named parameters.
create_integrations_confluent_cloud_account_resourcesC
Create a Confluent resource for the account associated with the provided ID.
Inputs: no named parameters.
create_integrations_confluent_cloud_accountsC
Create a Confluent account.
Inputs: no named parameters.
create_integrations_fastly_accountsC
Create a Fastly account.
Inputs: no named parameters.
create_integrations_fastly_account_servicesC
Create a Fastly service for an account.
Inputs: no named parameters.
create_integration_slack_configuration_account_channelsB
Add a channel to your Datadog-Slack integration.
Inputs: no named parameters.
create_integrations_okta_accountsC
Create an Okta account.
Inputs: no named parameters.
create_integration_webhooks_configuration_custom_variablesC
Creates an endpoint with the name <CUSTOM_VARIABLE_NAME>.
Inputs: no named parameters.
create_integration_webhooks_configuration_webhooksC
Creates an endpoint with the name <WEBHOOK_NAME>.
Inputs: no named parameters.
create_logs_config_archive_readersB
Adds a read role to an archive. (Roles API)
Inputs: no named parameters.
create_logs_config_archivesC
Create an archive in your organization.
Inputs: no named parameters.
create_logs_config_custom_destinationsB
Create a custom destination in your organization.
Inputs: no named parameters.
create_logs_config_indexesB
Creates a new index. Returns the Index object passed in the request body when the request is successful.
Inputs: no named parameters.
create_logs_config_metricsB
Create a metric based on your ingested logs in your organization. Returns the log-based metric object from the request body when the request is successful.
Inputs: no named parameters.
create_logs_config_pipelinesC
Create a pipeline in your organization.
Inputs: no named parameters.
create_metrics_config_bulk_tagsA
Create and define a list of queryable tag keys for a set of existing count, gauge, rate, and distribution metrics.
Metrics are selected by passing a metric name prefix. Use the Delete method of this API path to remove tag configurations.
Results can be sent to a set of account email addresses, just like the same operation in the Datadog web app.
If multiple calls include the same metric, the last configuration applied (not by submit order) is used, do not
expect deterministic ordering of concurrent calls. The exclude_tags_mode value will set all metrics that match the prefix to
the same exclusion state, metric tag configurations do not support mixed inclusion and exclusion for tags on the same metric.
Can only be used with application keys of users with the Manage Tags for Metrics permission.
Inputs: no named parameters.
create_metric_tagsA
Create and define a list of queryable tag keys for an existing count/gauge/rate/distribution metric.
Optionally, include percentile aggregations on any distribution metric. By setting exclude_tags_mode
to true, the behavior is changed from an allow-list to a deny-list, and tags in the defined list are
not queryable. Can only be used with application keys of users with the Manage Tags for Metrics
permission.
Inputs: no named parameters.
create_monitorA
Create a monitor using the specified options.
Monitor Types
The type of monitor chosen from:
anomaly:
query alertAPM:
query alertortrace-analytics alertcomposite:
compositecustom:
service checkforecast:
query alerthost:
service checkintegration:
query alertorservice checklive process:
process alertlogs:
log alertmetric:
query alertnetwork:
service checkoutlier:
query alertprocess:
service checkrum:
rum alertSLO:
slo alertwatchdog:
event-v2 alertevent-v2:
event-v2 alertaudit:
audit alerterror-tracking:
error-tracking alertdatabase-monitoring:
database-monitoring alertnetwork-performance:
network-performance alertcloud cost:
cost alert
Notes:
Synthetic monitors are created through the Synthetics API. See the Synthetics API documentation for more information.
Log monitors require an unscoped App Key.
Query Types
Metric Alert Query
Example: time_aggr(time_window):space_aggr:metric{tags} [by {key}] operator #
time_aggr: avg, sum, max, min, change, or pct_changetime_window:last_#m(with#between 1 and 10080 depending on the monitor type) orlast_#h(with#between 1 and 168 depending on the monitor type) orlast_1d, orlast_1wspace_aggr: avg, sum, min, or maxtags: one or more tags (comma-separated), or *key: a 'key' in key:value tag syntax; defines a separate alert for each tag in the group (multi-alert)operator: <, <=, >, >=, ==, or !=#: an integer or decimal number used to set the threshold
If you are using the _change_ or _pct_change_ time aggregator, instead use change_aggr(time_aggr(time_window), timeshift):space_aggr:metric{tags} [by {key}] operator # with:
change_aggrchange, pct_changetime_aggravg, sum, max, min Learn moretime_windowlast_#m (between 1 and 2880 depending on the monitor type), last_#h (between 1 and 48 depending on the monitor type), or last_#d (1 or 2)timeshift#m_ago (5, 10, 15, or 30), #h_ago (1, 2, or 4), or 1d_ago
Use this to create an outlier monitor using the following query:
avg(last_30m):outliers(avg:system.cpu.user{role:es-events-data} by {host}, 'dbscan', 7) > 0
Service Check Query
Example: "check".over(tags).last(count).by(group).count_by_status()
checkname of the check, for exampledatadog.agent.uptagsone or more quoted tags (comma-separated), or "*". for example:.over("env:prod", "role:db");overcannot be blank.countmust be at greater than or equal to your max threshold (defined in theoptions). It is limited to 100. For example, if you've specified to notify on 1 critical, 3 ok, and 2 warn statuses,countshould be at least 3.groupmust be specified for check monitors. Per-check grouping is already explicitly known for some service checks. For example, Postgres integration monitors are tagged bydb,host, andport, and Network monitors byhost,instance, andurl. See Service Checks documentation for more information.
Event Alert Query
Note: The Event Alert Query has been replaced by the Event V2 Alert Query. For more information, see the Event Migration guide.
Event V2 Alert Query
Example: events(query).rollup(rollup_method[, measure]).last(time_window) operator #
queryThe search query - following the Log search syntax.rollup_methodThe stats roll-up method - supportscount,avgandcardinality.measureForavgand cardinalityrollup_method- specify the measure or the facet name you want to use.time_window#m (between 1 and 2880), #h (between 1 and 48).operator<,<=,>,>=,==, or!=.#an integer or decimal number used to set the threshold.
Process Alert Query
Example: processes(search).over(tags).rollup('count').last(timeframe) operator #
searchfree text search string for querying processes. Matching processes match results on the Live Processes page.tagsone or more tags (comma-separated)timeframethe timeframe to roll up the counts. Examples: 10m, 4h. Supported timeframes: s, m, h and doperator<, <=, >, >=, ==, or !=#an integer or decimal number used to set the threshold
Logs Alert Query
Example: logs(query).index(index_name).rollup(rollup_method[, measure]).last(time_window) operator #
queryThe search query - following the Log search syntax.index_nameFor multi-index organizations, the log index in which the request is performed.rollup_methodThe stats roll-up method - supportscount,avgandcardinality.measureForavgand cardinalityrollup_method- specify the measure or the facet name you want to use.time_window#m (between 1 and 2880), #h (between 1 and 48).operator<,<=,>,>=,==, or!=.#an integer or decimal number used to set the threshold.
Composite Query
Example: 12345 && 67890, where 12345 and 67890 are the IDs of non-composite monitors
name[required, default = dynamic, based on query]: The name of the alert.message[required, default = dynamic, based on query]: A message to include with notifications for this monitor. Email notifications can be sent to specific users by using the same '@username' notation as events.tags[optional, default = empty list]: A list of tags to associate with your monitor. When getting all monitor details via the API, use themonitor_tagsargument to filter results by these tags. It is only available via the API and isn't visible or editable in the Datadog UI.
SLO Alert Query
Example: error_budget("slo_id").over("time_window") operator #
slo_id: The alphanumeric SLO ID of the SLO you are configuring the alert for.time_window: The time window of the SLO target you wish to alert on. Valid options:7d,30d,90d.operator:>=or>
Audit Alert Query
Example: audits(query).rollup(rollup_method[, measure]).last(time_window) operator #
queryThe search query - following the Log search syntax.rollup_methodThe stats roll-up method - supportscount,avgandcardinality.measureForavgand cardinalityrollup_method- specify the measure or the facet name you want to use.time_window#m (between 1 and 2880), #h (between 1 and 48).operator<,<=,>,>=,==, or!=.#an integer or decimal number used to set the threshold.
CI Pipelines Alert Query
Example: ci-pipelines(query).rollup(rollup_method[, measure]).last(time_window) operator #
queryThe search query - following the Log search syntax.rollup_methodThe stats roll-up method - supportscount,avg, andcardinality.measureForavgand cardinalityrollup_method- specify the measure or the facet name you want to use.time_window#m (between 1 and 2880), #h (between 1 and 48).operator<,<=,>,>=,==, or!=.#an integer or decimal number used to set the threshold.
CI Tests Alert Query
Example: ci-tests(query).rollup(rollup_method[, measure]).last(time_window) operator #
queryThe search query - following the Log search syntax.rollup_methodThe stats roll-up method - supportscount,avg, andcardinality.measureForavgand cardinalityrollup_method- specify the measure or the facet name you want to use.time_window#m (between 1 and 2880), #h (between 1 and 48).operator<,<=,>,>=,==, or!=.#an integer or decimal number used to set the threshold.
Error Tracking Alert Query
"New issue" example: error-tracking(query).source(issue_source).new().rollup(rollup_method[, measure]).by(group_by).last(time_window) operator #
"High impact issue" example: error-tracking(query).source(issue_source).impact().rollup(rollup_method[, measure]).by(group_by).last(time_window) operator #
queryThe search query - following the Log search syntax.issue_sourceThe issue source - supportsall,browser,mobileandbackendand defaults toallif omitted.rollup_methodThe stats roll-up method - supportscount,avg, andcardinalityand defaults tocountif omitted.measureForavgand cardinalityrollup_method- specify the measure or the facet name you want to use.group byComma-separated list of attributes to group by - should contain at leastissue.id.time_window#m (between 1 and 2880), #h (between 1 and 48).operator<,<=,>,>=,==, or!=.#an integer or decimal number used to set the threshold.
Database Monitoring Alert Query
Example: database-monitoring(query).rollup(rollup_method[, measure]).last(time_window) operator #
queryThe search query - following the Log search syntax.rollup_methodThe stats roll-up method - supportscount,avg, andcardinality.measureForavgand cardinalityrollup_method- specify the measure or the facet name you want to use.time_window#m (between 1 and 2880), #h (between 1 and 48).operator<,<=,>,>=,==, or!=.#an integer or decimal number used to set the threshold.
Network Performance Alert Query
Example: network-performance(query).rollup(rollup_method[, measure]).last(time_window) operator #
queryThe search query - following the Log search syntax.rollup_methodThe stats roll-up method - supportscount,avg, andcardinality.measureForavgand cardinalityrollup_method- specify the measure or the facet name you want to use.time_window#m (between 1 and 2880), #h (between 1 and 48).operator<,<=,>,>=,==, or!=.#an integer or decimal number used to set the threshold.
Cost Alert Query
Example: formula(query).timeframe_type(time_window).function(parameter) operator #
queryThe search query - following the Log search syntax.timeframe_typeThe timeframe type to evaluate the cost - forforecastsupportscurrent- forchange,anomaly,thresholdsupportslasttime_window- supports daily roll-up e.g.7dfunction- [optional, defaults tothresholdmonitor if omitted] supportschange,anomaly,forecastparameterSpecify the parameter of the typefor
change:supports
relative,absolute[optional] supports
#, where#is an integer or decimal number used to set the threshold
for
anomaly:supports
direction=both,direction=above,direction=below[optional] supports
threshold=#, where#is an integer or decimal number used to set the threshold
operatorfor
thresholdsupports<,<=,>,>=,==, or!=for
changesupports>,<for
anomalysupports>=for
forecastsupports>
#an integer or decimal number used to set the threshold.
Inputs: no named parameters.
create_monitor_notification_rulesC
Creates a monitor notification rule.
Inputs: no named parameters.
create_monitor_policiesB
Create a monitor configuration policy.
Inputs: no named parameters.
create_monitor_v1D
Create a monitor
Inputs: no named parameters.
create_notebooksC
Create a notebook using the specified options.
Inputs: no named parameters.
create_on_call_escalation_policiesB
Create a new on-call escalation policy
Inputs: no named parameters.
create_on_call_schedulesC
Create a new on-call schedule
Inputs: no named parameters.
create_org_downgradeA
Only available for MSP customers. Removes a child organization from the hierarchy of the master organization and places the child organization on a 30-day trial.
Inputs: no named parameters.
create_orgsA
Create a child organization.
This endpoint requires the multi-organization account feature and must be enabled by contacting support.
Once a new child organization is created, you can interact with it
by using the org.public_id, api_key.key, and
application_key.hash provided in the response.
Inputs: no named parameters.
create_powerpacksC
Create a powerpack.
Inputs: no named parameters.
create_remote_config_products_asm_waf_custom_rulesB
Create a new WAF custom rule with the given parameters.
Inputs: no named parameters.
create_remote_config_products_asm_waf_exclusion_filtersA
Create a new WAF exclusion filter with the given parameters.
A request matched by an exclusion filter will be ignored by the Application Security WAF product. Go to https://app.datadoghq.com/security/appsec/passlist to review existing exclusion filters (also called passlist entries).
Inputs: no named parameters.
create_remote_config_products_cws_agent_rulesB
Create a new Workload Protection agent rule with the given parameters.
Note: This endpoint is not available for the Government (US1-FED) site. Please reference the (US1-FED) specific resource below.
Inputs: no named parameters.
create_remote_config_products_cws_policiesB
Create a new Workload Protection policy with the given parameters.
Note: This endpoint is not available for the Government (US1-FED) site. Please reference the (US1-FED) specific resource below.
Inputs: no named parameters.
create_restriction_policyA
Updates the restriction policy associated with a resource.
Supported resources
Restriction policies can be applied to the following resources:
Connections:
connectionDashboards:
dashboardNotebooks:
notebookSecurity Rules:
security-ruleService Level Objectives:
slo
Supported relations for resources
Resource Type | Supported Relations |
Connections |
|
Dashboards |
|
Notebooks |
|
Security Rules |
|
Service Level Objectives |
|
Inputs: no named parameters.
create_role_cloneC
Clone an existing role
Inputs: no named parameters.
create_role_permissionsC
Adds a permission to a role.
Inputs: no named parameters.
create_rolesB
Create a new role for your organization.
Inputs: no named parameters.
create_role_usersB
Adds a user to a role.
Inputs: no named parameters.
create_rum_application_retention_filtersB
Create a RUM retention filter for a RUM application. Returns RUM retention filter objects from the request body when the request is successful.
Inputs: no named parameters.
create_rum_applicationsB
Create a new RUM application in your organization.
Inputs: no named parameters.
create_rum_config_metricsC
Create a metric based on your organization's RUM data. Returns the rum-based metric object from the request body when the request is successful.
Inputs: no named parameters.
create_saml_configurations_idp_metadatasB
Endpoint for uploading IdP metadata for SAML setup.
Use this endpoint to upload or replace IdP metadata for SAML login configuration.
Inputs: no named parameters.
create_security_monitoring_cloud_workload_security_agent_rulesC
Create a new agent rule with the given parameters.
Note: This endpoint should only be used for the Government (US1-FED) site.
Inputs: no named parameters.
create_security_monitoring_configuration_security_filtersC
Create a security filter.
See the security filter guide for more examples.
Inputs: no named parameters.
create_security_monitoring_configuration_suppressionsC
Create a new suppression rule.
Inputs: no named parameters.
create_security_monitoring_configuration_suppressions_rulesC
Get the list of suppressions that would affect a rule.
Inputs: no named parameters.
create_security_monitoring_configuration_suppressions_validationsC
Validate a suppression rule.
Inputs: no named parameters.
create_security_monitoring_rulesC
Create a detection rule.
Inputs: no named parameters.
create_security_monitoring_rules_convertsC
Convert a rule that doesn't (yet) exist from JSON to Terraform for datadog provider resource datadog_security_monitoring_rule.
Inputs: no named parameters.
create_security_monitoring_rules_testsD
Test a rule.
Inputs: no named parameters.
create_security_monitoring_rules_validationsC
Validate a detection rule.
Inputs: no named parameters.
create_security_monitoring_rule_testD
Test an existing rule.
Inputs: no named parameters.
create_security_signals_notification_rulesB
Create a new notification rule for security signals and return the created rule.
Inputs: no named parameters.
create_security_vulnerabilities_notification_rulesB
Create a new notification rule for security vulnerabilities and return the created rule.
Inputs: no named parameters.
create_sensitive_data_scanner_config_groupsA
Create a scanning group. The request MAY include a configuration relationship. A rules relationship can be omitted entirely, but if it is included it MUST be null or an empty array (rules cannot be created at the same time). The new group will be ordered last within the configuration.
Inputs: no named parameters.
create_sensitive_data_scanner_config_rulesA
Create a scanning rule in a sensitive data scanner group, ordered last. The posted rule MUST include a group relationship. It MUST include either a standard_pattern relationship or a regex attribute, but not both. If included_attributes is empty or missing, we will scan all attributes except excluded_attributes. If both are missing, we will scan the whole event.
Inputs: no named parameters.
create_service_account_application_keysB
Create an application key for this service account.
Inputs: no named parameters.
create_service_accountsB
Create a service account for your organization.
Inputs: no named parameters.
create_services_definitionsB
Create or update service definition in the Datadog Service Catalog.
Inputs: no named parameters.
create_slo_bulk_deletesB
Delete (or partially delete) multiple service level objective objects.
This endpoint facilitates deletion of one or more thresholds for one or more service level objective objects. If all thresholds are deleted, the service level objective object is deleted as well.
Inputs: no named parameters.
create_slo_correctionsC
Create an SLO Correction.
Inputs: no named parameters.
create_slosC
Create a service level objective object.
Inputs: no named parameters.
create_synthetics_private_locationsB
Create a new Synthetic private location.
Inputs: no named parameters.
create_synthetics_settings_on_demand_concurrency_capsB
Save new value for on-demand concurrency cap.
Inputs: no named parameters.
create_synthetics_testsC
Create a Synthetic API test.
Inputs: no named parameters.
create_synthetics_tests_browsersC
Create a Synthetic browser test.
Inputs: no named parameters.
create_synthetics_tests_deletesB
Delete multiple Synthetic tests by ID.
Inputs: no named parameters.
create_synthetics_tests_mobilesC
Create a Synthetic mobile test.
Inputs: no named parameters.
create_synthetics_tests_trigger_cisB
Trigger a set of Synthetic tests for continuous integration.
Inputs: no named parameters.
create_synthetics_tests_triggersC
Trigger a set of Synthetic tests.
Inputs: no named parameters.
create_synthetics_tests_uptimesB
Fetch uptime for multiple Synthetic tests by ID.
Inputs: no named parameters.
create_synthetics_variablesB
Create a Synthetic global variable.
Inputs: no named parameters.
create_tags_hostC
This endpoint allows you to add new tags to a host, optionally specifying where these tags come from.
Inputs: no named parameters.
create_team_linksC
Add a new link to a team.
Inputs: no named parameters.
create_team_membershipsB
Add a user to a team.
Inputs: no named parameters.
create_teamsB
Create a new team.
User IDs passed through the users relationship field are added to the team.
Inputs: no named parameters.
create_user_invitationsB
Sends emails to one or more users inviting them to join the organization.
Inputs: no named parameters.
create_usersB
Create a user for your organization.
Inputs: no named parameters.
create_workflow_instancesB
Execute the given workflow. This API requires a registered application key.
Inputs: no named parameters.
create_workflowsB
Create a new workflow, returning the workflow ID. This API requires a registered application key.
Inputs: no named parameters.
delete_actions_app_key_registrationC
Unregister an App Key
Inputs: no named parameters.
delete_actions_connectionB
Delete an existing Action Connection. This API requires a registered application key. Alternatively, you can configure these permissions in the UI.
Inputs: no named parameters.
delete_agentless_scanning_accounts_awB
Delete Agentless scan options for an AWS account.
Inputs: no named parameters.
delete_api_keyC
Delete an API key.
Inputs: no named parameters.
delete_apm_config_metricB
Delete a specific span-based metric from your organization.
Inputs: no named parameters.
delete_apm_config_retention_filterB
Delete a specific retention filter from your organization.
Inputs: no named parameters.
delete_app_builder_appC
Delete a single app.
Inputs: no named parameters.
delete_app_builder_app_deploymentA
Unpublish an app, removing the live version of the app. Unpublishing creates a new instance of a deployment object on the app, with a nil app_version_id (00000000-0000-0000-0000-000000000000). The app can still be updated and published again in the future.
Inputs: no named parameters.
delete_app_builder_appsB
Delete multiple apps in a single request from a list of app IDs.
Inputs: no named parameters.
delete_application_keyC
Delete an application key
Inputs: no named parameters.
delete_authn_mappingB
Delete an AuthN Mapping specified by AuthN Mapping UUID.
Inputs: no named parameters.
delete_cases_projectB
Remove a project using the project's id.
Inputs: no named parameters.
delete_catalog_entityB
Delete a single entity in Software Catalog.
Inputs: no named parameters.
delete_catalog_kindB
Delete a single kind in Software Catalog.
Inputs: no named parameters.
delete_cloud_security_management_custom_frameworkB
Delete a custom framework.
Inputs: no named parameters.
delete_cost_aws_cur_configB
Archive a Cloud Cost Management Account.
Inputs: no named parameters.
delete_cost_azure_uc_configB
Archive a Cloud Cost Management Account.
Inputs: no named parameters.
delete_cost_budgetC
Delete a budget.
Inputs: no named parameters.
delete_cost_custom_costB
Delete the specified Custom Costs file.
Inputs: no named parameters.
delete_cost_gcp_uc_configC
Archive a Cloud Cost Management account.
Inputs: no named parameters.
delete_current_user_application_keyB
Delete an application key owned by current user
Inputs: no named parameters.
delete_dashboardB
Delete a dashboard using the specified ID.
Inputs: no named parameters.
delete_dashboard_lists_manualB
Delete a dashboard list.
Inputs: no named parameters.
delete_dashboard_lists_manual_dashboardsB
Delete dashboards from an existing dashboard list.
Inputs: no named parameters.
delete_dashboard_publicB
Revoke the public URL for a dashboard (rendering it private) associated with the specified token.
Inputs: no named parameters.
delete_dashboard_public_invitationB
Revoke previously sent invitation emails and active sessions used to access a given shared dashboard for specific email addresses.
Inputs: no named parameters.
delete_dashboardsB
Delete dashboards using the specified IDs. If there are any failures, no dashboards will be deleted (partial success is not allowed).
Inputs: no named parameters.
delete_dashboard_v1C
Delete a dashboard
Inputs: no named parameters.
delete_downtimeB
Cancel a downtime.
Inputs: no named parameters.
delete_integration_awsB
Delete a Datadog-AWS integration matching the specified account_id and role_name parameters.
Inputs: no named parameters.
delete_integration_aws_event_bridgesB
Delete an Amazon EventBridge source.
Inputs: no named parameters.
delete_integration_aws_filteringsB
Delete a tag filtering entry.
Inputs: no named parameters.
delete_integration_aws_logsB
Delete a Datadog-AWS logs configuration by removing the specific Lambda ARN associated with a given AWS account.
Inputs: no named parameters.
delete_integration_azuresB
Delete a given Datadog-Azure integration from your Datadog account.
Inputs: no named parameters.
delete_integration_gcp_accountB
Delete an STS enabled GCP account from within Datadog.
Inputs: no named parameters.
delete_integration_ms_teams_configuration_tenant_based_handleB
Delete a tenant-based handle from the Datadog Microsoft Teams integration.
Inputs: no named parameters.
delete_integration_ms_teams_configuration_workflows_webhook_handleB
Delete a Workflows webhook handle from the Datadog Microsoft Teams integration.
Inputs: no named parameters.
delete_integration_opsgenie_serviceB
Delete a single service object in the Datadog Opsgenie integration.
Inputs: no named parameters.
delete_integration_pagerduty_configuration_serviceB
Delete a single service object in the Datadog-PagerDuty integration.
Inputs: no named parameters.
delete_integrations_cloudflare_accountB
Delete a Cloudflare account.
Inputs: no named parameters.
delete_integrations_confluent_cloud_accountB
Delete a Confluent account with the provided account ID.
Inputs: no named parameters.
delete_integrations_confluent_cloud_account_resourcesB
Delete a Confluent resource with the provided resource id for the account associated with the provided account ID.
Inputs: no named parameters.
delete_integrations_fastly_accountB
Delete a Fastly account.
Inputs: no named parameters.
delete_integrations_fastly_account_servicesB
Delete a Fastly service for an account.
Inputs: no named parameters.
delete_integration_slack_configuration_account_channelsB
Remove a channel from your Datadog-Slack integration.
Inputs: no named parameters.
delete_integrations_okta_accountC
Delete an Okta account.
Inputs: no named parameters.
delete_integration_webhooks_configuration_custom_variableC
Deletes the endpoint with the name <CUSTOM_VARIABLE_NAME>.
Inputs: no named parameters.
delete_integration_webhooks_configuration_webhookB
Deletes the endpoint with the name <WEBHOOK NAME>.
Inputs: no named parameters.
delete_logs_config_archiveB
Delete a given archive from your organization.
Inputs: no named parameters.
delete_logs_config_archive_readersC
Removes a role from an archive. (Roles API)
Inputs: no named parameters.
delete_logs_config_custom_destinationB
Delete a specific custom destination in your organization.
Inputs: no named parameters.
delete_logs_config_indexeA
Delete an existing index from your organization. Index deletions are permanent and cannot be reverted. You cannot recreate an index with the same name as deleted ones.
Inputs: no named parameters.
delete_logs_config_metricB
Delete a specific log-based metric from your organization.
Inputs: no named parameters.
delete_logs_config_pipelineB
Delete a given pipeline from your organization. This endpoint takes no JSON arguments.
Inputs: no named parameters.
delete_metrics_config_bulk_tagsA
Delete all custom lists of queryable tag keys for a set of existing count, gauge, rate, and distribution metrics.
Metrics are selected by passing a metric name prefix.
Results can be sent to a set of account email addresses, just like the same operation in the Datadog web app.
Can only be used with application keys of users with the Manage Tags for Metrics permission.
Inputs: no named parameters.
delete_metric_tagsA
Deletes a metric's tag configuration. Can only be used with application
keys from users with the Manage Tags for Metrics permission.
Inputs: no named parameters.
delete_monitorC
Delete the specified monitor
Inputs: no named parameters.
delete_monitor_notification_ruleB
Deletes a monitor notification rule by rule_id.
Inputs: no named parameters.
delete_monitor_policyB
Delete a monitor configuration policy.
Inputs: no named parameters.
delete_monitor_v1D
Delete a monitor
Inputs: no named parameters.
delete_notebookB
Delete a notebook using the specified ID.
Inputs: no named parameters.
delete_on_call_escalation_policyB
Delete an on-call escalation policy
Inputs: no named parameters.
delete_on_call_scheduleB
Delete an on-call schedule
Inputs: no named parameters.
delete_powerpackC
Delete a powerpack.
Inputs: no named parameters.
delete_remote_config_products_asm_waf_custom_ruleB
Delete a specific WAF custom rule.
Inputs: no named parameters.
delete_remote_config_products_asm_waf_exclusion_filterB
Delete a specific WAF exclusion filter using its identifier.
Inputs: no named parameters.
delete_remote_config_products_cws_agent_ruleB
Delete a specific Workload Protection agent rule.
Note: This endpoint is not available for the Government (US1-FED) site. Please reference the (US1-FED) specific resource below.
Inputs: no named parameters.
delete_remote_config_products_cws_policyB
Delete a specific Workload Protection policy.
Note: This endpoint is not available for the Government (US1-FED) site. Please reference the (US1-FED) specific resource below.
Inputs: no named parameters.
delete_restriction_policyB
Deletes the restriction policy associated with a specified resource.
Inputs: no named parameters.
delete_roleB
Disables a role.
Inputs: no named parameters.
delete_role_permissionsB
Removes a permission from a role.
Inputs: no named parameters.
delete_role_usersB
Removes a user from a role.
Inputs: no named parameters.
delete_rum_applicationB
Delete an existing RUM application in your organization.
Inputs: no named parameters.
delete_rum_application_retention_filtersB
Delete a RUM retention filter for a RUM application.
Inputs: no named parameters.
delete_rum_config_metricB
Delete a specific rum-based metric from your organization.
Inputs: no named parameters.
delete_security_monitoring_cloud_workload_security_agent_ruleC
Delete a specific agent rule.
Note: This endpoint should only be used for the Government (US1-FED) site.
Inputs: no named parameters.
delete_security_monitoring_configuration_security_filterC
Delete a specific security filter.
Inputs: no named parameters.
delete_security_monitoring_configuration_suppressionC
Delete a specific suppression rule.
Inputs: no named parameters.
delete_security_monitoring_ruleB
Delete an existing rule. Default rules cannot be deleted.
Inputs: no named parameters.
delete_security_signals_notification_ruleB
Delete a notification rule for security signals.
Inputs: no named parameters.
delete_security_vulnerabilities_notification_ruleB
Delete a notification rule for security vulnerabilities.
Inputs: no named parameters.
delete_sensitive_data_scanner_config_groupC
Delete a given group.
Inputs: no named parameters.
delete_sensitive_data_scanner_config_ruleC
Delete a given rule.
Inputs: no named parameters.
delete_service_account_application_keysB
Delete an application key owned by this service account.
Inputs: no named parameters.
delete_services_definitionB
Delete a single service definition in the Datadog Service Catalog.
Inputs: no named parameters.
delete_sloA
Permanently delete the specified service level objective object.
If an SLO is used in a dashboard, the DELETE /v1/slo/ endpoint returns
a 409 conflict error because the SLO is referenced in a dashboard.
Inputs: no named parameters.
delete_slo_correctionB
Permanently delete the specified SLO correction object.
Inputs: no named parameters.
delete_synthetics_private_locationB
Delete a Synthetic private location.
Inputs: no named parameters.
delete_synthetics_variableC
Delete a Synthetic global variable.
Inputs: no named parameters.
delete_tags_hostB
This endpoint allows you to remove all user-assigned tags for a single host.
Inputs: no named parameters.
delete_teamB
Remove a team using the team's id.
Inputs: no named parameters.
delete_team_linksB
Remove a link from a team.
Inputs: no named parameters.
delete_team_membershipsB
Remove a user from a team.
Inputs: no named parameters.
delete_userB
Disable a user. Can only be used with an application key belonging to an administrator user.
Inputs: no named parameters.
delete_workflowB
Delete a workflow by ID. This API requires a registered application key.
Inputs: no named parameters.
downtimes_cancelD
Cancel downtime
Inputs: no named parameters.
downtimes_createC
Schedule downtime
Inputs: no named parameters.
downtimes_listC
List downtimes
Inputs: no named parameters.
estimate_metricB
Returns the estimated cardinality for a metric with a given tag, percentile and number of aggregations configuration using Metrics without Limits™.
Inputs: no named parameters.
events_listC
List events
Inputs: no named parameters.
events_postD
Post event
Inputs: no named parameters.
get_actions_app_key_registrationC
Get an existing App Key Registration
Inputs: no named parameters.
get_actions_app_key_registrationsC
List App Key Registrations
Inputs: no named parameters.
get_actions_connectionB
Get an existing Action Connection. This API requires a registered application key.
Inputs: no named parameters.
get_agentless_scanning_accounts_awC
Fetches the Agentless scan options for an activated account.
Inputs: no named parameters.
get_agentless_scanning_accounts_awsB
Fetches the scan options configured for AWS accounts.
Inputs: no named parameters.
get_agentless_scanning_ondemand_awC
Fetch the data of a specific on demand task.
Inputs: no named parameters.
get_agentless_scanning_ondemand_awsB
Fetches the most recent 1000 AWS on demand tasks.
Inputs: no named parameters.
get_api_keyC
Get an API key.
Inputs: no named parameters.
get_api_keysB
List all API keys available for your account.
Inputs: no named parameters.
get_apm_config_metricC
Get a specific span-based metric from your organization.
Inputs: no named parameters.
get_apm_config_metricsB
Get the list of configured span-based metrics with their definitions.
Inputs: no named parameters.
get_apm_config_retention_filterC
Get an APM retention filter.
Inputs: no named parameters.
get_apm_config_retention_filtersB
Get the list of APM retention filters.
Inputs: no named parameters.
get_app_builder_appC
Get the full definition of an app.
Inputs: no named parameters.
get_app_builder_appsB
List all apps, with optional filters and sorting. This endpoint is paginated. Only basic app information such as the app ID, name, and description is returned by this endpoint.
Inputs: no named parameters.
get_application_keyC
Get an application key for your org.
Inputs: no named parameters.
get_application_keysB
List all application keys available for your org
Inputs: no named parameters.
get_audit_eventsA
List endpoint returns events that match a Audit Logs search query. Results are paginated.
Use this endpoint to see your latest Audit Logs events.
Inputs: no named parameters.
get_authn_mappingB
Get an AuthN Mapping specified by the AuthN Mapping UUID.
Inputs: no named parameters.
get_authn_mappingsB
List all AuthN Mappings in the org.
Inputs: no named parameters.
get_caseC
Get the details of case by case_id
Inputs: no named parameters.
get_casesD
Search cases.
Inputs: no named parameters.
get_cases_projectB
Get the details of a project by project_id.
Inputs: no named parameters.
get_cases_projectsC
Get all projects.
Inputs: no named parameters.
get_catalog_entitiesB
Get a list of entities from Software Catalog.
Inputs: no named parameters.
get_catalog_kindsB
Get a list of entity kinds from Software Catalog.
Inputs: no named parameters.
get_catalog_relationsB
Get a list of entity relations from Software Catalog.
Inputs: no named parameters.
get_ci_pipelines_eventsA
List endpoint returns CI Visibility pipeline events that match a search query. Results are paginated similarly to logs.
Use this endpoint to see your latest pipeline events.
Inputs: no named parameters.
get_ci_tests_eventsA
List endpoint returns CI Visibility test events that match a search query. Results are paginated similarly to logs.
Use this endpoint to see your latest test events.
Inputs: no named parameters.
get_cloud_security_management_custom_frameworkC
Get a custom framework.
Inputs: no named parameters.
get_cloud_security_management_resource_filtersC
List resource filters.
Inputs: no named parameters.
get_container_imagesB
Get all Container Images for your organization.
Inputs: no named parameters.
get_containersB
Get all containers for your organization.
Inputs: no named parameters.
get_cost_aws_cur_configsB
List the AWS CUR configs.
Inputs: no named parameters.
get_cost_azure_uc_configsC
List the Azure configs.
Inputs: no named parameters.
get_cost_budgetC
Get a budget.
Inputs: no named parameters.
get_cost_budgetsC
List budgets.
Inputs: no named parameters.
get_cost_by_tag_active_billing_dimensionsB
Get active billing dimensions for cost attribution. Cost data for a given month becomes available no later than the 19th of the following month.
Inputs: no named parameters.
get_cost_by_tag_monthly_cost_attributionsA
Get monthly cost attribution by tag across multi-org and single root-org accounts.
Cost Attribution data for a given month becomes available no later than the 19th of the following month.
This API endpoint is paginated. To make sure you receive all records, check if the value of next_record_id is
set in the response. If it is, make another request and pass next_record_id as a parameter.
Pseudo code example:
response := GetMonthlyCostAttribution(start_month, end_month)
cursor := response.metadata.pagination.next_record_id
WHILE cursor != null BEGIN
sleep(5 seconds) # Avoid running into rate limit
response := GetMonthlyCostAttribution(start_month, end_month, next_record_id=cursor)
cursor := response.metadata.pagination.next_record_id
ENDThis endpoint is only accessible for parent-level organizations. This endpoint is not available in the Government (US1-FED) site.
Inputs: no named parameters.
get_cost_custom_costB
Fetch the specified Custom Costs file.
Inputs: no named parameters.
get_cost_custom_costsC
List the Custom Costs files.
Inputs: no named parameters.
get_cost_gcp_uc_configsC
List the GCP Usage Cost configs.
Inputs: no named parameters.
get_csm_onboarding_agentsB
Get the list of all CSM Agents running on your hosts and containers.
Inputs: no named parameters.
get_csm_onboarding_coverage_analysis_cloud_accountsB
Get the CSM Coverage Analysis of your Cloud Accounts. This is calculated based on the number of your Cloud Accounts that are scanned for security issues.
Inputs: no named parameters.
get_csm_onboarding_coverage_analysis_hosts_and_containersB
Get the CSM Coverage Analysis of your Hosts and Containers. This is calculated based on the number of agents running on your Hosts and Containers with CSM feature(s) enabled.
Inputs: no named parameters.
get_csm_onboarding_coverage_analysis_serverlessB
Get the CSM Coverage Analysis of your Serverless Resources. This is calculated based on the number of agents running on your Serverless Resources with CSM feature(s) enabled.
Inputs: no named parameters.
get_csm_onboarding_serverless_agentsB
Get the list of all CSM Serverless Agents running on your hosts and containers.
Inputs: no named parameters.
get_current_user_application_keyB
Get an application key owned by current user
Inputs: no named parameters.
get_current_user_application_keysB
List all application keys available for current user
Inputs: no named parameters.
get_dashboardC
Get a dashboard using the specified ID.
Inputs: no named parameters.
get_dashboard_by_idD
Get dashboard by ID
Inputs: no named parameters.
get_dashboard_lists_manualB
Fetch an existing dashboard list's definition.
Inputs: no named parameters.
get_dashboard_lists_manual_dashboardsB
Fetch the dashboard list’s dashboard definitions.
Inputs: no named parameters.
get_dashboard_lists_manualsB
Fetch all of your existing dashboard list definitions.
Inputs: no named parameters.
get_dashboard_publicB
Fetch an existing shared dashboard's sharing metadata associated with the specified token.
Inputs: no named parameters.
get_dashboard_public_invitationB
Describe the invitations that exist for the given shared dashboard (paginated).
Inputs: no named parameters.
get_dashboardsB
Get all dashboards.
Note: This query will only return custom created or cloned dashboards. This query will not return preset dashboards.
Inputs: no named parameters.
get_domain_allowlistsB
Get the domain allowlist for an organization.
Inputs: no named parameters.
get_dora_deploymentC
Use this API endpoint to get a deployment event.
Inputs: no named parameters.
get_dora_failureC
Use this API endpoint to get a failure event.
Inputs: no named parameters.
get_downtimeC
Get downtime detail by downtime_id.
Inputs: no named parameters.
get_downtimesB
Get all scheduled downtimes.
Inputs: no named parameters.
get_error_tracking_issueB
Retrieve the full details for a specific error tracking issue, including attributes and relationships.
Inputs: no named parameters.
get_eventB
Get the details of an event by event_id.
Inputs: no named parameters.
get_eventsA
List endpoint returns events that match an events search query. Results are paginated similarly to logs.
Use this endpoint to see your latest events.
Inputs: no named parameters.
get_graph_embedB
Get the HTML fragment for a previously generated embed with embed_id.
Inputs: no named parameters.
get_graph_embed_enableC
Enable a specified embed.
Inputs: no named parameters.
get_graph_embed_revokeC
Revoke a specified embed.
Inputs: no named parameters.
get_graph_embedsB
Gets a list of previously created embeddable graphs.
Inputs: no named parameters.
get_graph_snapshotsC
Take graph snapshots. Note: When a snapshot is created, there is some delay before it is available.
Inputs: no named parameters.
get_hostsA
This endpoint allows searching for hosts by name, alias, or tag. Hosts live within the past 3 hours are included by default. Retention is 7 days. Results are paginated with a max of 1000 results at a time.
Inputs: no named parameters.
get_hosts_totalsA
This endpoint returns the total number of active and up hosts in your Datadog account. Active means the host has reported in the past hour, and up means it has reported in the past two hours.
Inputs: no named parameters.
get_integration_awsB
List all Datadog-AWS integrations available in your Datadog organization.
Inputs: no named parameters.
get_integration_aws_available_namespace_rulesB
List all namespace rules for a given Datadog-AWS integration. This endpoint takes no arguments.
Inputs: no named parameters.
get_integration_aws_event_bridgesB
Get all Amazon EventBridge sources.
Inputs: no named parameters.
get_integration_aws_filteringsB
Get all AWS tag filters.
Inputs: no named parameters.
get_integration_aws_iam_permissionsB
Get all AWS IAM permissions required for the AWS integration.
Inputs: no named parameters.
get_integration_aws_logsB
List all Datadog-AWS Logs integrations configured in your Datadog account.
Inputs: no named parameters.
get_integration_aws_logs_servicesA
Get the list of current AWS services that Datadog offers automatic log collection. Use returned service IDs with the services parameter for the Enable an AWS service log collection API endpoint.
Inputs: no named parameters.
get_integration_azuresB
List all Datadog-Azure integrations configured in your Datadog account.
Inputs: no named parameters.
get_integration_gcp_accountsA
List all GCP STS-enabled service accounts configured in your Datadog account.
Inputs: no named parameters.
get_integration_gcp_sts_delegatesB
List your Datadog-GCP STS delegate account configured in your Datadog account.
Inputs: no named parameters.
get_integration_ms_teams_configuration_channelB
Get the tenant, team, and channel ID of a channel in the Datadog Microsoft Teams integration.
Inputs: no named parameters.
get_integration_ms_teams_configuration_tenant_based_handleB
Get the tenant, team, and channel information of a tenant-based handle from the Datadog Microsoft Teams integration.
Inputs: no named parameters.
get_integration_ms_teams_configuration_tenant_based_handlesB
Get a list of all tenant-based handles from the Datadog Microsoft Teams integration.
Inputs: no named parameters.
get_integration_ms_teams_configuration_workflows_webhook_handleB
Get the name of a Workflows webhook handle from the Datadog Microsoft Teams integration.
Inputs: no named parameters.
get_integration_ms_teams_configuration_workflows_webhook_handlesB
Get a list of all Workflows webhook handles from the Datadog Microsoft Teams integration.
Inputs: no named parameters.
get_integration_opsgenie_serviceB
Get a single service from the Datadog Opsgenie integration.
Inputs: no named parameters.
get_integration_opsgenie_servicesB
Get a list of all services from the Datadog Opsgenie integration.
Inputs: no named parameters.
get_integration_pagerduty_configuration_serviceB
Get service name in the Datadog-PagerDuty integration.
Inputs: no named parameters.
get_integrations_cloudflare_accountC
Get a Cloudflare account.
Inputs: no named parameters.
get_integrations_cloudflare_accountsB
List Cloudflare accounts.
Inputs: no named parameters.
get_integrations_confluent_cloud_accountB
Get the Confluent account with the provided account ID.
Inputs: no named parameters.
get_integrations_confluent_cloud_account_resources_v2C
Get a Confluent resource with the provided resource id for the account associated with the provided account ID.
Inputs: no named parameters.
get_integrations_confluent_cloud_account_resources_v2_2B
Get a Confluent resource for the account associated with the provided ID.
Inputs: no named parameters.
get_integrations_confluent_cloud_accountsB
List Confluent accounts.
Inputs: no named parameters.
get_integrations_fastly_accountC
Get a Fastly account.
Inputs: no named parameters.
get_integrations_fastly_accountsB
List Fastly accounts.
Inputs: no named parameters.
get_integrations_fastly_account_services_v2B
List Fastly services for an account.
Inputs: no named parameters.
get_integrations_fastly_account_services_v2_2C
Get a Fastly service for an account.
Inputs: no named parameters.
get_integration_slack_configuration_account_channels_v1B
Get a list of all channels configured for your Datadog-Slack integration.
Inputs: no named parameters.
get_integration_slack_configuration_account_channels_v1_2B
Get a channel configured for your Datadog-Slack integration.
Inputs: no named parameters.
get_integrations_okta_accountD
Get an Okta account.
Inputs: no named parameters.
get_integrations_okta_accountsC
List Okta accounts.
Inputs: no named parameters.
get_integration_webhooks_configuration_custom_variableB
Shows the content of the custom variable with the name <CUSTOM_VARIABLE_NAME>.
If the custom variable is secret, the value does not return in the response payload.
Inputs: no named parameters.
get_integration_webhooks_configuration_webhookB
Gets the content of the webhook with the name <WEBHOOK_NAME>.
Inputs: no named parameters.
get_ip_allowlistsB
Returns the IP allowlist and its enabled or disabled state.
Inputs: no named parameters.
get_logs_config_archiveC
Get a specific archive from your organization.
Inputs: no named parameters.
get_logs_config_archive_ordersB
Get the current order of your archives. This endpoint takes no JSON arguments.
Inputs: no named parameters.
get_logs_config_archive_readersB
Returns all read roles a given archive is restricted to.
Inputs: no named parameters.
get_logs_config_archivesB
Get the list of configured logs archives with their definitions.
Inputs: no named parameters.
get_logs_config_custom_destinationC
Get a specific custom destination in your organization.
Inputs: no named parameters.
get_logs_config_custom_destinationsB
Get the list of configured custom destinations in your organization with their definitions.
Inputs: no named parameters.
get_logs_config_indexeB
Get one log index from your organization. This endpoint takes no JSON arguments.
Inputs: no named parameters.
get_logs_config_indexesC
The Index object describes the configuration of a log index.
This endpoint returns an array of the LogIndex objects of your organization.
Inputs: no named parameters.
get_logs_config_index_ordersB
Get the current order of your log indexes. This endpoint takes no JSON arguments.
Inputs: no named parameters.
get_logs_config_metricB
Get a specific log-based metric from your organization.
Inputs: no named parameters.
get_logs_config_metricsB
Get the list of configured log-based metrics with their definitions.
Inputs: no named parameters.
get_logs_config_pipelineB
Get a specific pipeline from your organization. This endpoint takes no JSON arguments.
Inputs: no named parameters.
get_logs_config_pipeline_ordersB
Get the current order of your pipelines. This endpoint takes no JSON arguments.
Inputs: no named parameters.
get_logs_config_pipelinesB
Get all pipelines from your organization. This endpoint takes no JSON arguments.
Inputs: no named parameters.
get_logs_eventsA
List endpoint returns logs that match a log search query. Results are paginated.
Use this endpoint to see your latest logs.
If you are considering archiving logs for your organization, consider use of the Datadog archive capabilities instead of the log list API. See Datadog Logs Archive documentation.
Inputs: no named parameters.
get_metricC
Get metadata about a specific metric.
Inputs: no named parameters.
get_metric_active_configurationsA
List tags and aggregations that are actively queried on dashboards, notebooks, monitors, the Metrics Explorer, and using the API for a given metric name.
Inputs: no named parameters.
get_metric_all_tagsB
View indexed tag key-value pairs for a given metric name over the previous hour.
Inputs: no named parameters.
get_metric_assetsB
Returns dashboards, monitors, notebooks, and SLOs that a metric is stored in, if any. Updated every 24 hours.
Inputs: no named parameters.
get_metrics_v1B
Get the list of actively reporting metrics from a given time until now.
Inputs: no named parameters.
get_metrics_v2A
Returns all metrics that can be configured in the Metrics Summary page or with Metrics without Limits™ (matching additional filters if specified).
Optionally, paginate by using the page[cursor] and/or page[size] query parameters.
To fetch the first page, pass in a query parameter with either a valid page[size] or an empty cursor like page[cursor]=. To fetch the next page, pass in the next_cursor value from the response as the new page[cursor] value.
Once the meta.pagination.next_cursor value is null, all pages have been retrieved.
Inputs: no named parameters.
get_metric_tag_cardinalitiesB
Returns the cardinality details of tags for a specific metric.
Inputs: no named parameters.
get_metric_tagsB
Returns the tag configuration for the given metric name.
Inputs: no named parameters.
get_metric_volumesB
View distinct metrics volumes for the given metric name.
Custom metrics generated in-app from other products will return null for ingested volumes.
Inputs: no named parameters.
get_monitorB
Get details about the specified monitor from your organization.
Inputs: no named parameters.
get_monitor_by_idD
Get a monitor by ID
Inputs: no named parameters.
get_monitor_downtime_matchesB
Get all active downtimes for the specified monitor.
Inputs: no named parameters.
get_monitor_notification_ruleB
Returns a monitor notification rule by rule_id.
Inputs: no named parameters.
get_monitor_notification_rulesB
Returns a list of all monitor notification rules.
Inputs: no named parameters.
get_monitor_policiesB
Get all monitor configuration policies.
Inputs: no named parameters.
get_monitor_policyB
Get a monitor configuration policy by policy_id.
Inputs: no named parameters.
get_monitorsB
Get all monitors from your organization.
Inputs: no named parameters.
get_ndm_deviceC
Get the device details.
Inputs: no named parameters.
get_ndm_devicesC
Get the list of devices.
Inputs: no named parameters.
get_ndm_interfacesC
Get the list of interfaces of the device.
Inputs: no named parameters.
get_ndm_tags_deviceB
Get the list of tags for a device.
Inputs: no named parameters.
get_notebookC
Get a notebook using the specified notebook ID.
Inputs: no named parameters.
get_notebooksB
Get all notebooks. This can also be used to search for notebooks with a particular query in the notebook
name or author handle.
Inputs: no named parameters.
get_on_call_escalation_policyC
Get an on-call escalation policy
Inputs: no named parameters.
get_on_call_scheduleC
Get an on-call schedule
Inputs: no named parameters.
get_on_call_schedule_on_callB
Retrieves the user who is on-call for the specified schedule at a given time.
Inputs: no named parameters.
get_on_call_team_on_callB
Get a team's on-call users at a given time
Inputs: no named parameters.
get_on_call_team_routing_rulesB
Get a team's on-call routing rules
Inputs: no named parameters.
get_orgC
Get organization information.
Inputs: no named parameters.
get_org_configB
Return the name, description, and value of a specific Org Config.
Inputs: no named parameters.
get_org_configsB
Returns all Org Configs (name, description, and value).
Inputs: no named parameters.
get_orgsB
This endpoint returns data on your top-level organization.
Inputs: no named parameters.
get_permissionsB
Returns a list of all permissions, including name, description, and ID.
Inputs: no named parameters.
get_powerpackD
Get a powerpack.
Inputs: no named parameters.
get_powerpacksB
Get a list of all powerpacks.
Inputs: no named parameters.
get_processesB
Get all processes for your organization.
Inputs: no named parameters.
get_remote_config_products_asm_waf_custom_ruleB
Retrieve a WAF custom rule by ID.
Inputs: no named parameters.
get_remote_config_products_asm_waf_custom_rulesB
Retrieve a list of WAF custom rule.
Inputs: no named parameters.
get_remote_config_products_asm_waf_exclusion_filterB
Retrieve a specific WAF exclusion filter using its identifier.
Inputs: no named parameters.
get_remote_config_products_asm_waf_exclusion_filtersB
Retrieve a list of WAF exclusion filters.
Inputs: no named parameters.
get_remote_config_products_cws_agent_ruleB
Get the details of a specific Workload Protection agent rule.
Note: This endpoint is not available for the Government (US1-FED) site. Please reference the (US1-FED) specific resource below.
Inputs: no named parameters.
get_remote_config_products_cws_agent_rulesB
Get the list of Workload Protection agent rules.
Note: This endpoint is not available for the Government (US1-FED) site. Please reference the (US1-FED) specific resource below.
Inputs: no named parameters.
get_remote_config_products_cws_policiesA
Get the list of Workload Protection policies.
Note: This endpoint is not available for the Government (US1-FED) site. Please reference the (US1-FED) specific resource below.
Inputs: no named parameters.
get_remote_config_products_cws_policyB
Get the details of a specific Workload Protection policy.
Note: This endpoint is not available for the Government (US1-FED) site. Please reference the (US1-FED) specific resource below.
Inputs: no named parameters.
get_remote_config_products_cws_policy_downloadsA
The download endpoint generates a Workload Protection policy file from your currently active
Workload Protection agent rules, and downloads them as a .policy file. This file can then be deployed to
your agents to update the policy running in your environment.
Note: This endpoint is not available for the Government (US1-FED) site. Please reference the (US1-FED) specific resource below.
Inputs: no named parameters.
get_resourcesB
Get information about Datadog IP ranges.
Inputs: no named parameters.
get_restriction_policyB
Retrieves the restriction policy associated with a specified resource.
Inputs: no named parameters.
get_roleB
Get a role in the organization specified by the role’s role_id.
Inputs: no named parameters.
get_role_permissionsB
Returns a list of all permissions for a single role.
Inputs: no named parameters.
get_rolesB
Returns all roles, including their names and their unique identifiers.
Inputs: no named parameters.
get_role_usersC
Gets all users of a role.
Inputs: no named parameters.
get_rum_applicationB
Get the RUM application with given ID in your organization.
Inputs: no named parameters.
get_rum_application_retention_filters_v2B
Get the list of RUM retention filters for a RUM application.
Inputs: no named parameters.
get_rum_application_retention_filters_v2_2B
Get a RUM retention filter for a RUM application.
Inputs: no named parameters.
get_rum_applicationsB
List all the RUM applications in your organization.
Inputs: no named parameters.
get_rum_config_metricC
Get a specific rum-based metric from your organization.
Inputs: no named parameters.
get_rum_config_metricsB
Get the list of configured rum-based metrics with their definitions.
Inputs: no named parameters.
get_rum_eventsB
List endpoint returns events that match a RUM search query. Results are paginated.
Use this endpoint to see your latest RUM events.
Inputs: no named parameters.
get_security_cloud_workload_policy_downloadsA
The download endpoint generates a Workload Protection policy file from your currently active
Workload Protection agent rules, and downloads them as a .policy file. This file can then be deployed to
your agents to update the policy running in your environment.
Note: This endpoint should only be used for the Government (US1-FED) site.
Inputs: no named parameters.
get_security_monitoring_cloud_workload_security_agent_ruleC
Get the details of a specific agent rule.
Note: This endpoint should only be used for the Government (US1-FED) site.
Inputs: no named parameters.
get_security_monitoring_cloud_workload_security_agent_rulesC
Get the list of agent rules.
Note: This endpoint should only be used for the Government (US1-FED) site.
Inputs: no named parameters.
get_security_monitoring_configuration_security_filterC
Get the details of a specific security filter.
See the security filter guide for more examples.
Inputs: no named parameters.
get_security_monitoring_configuration_security_filtersB
Get the list of configured security filters with their definitions.
Inputs: no named parameters.
get_security_monitoring_configuration_suppressionB
Get the details of a specific suppression rule.
Inputs: no named parameters.
get_security_monitoring_configuration_suppressionsB
Get the list of all suppression rules.
Inputs: no named parameters.
get_security_monitoring_configuration_suppressions_ruleB
Get the list of suppressions that affect a specific existing rule by its ID.
Inputs: no named parameters.
get_security_monitoring_ruleC
Get a rule's details.
Inputs: no named parameters.
get_security_monitoring_rule_convertB
Convert an existing rule from JSON to Terraform for datadog provider resource datadog_security_monitoring_rule.
Inputs: no named parameters.
get_security_monitoring_rulesD
List rules.
Inputs: no named parameters.
get_security_monitoring_signalC
Get a signal's details.
Inputs: no named parameters.
get_security_monitoring_signalsC
The list endpoint returns security signals that match a search query. Both this endpoint and the POST endpoint can be used interchangeably when listing security signals.
Inputs: no named parameters.
get_security_signals_notification_ruleB
Get the details of a notification rule for security signals.
Inputs: no named parameters.
get_security_signals_notification_rulesB
Returns the list of notification rules for security signals.
Inputs: no named parameters.
get_security_vulnerabilities_notification_ruleB
Get the details of a notification rule for security vulnerabilities.
Inputs: no named parameters.
get_security_vulnerabilities_notification_rulesB
Returns the list of notification rules for security vulnerabilities.
Inputs: no named parameters.
get_sensitive_data_scanner_configsB
List all the Scanning groups in your organization.
Inputs: no named parameters.
get_sensitive_data_scanner_config_standard_patternsD
Returns all standard patterns.
Inputs: no named parameters.
get_service_account_application_keys_v2B
Get an application key owned by this service account.
Inputs: no named parameters.
get_service_account_application_keys_v2_2B
List all application keys available for this service account.
Inputs: no named parameters.
get_services_definitionB
Get a single service definition from the Datadog Service Catalog.
Inputs: no named parameters.
get_services_definitionsB
Get a list of all service definitions from the Datadog Service Catalog.
Inputs: no named parameters.
get_sloC
Get a service level objective object.
Inputs: no named parameters.
get_slo_correctionD
Get an SLO correction.
Inputs: no named parameters.
get_slo_corrections_v1C
Get all Service Level Objective corrections.
Inputs: no named parameters.
get_slo_corrections_v1_2C
Get corrections applied to an SLO
Inputs: no named parameters.
get_slo_historyB
Get a specific SLO’s history, regardless of its SLO type.
The detailed history data is structured according to the source data type. For example, metric data is included for event SLOs that use the metric source, and monitor SLO types include the monitor transition history.
Note: There are different response formats for event based and time based SLOs. Examples of both are shown.
Inputs: no named parameters.
get_slosB
Get a list of service level objective objects for your organization.
Inputs: no named parameters.
get_spans_eventsA
List endpoint returns spans that match a span search query. Results are paginated.
Use this endpoint to see your latest spans.
This endpoint is rate limited to 300 requests per hour.
Inputs: no named parameters.
get_synthetics_ci_batchC
Get a batch's updated details.
Inputs: no named parameters.
get_synthetics_locationsB
Get the list of public and private locations available for Synthetic tests. No arguments required.
Inputs: no named parameters.
get_synthetics_private_locationC
Get a Synthetic private location.
Inputs: no named parameters.
get_synthetics_settings_default_locationsC
Get the default locations settings.
Inputs: no named parameters.
get_synthetics_settings_on_demand_concurrency_capsB
Get the on-demand concurrency cap.
Inputs: no named parameters.
get_synthetics_test_results_v1C
Get a specific full result from a given Synthetic API test.
Inputs: no named parameters.
get_synthetics_test_results_v1_2B
Get the last 150 test results summaries for a given Synthetic API test.
Inputs: no named parameters.
get_synthetics_testsB
Get the list of all Synthetic tests.
Inputs: no named parameters.
get_synthetics_tests_browserB
Get the detailed configuration (including steps) associated with a Synthetic browser test.
Inputs: no named parameters.
get_synthetics_tests_browser_results_v1B
Get a specific full result from a given Synthetic browser test.
Inputs: no named parameters.
get_synthetics_tests_browser_results_v1_2B
Get the last 150 test results summaries for a given Synthetic browser test.
Inputs: no named parameters.
get_synthetics_tests_mobileB
Get the detailed configuration associated with a Synthetic Mobile test.
Inputs: no named parameters.
get_synthetics_test_v1B
Get the detailed configuration associated with a Synthetic API test.
Inputs: no named parameters.
get_synthetics_test_v1_2B
Get the detailed configuration associated with a Synthetic test.
Inputs: no named parameters.
get_synthetics_variableB
Get the detailed configuration of a global variable.
Inputs: no named parameters.
get_synthetics_variablesB
Get the list of all Synthetic global variables.
Inputs: no named parameters.
get_tags_hostB
Return the list of tags that apply to a given host.
Inputs: no named parameters.
get_tags_hostsB
Return a mapping of tags to hosts for your whole infrastructure.
Inputs: no named parameters.
get_teamB
Get a single team using the team's id.
Inputs: no named parameters.
get_team_links_v2B
Get all links for a given team.
Inputs: no named parameters.
get_team_links_v2_2C
Get a single link for a team.
Inputs: no named parameters.
get_team_membershipsB
Get a paginated list of members for a team
Inputs: no named parameters.
get_team_permission_settingsB
Get all permission settings for a given team.
Inputs: no named parameters.
get_teamsB
Get all teams.
Can be used to search for teams using the filter[keyword] and filter[me] query parameters.
Inputs: no named parameters.
get_usage_billable_summariesA
Get billable usage across your account.
This endpoint is only accessible for parent-level organizations.
Inputs: no named parameters.
get_usage_billing_dimension_mappingsA
Get a mapping of billing dimensions to the corresponding keys for the supported usage metering public API endpoints. Mapping data is updated on a monthly cadence.
This endpoint is only accessible to parent-level organizations.
Inputs: no named parameters.
get_usage_estimated_costsA
Get estimated cost across multi-org and single root-org accounts.
Estimated cost data is only available for the current month and previous month
and is delayed by up to 72 hours from when it was incurred.
To access historical costs prior to this, use the /historical_cost endpoint.
This endpoint is only accessible for parent-level organizations.
Inputs: no named parameters.
get_usage_historical_costsA
Get historical cost across multi-org and single root-org accounts. Cost data for a given month becomes available no later than the 16th of the following month.
This endpoint is only accessible for parent-level organizations.
Inputs: no named parameters.
get_usage_hourly_attributionsA
Get hourly usage attribution. Multi-region data is available starting March 1, 2023.
This API endpoint is paginated. To make sure you receive all records, check if the value of next_record_id is
set in the response. If it is, make another request and pass next_record_id as a parameter.
Pseudo code example:
response := GetHourlyUsageAttribution(start_month)
cursor := response.metadata.pagination.next_record_id
WHILE cursor != null BEGIN
sleep(5 seconds) # Avoid running into rate limit
response := GetHourlyUsageAttribution(start_month, next_record_id=cursor)
cursor := response.metadata.pagination.next_record_id
ENDInputs: no named parameters.
get_usage_hourly_usagesC
Get hourly usage by product family.
Inputs: no named parameters.
get_usage_logs_by_indexsC
Get hourly usage for logs by index.
Inputs: no named parameters.
get_usage_monthly_attributionsB
Get monthly usage attribution. Multi-region data is available starting March 1, 2023.
This API endpoint is paginated. To make sure you receive all records, check if the value of next_record_id is
set in the response. If it is, make another request and pass next_record_id as a parameter.
Pseudo code example:
response := GetMonthlyUsageAttribution(start_month)
cursor := response.metadata.pagination.next_record_id
WHILE cursor != null BEGIN
sleep(5 seconds) # Avoid running into rate limit
response := GetMonthlyUsageAttribution(start_month, next_record_id=cursor)
cursor := response.metadata.pagination.next_record_id
ENDInputs: no named parameters.
get_usage_projected_costsA
Get projected cost across multi-org and single root-org accounts. Projected cost data is only available for the current month and becomes available around the 12th of the month.
This endpoint is only accessible for parent-level organizations.
Inputs: no named parameters.
get_usage_summariesA
Get all usage across your account.
This endpoint is only accessible for parent-level organizations.
Inputs: no named parameters.
get_usage_top_avg_metricsA
Get all custom metrics by hourly average. Use the month parameter to get a month-to-date data resolution or use the day parameter to get a daily resolution. One of the two is required, and only one of the two is allowed.
Inputs: no named parameters.
get_userB
Get a user in the organization specified by the user’s user_id.
Inputs: no named parameters.
get_user_invitationB
Returns a single user invitation by its UUID.
Inputs: no named parameters.
get_user_membershipsC
Get a list of memberships for a user
Inputs: no named parameters.
get_user_orgsB
Get a user organization. Returns the user information and all organizations joined by this user.
Inputs: no named parameters.
get_user_permissionsC
Get a user permission set. Returns a list of the user’s permissions granted by the associated user's roles.
Inputs: no named parameters.
get_usersA
Get the list of all users in the organization. This list includes all users even if they are deactivated or unverified.
Inputs: no named parameters.
get_workflowB
Get a workflow by ID. This API requires a registered application key.
Inputs: no named parameters.
get_workflow_instances_v2B
List all instances of a given workflow. This API requires a registered application key.
Inputs: no named parameters.
get_workflow_instances_v2_2B
Get a specific execution of a given workflow. This API requires a registered application key.
Inputs: no named parameters.
incidents_createD
Create incident
Inputs: no named parameters.
incidents_getC
Get incident by ID
Inputs: no named parameters.
incidents_listC
List incidents
Inputs: no named parameters.
incidents_updateD
Update incident
Inputs: no named parameters.
list_dashboardsB
List dashboards with optional name/tags filters
Inputs: no named parameters.
list_monitorsB
List monitors (common filters supported)
Inputs: no named parameters.
logs_aggregate_analyticsD
Aggregate logs analytics
Inputs: no named parameters.
logs_search_eventsC
Search logs (events)
Inputs: no named parameters.
logs_sendC
Send logs to intake
Inputs: no named parameters.
metrics_query_scalarsD
Metrics: query scalars
Inputs: no named parameters.
metrics_query_timeseriesD
Metrics: query timeseries
Inputs: no named parameters.
metrics_submit_seriesC
Submit metrics (v2 series)
Inputs: no named parameters.
mute_hostB
Mute a host. Note: This creates a Downtime V2 for the host.
Inputs: no named parameters.
mute_monitorB
Mute the specified monitor.
Inputs: no named parameters.
mute_monitor_v1C
Mute a monitor
Inputs: no named parameters.
notebooks_createD
Create a notebook
Inputs: no named parameters.
notebooks_deleteD
Delete a notebook
Inputs: no named parameters.
notebooks_getC
Get a notebook by ID
Inputs: no named parameters.
notebooks_listC
List notebooks
Inputs: no named parameters.
notebooks_updateC
Update a notebook
Inputs: no named parameters.
query_resourcesC
Query timeseries points.
Inputs: no named parameters.
query_scalarsC
Query scalar values (as seen on Query Value, Table, and Toplist widgets). Multiple data sources are supported with the ability to process the data using formulas and functions.
Inputs: no named parameters.
query_timeseriesC
Query timeseries data across various data sources and process the data by applying formulas and functions.
Inputs: no named parameters.
roles_getC
Get role by ID
Inputs: no named parameters.
roles_listD
List roles
Inputs: no named parameters.
search_audit_eventsA
List endpoint returns Audit Logs events that match an Audit search query. Results are paginated.
Use this endpoint to build complex Audit Logs events filtering and search.
Inputs: no named parameters.
search_ci_pipelines_eventsA
List endpoint returns CI Visibility pipeline events that match a search query. Results are paginated similarly to logs.
Use this endpoint to build complex events filtering and search.
Inputs: no named parameters.
search_ci_tests_eventsA
List endpoint returns CI Visibility test events that match a search query. Results are paginated similarly to logs.
Use this endpoint to build complex events filtering and search.
Inputs: no named parameters.
search_error_tracking_issuesA
Search issues endpoint allows you to programmatically search for issues within your organization. This endpoint returns a list of issues that match a given search query, following the event search syntax. The search results are limited to a maximum of 100 issues per request.
Inputs: no named parameters.
search_eventsB
List endpoint returns events that match an events search query. Results are paginated similarly to logs.
Use this endpoint to build complex events filtering and search.
Inputs: no named parameters.
search_logs_eventsA
List endpoint returns logs that match a log search query. Results are paginated.
Use this endpoint to build complex logs filtering and search.
If you are considering archiving logs for your organization, consider use of the Datadog archive capabilities instead of the log list API. See Datadog Logs Archive documentation.
Inputs: no named parameters.
search_monitor_groupsC
Search and filter your monitor groups details.
Inputs: no named parameters.
search_monitorsC
Search and filter your monitors details.
Inputs: no named parameters.
search_resourcesB
Search for metrics from the last 24 hours in Datadog.
Inputs: no named parameters.
search_rum_eventsA
List endpoint returns RUM events that match a RUM search query. Results are paginated.
Use this endpoint to build complex RUM events filtering and search.
Inputs: no named parameters.
search_security_monitoring_signalsB
Returns security signals that match a search query. Both this endpoint and the GET endpoint can be used interchangeably for listing security signals.
Inputs: no named parameters.
search_slosB
Get a list of service level objective objects for your organization.
Inputs: no named parameters.
search_spans_eventsA
List endpoint returns spans that match a span search query. Results are paginated.
Use this endpoint to build complex spans filtering and search.
This endpoint is rate limited to 300 requests per hour.
Inputs: no named parameters.
search_synthetics_testsC
Search for Synthetic tests and Test Suites.
Inputs: no named parameters.
send_logsA
Send your logs to your Datadog platform over HTTP. Limits per HTTP request are:
Maximum content size per payload (uncompressed): 5MB
Maximum size for a single log: 1MB
Maximum array size if sending multiple logs in an array: 1000 entries
Any log exceeding 1MB is accepted and truncated by Datadog:
For a single log request, the API truncates the log at 1MB and returns a 2xx.
For a multi-logs request, the API processes all logs, truncates only logs larger than 1MB, and returns a 2xx.
Datadog recommends sending your logs compressed.
Add the Content-Encoding: gzip header to the request when sending compressed logs.
Log events can be submitted with a timestamp that is up to 18 hours in the past.
The status codes answered by the HTTP API are:
202: Accepted: the request has been accepted for processing
400: Bad request (likely an issue in the payload formatting)
401: Unauthorized (likely a missing API Key)
403: Permission issue (likely using an invalid API Key)
408: Request Timeout, request should be retried after some time
413: Payload too large (batch is above 5MB uncompressed)
429: Too Many Requests, request should be retried after some time
500: Internal Server Error, the server encountered an unexpected condition that prevented it from fulfilling the request, request should be retried after some time
503: Service Unavailable, the server is not ready to handle the request probably because it is overloaded, request should be retried after some time
Inputs: no named parameters.
slos_createD
Create SLO
Inputs: no named parameters.
slos_deleteC
Delete SLO
Inputs: no named parameters.
slos_getC
Get SLO by ID
Inputs: no named parameters.
slos_listC
List Service Level Objectives
Inputs: no named parameters.
slos_updateD
Update SLO
Inputs: no named parameters.
submit_distribution_pointsC
The distribution points end-point allows you to post distribution data that can be graphed on Datadog’s dashboards.
Inputs: no named parameters.
submit_seriesB
The metrics end-point allows you to post time-series data that can be graphed on Datadog’s dashboards. The maximum payload size is 500 kilobytes (512000 bytes). Compressed payloads must have a decompressed size of less than 5 megabytes (5242880 bytes).
If you’re submitting metrics directly to the Datadog API without using DogStatsD, expect:
64 bits for the timestamp
64 bits for the value
20 bytes for the metric names
50 bytes for the timeseries
The full payload is approximately 100 bytes.
Host name is one of the resources in the Resources field.
Inputs: no named parameters.
synthetics_create_testC
Create a Synthetics test
Inputs: no named parameters.
synthetics_delete_testB
Delete a Synthetics test
Inputs: no named parameters.
synthetics_get_testC
Get a Synthetics test
Inputs: no named parameters.
synthetics_list_testsC
List Synthetics tests
Inputs: no named parameters.
synthetics_update_testC
Update a Synthetics test
Inputs: no named parameters.
teams_getC
Get team by ID
Inputs: no named parameters.
teams_listC
List teams
Inputs: no named parameters.
unmute_hostB
Unmutes a host. This endpoint takes no JSON arguments.
Inputs: no named parameters.
unmute_monitorB
Unmute the specified monitor.
Inputs: no named parameters.
unmute_monitor_v1C
Unmute a monitor
Inputs: no named parameters.
update_actions_app_key_registrationC
Register a new App Key
Inputs: no named parameters.
update_actions_connectionB
Update an existing Action Connection. This API requires a registered application key.
Inputs: no named parameters.
update_agentless_scanning_accounts_awB
Update the Agentless scan options for an activated account.
Inputs: no named parameters.
update_api_keyC
Update an API key.
Inputs: no named parameters.
update_apm_config_metricB
Update a specific span-based metric from your organization. Returns the span-based metric object from the request body when the request is successful.
Inputs: no named parameters.
update_apm_config_retention_filterC
Update a retention filter from your organization.
Inputs: no named parameters.
update_apm_config_retention_filters_execution_ordersB
Re-order the execution order of retention filters.
Inputs: no named parameters.
update_app_builder_appB
Update an existing app. This creates a new version of the app.
Inputs: no named parameters.
update_application_keyC
Edit an application key
Inputs: no named parameters.
update_authn_mappingC
Edit an AuthN Mapping.
Inputs: no named parameters.
update_cloud_security_management_custom_frameworkC
Update a custom framework.
Inputs: no named parameters.
update_cloud_security_management_resource_filtersD
Update resource filters.
Inputs: no named parameters.
update_cost_aws_cur_configB
Update the status (active/archived) and/or account filtering configuration of an AWS CUR config.
Inputs: no named parameters.
update_cost_azure_uc_configB
Update the status of an Azure config (active/archived).
Inputs: no named parameters.
update_cost_budgetsB
Create a new budget or update an existing one.
Inputs: no named parameters.
update_cost_custom_costsB
Upload a Custom Costs file.
Inputs: no named parameters.
update_cost_gcp_uc_configB
Update the status of an GCP Usage Cost config (active/archived).
Inputs: no named parameters.
update_current_user_application_keyB
Edit an application key owned by current user
Inputs: no named parameters.
update_dashboardC
Update a dashboard using the specified ID.
Inputs: no named parameters.
update_dashboard_lists_manualB
Update the name of a dashboard list.
Inputs: no named parameters.
update_dashboard_lists_manual_dashboardsC
Update dashboards of an existing dashboard list.
Inputs: no named parameters.
update_dashboard_publicC
Update a shared dashboard associated with the specified token.
Inputs: no named parameters.
update_dashboardsB
Restore dashboards using the specified IDs. If there are any failures, no dashboards will be restored (partial success is not allowed).
Inputs: no named parameters.
update_dashboard_v1C
Update a dashboard
Inputs: no named parameters.
update_domain_allowlistsB
Update the domain allowlist for an organization.
Inputs: no named parameters.
update_downtimeD
Update a downtime by downtime_id.
Inputs: no named parameters.
update_error_tracking_issue_assigneeC
Update the assignee of an issue by issue_id.
Inputs: no named parameters.
update_error_tracking_issue_stateB
Update the state of an issue by issue_id. Use this endpoint to move an issue between states such as OPEN, RESOLVED, or IGNORED.
Inputs: no named parameters.
update_integration_awsB
Update a Datadog-Amazon Web Services integration.
Inputs: no named parameters.
update_integration_aws_generate_new_external_idsB
Generate a new AWS external ID for a given AWS account ID and role name pair.
Inputs: no named parameters.
update_integration_azuresA
Update a Datadog-Azure integration. Requires an existing tenant_name and client_id.
Any other fields supplied will overwrite existing values. To overwrite tenant_name or client_id,
use new_tenant_name and new_client_id. To leave a field unchanged, do not supply that field in the payload.
Inputs: no named parameters.
update_integration_gcp_accountB
Update an STS enabled service account.
Inputs: no named parameters.
update_integration_ms_teams_configuration_tenant_based_handleB
Update a tenant-based handle from the Datadog Microsoft Teams integration.
Inputs: no named parameters.
update_integration_ms_teams_configuration_workflows_webhook_handleB
Update a Workflows webhook handle from the Datadog Microsoft Teams integration.
Inputs: no named parameters.
update_integration_opsgenie_serviceB
Update a single service object in the Datadog Opsgenie integration.
Inputs: no named parameters.
update_integration_pagerduty_configuration_serviceB
Update a single service object in the Datadog-PagerDuty integration.
Inputs: no named parameters.
update_integrations_cloudflare_accountC
Update a Cloudflare account.
Inputs: no named parameters.
update_integrations_confluent_cloud_accountB
Update the Confluent account with the provided account ID.
Inputs: no named parameters.
update_integrations_confluent_cloud_account_resourcesC
Update a Confluent resource with the provided resource id for the account associated with the provided account ID.
Inputs: no named parameters.
update_integrations_fastly_accountC
Update a Fastly account.
Inputs: no named parameters.
update_integrations_fastly_account_servicesB
Update a Fastly service for an account.
Inputs: no named parameters.
update_integration_slack_configuration_account_channelsB
Update a channel used in your Datadog-Slack integration.
Inputs: no named parameters.
update_integrations_okta_accountD
Update an Okta account.
Inputs: no named parameters.
update_integration_webhooks_configuration_custom_variableD
Updates the endpoint with the name <CUSTOM_VARIABLE_NAME>.
Inputs: no named parameters.
update_integration_webhooks_configuration_webhookC
Updates the endpoint with the name <WEBHOOK_NAME>.
Inputs: no named parameters.
update_ip_allowlistsB
Edit the entries in the IP allowlist, and enable or disable it.
Inputs: no named parameters.
update_logs_config_archiveA
Update a given archive configuration.
Note: Using this method updates your archive configuration by replacing your current configuration with the new one sent to your Datadog organization.
Inputs: no named parameters.
update_logs_config_archive_ordersA
Update the order of your archives. Since logs are processed sequentially, reordering an archive may change the structure and content of the data processed by other archives.
Note: Using the PUT method updates your archive's order by replacing the current order
with the new one.
Inputs: no named parameters.
update_logs_config_custom_destinationB
Update the given fields of a specific custom destination in your organization.
Inputs: no named parameters.
update_logs_config_indexeB
Update an index as identified by its name. Returns the Index object passed in the request body when the request is successful.
Using the PUT method updates your index’s configuration by replacing
your current configuration with the new one sent to your Datadog organization.
Inputs: no named parameters.
update_logs_config_index_ordersC
This endpoint updates the index order of your organization. It returns the index order object passed in the request body when the request is successful.
Inputs: no named parameters.
update_logs_config_metricC
Update a specific log-based metric from your organization. Returns the log-based metric object from the request body when the request is successful.
Inputs: no named parameters.
update_logs_config_pipelineA
Update a given pipeline configuration to change it’s processors or their order.
Note: Using this method updates your pipeline configuration by replacing your current configuration with the new one sent to your Datadog organization.
Inputs: no named parameters.
update_logs_config_pipeline_ordersA
Update the order of your pipelines. Since logs are processed sequentially, reordering a pipeline may change the structure and content of the data processed by other pipelines and their processors.
Note: Using the PUT method updates your pipeline order by replacing your current order
with the new one sent to your Datadog organization.
Inputs: no named parameters.
update_metricB
Edit metadata of a specific metric. Find out more about supported types.
Inputs: no named parameters.
update_metric_tagsA
Update the tag configuration of a metric or percentile aggregations of a distribution metric or custom aggregations
of a count, rate, or gauge metric. By setting exclude_tags_mode to true the behavior is changed
from an allow-list to a deny-list, and tags in the defined list will not be queryable.
Can only be used with application keys from users with the Manage Tags for Metrics permission. This endpoint requires
a tag configuration to be created first.
Inputs: no named parameters.
update_monitorD
Edit the specified monitor.
Inputs: no named parameters.
update_monitor_notification_ruleC
Updates a monitor notification rule by rule_id.
Inputs: no named parameters.
update_monitor_policyC
Edit a monitor configuration policy.
Inputs: no named parameters.
update_monitor_v1D
Update a monitor
Inputs: no named parameters.
update_ndm_tags_deviceB
Update the tags for a device.
Inputs: no named parameters.
update_notebookC
Update a notebook using the specified ID.
Inputs: no named parameters.
update_on_call_escalation_policyC
Update an on-call escalation policy
Inputs: no named parameters.
update_on_call_scheduleC
Update a new on-call schedule
Inputs: no named parameters.
update_on_call_team_routing_rulesB
Set a team's on-call routing rules
Inputs: no named parameters.
update_orgD
Update your organization.
Inputs: no named parameters.
update_org_configC
Update the value of a specific Org Config.
Inputs: no named parameters.
update_powerpackC
Update a powerpack.
Inputs: no named parameters.
update_remote_config_products_asm_waf_custom_ruleC
Update a specific WAF custom Rule. Returns the Custom Rule object when the request is successful.
Inputs: no named parameters.
update_remote_config_products_asm_waf_exclusion_filterB
Update a specific WAF exclusion filter using its identifier. Returns the exclusion filter object when the request is successful.
Inputs: no named parameters.
update_remote_config_products_cws_agent_ruleA
Update a specific Workload Protection Agent rule. Returns the agent rule object when the request is successful.
Note: This endpoint is not available for the Government (US1-FED) site. Please reference the (US1-FED) specific resource below.
Inputs: no named parameters.
update_remote_config_products_cws_policyA
Update a specific Workload Protection policy. Returns the policy object when the request is successful.
Note: This endpoint is not available for the Government (US1-FED) site. Please reference the (US1-FED) specific resource below.
Inputs: no named parameters.
update_roleA
Edit a role. Can only be used with application keys belonging to administrators.
Inputs: no named parameters.
update_rum_applicationB
Update the RUM application with given ID in your organization.
Inputs: no named parameters.
update_rum_application_relationships_retention_filtersC
Order RUM retention filters for a RUM application. Returns RUM retention filter objects without attributes from the request body when the request is successful.
Inputs: no named parameters.
update_rum_application_retention_filtersC
Update a RUM retention filter for a RUM application. Returns RUM retention filter objects from the request body when the request is successful.
Inputs: no named parameters.
update_rum_config_metricB
Update a specific rum-based metric from your organization. Returns the rum-based metric object from the request body when the request is successful.
Inputs: no named parameters.
update_security_analytics_signal_add_to_incidentB
Add a security signal to an incident. This makes it possible to search for signals by incident within the signal explorer and to view the signals on the incident timeline.
Inputs: no named parameters.
update_security_monitoring_cloud_workload_security_agent_ruleB
Update a specific agent rule. Returns the agent rule object when the request is successful.
Note: This endpoint should only be used for the Government (US1-FED) site.
Inputs: no named parameters.
update_security_monitoring_configuration_security_filterC
Update a specific security filter. Returns the security filter object when the request is successful.
Inputs: no named parameters.
update_security_monitoring_configuration_suppressionC
Update a specific suppression rule.
Inputs: no named parameters.
update_security_monitoring_ruleA
Update an existing rule. When updating cases, queries or options, the whole field
must be included. For example, when modifying a query all queries must be included.
Default rules can only be updated to be enabled, to change notifications, or to update
the tags (default tags cannot be removed).
Inputs: no named parameters.
update_security_monitoring_signal_assigneeB
Modify the triage assignee of a security signal.
Inputs: no named parameters.
update_security_monitoring_signal_incidentsC
Change the related incidents for a security signal.
Inputs: no named parameters.
update_security_monitoring_signal_stateC
Change the triage state of a security signal.
Inputs: no named parameters.
update_security_signals_notification_ruleC
Partially update the notification rule. All fields are optional; if a field is not provided, it is not updated.
Inputs: no named parameters.
update_security_vulnerabilities_notification_ruleB
Partially update the notification rule. All fields are optional; if a field is not provided, it is not updated.
Inputs: no named parameters.
update_sensitive_data_scanner_config_groupC
Update a group, including the order of the rules. Rules within the group are reordered by including a rules relationship. If the rules relationship is present, its data section MUST contain linkages for all of the rules currently in the group, and MUST NOT contain any others.
Inputs: no named parameters.
update_sensitive_data_scanner_config_ruleC
Update a scanning rule. The request body MUST NOT include a standard_pattern relationship, as that relationship is non-editable. Trying to edit the regex attribute of a rule with a standard_pattern relationship will also result in an error.
Inputs: no named parameters.
update_sensitive_data_scanner_configsD
Reorder the list of groups.
Inputs: no named parameters.
update_service_account_application_keysB
Edit an application key owned by this service account.
Inputs: no named parameters.
update_sloC
Update the specified service level objective object.
Inputs: no named parameters.
update_slo_correctionC
Update the specified SLO correction object.
Inputs: no named parameters.
update_synthetics_private_locationC
Edit a Synthetic private location.
Inputs: no named parameters.
update_synthetics_tests_browserB
Edit the configuration of a Synthetic browser test.
Inputs: no named parameters.
update_synthetics_tests_mobileB
Edit the configuration of a Synthetic Mobile test.
Inputs: no named parameters.
update_synthetics_test_statusB
Pause or start a Synthetic test by changing the status.
Inputs: no named parameters.
update_synthetics_test_v1B
Edit the configuration of a Synthetic API test.
Inputs: no named parameters.
update_synthetics_test_v1_2B
Patch the configuration of a Synthetic test with partial data.
Inputs: no named parameters.
update_synthetics_variableB
Edit a Synthetic global variable.
Inputs: no named parameters.
update_tags_hostB
This endpoint allows you to update/replace all tags in an integration source with those supplied in the request.
Inputs: no named parameters.
update_teamB
Update a team using the team's id.
If the team_links relationship is present, the associated links are updated to be in the order they appear in the array, and any existing team links not present are removed.
Inputs: no named parameters.
update_team_linksD
Update a team link.
Inputs: no named parameters.
update_team_membershipsB
Update a user's membership attributes on a team.
Inputs: no named parameters.
update_team_permission_settingsC
Update a team permission setting for a given team.
Inputs: no named parameters.
update_userB
Edit a user. Can only be used with an application key belonging to an administrator user.
Inputs: no named parameters.
update_workflowB
Update a workflow by ID. This API requires a registered application key.
Inputs: no named parameters.
update_workflow_instances_cancelA
Cancels a specific execution of a given workflow. This API requires a registered application key.
Inputs: no named parameters.
users_createD
Create user
Inputs: no named parameters.
users_getB
Get a user by ID
Inputs: no named parameters.
users_listC
List users
Inputs: no named parameters.
users_updateD
Update user
Inputs: no named parameters.
validate_monitor_v1C
Validate the monitor provided in the request.
Note: Log monitors require an unscoped App Key.
Inputs: no named parameters.
validate_monitor_v1_2C
Validate the monitor provided in the request.
Inputs: no named parameters.
validate_resourcesB
Check if the API key (not the APP key) is valid. If invalid, a 403 is returned.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 670 tools
The tools are generally distinct within their specific domains (e.g., create_monitor vs. delete_monitor), but there is significant overlap across similar operations for different resources (e.g., multiple create/delete/get tools for various integrations like AWS, Azure, Slack). The descriptions help clarify the target resource, but the sheer volume (670 tools) makes it challenging to distinguish between similar tools without careful reading. Some redundancy exists, such as create_dashboard and create_dashboard_v1, which could confuse agents.
Most tools follow a consistent verb_noun pattern (e.g., create_monitor, get_slo, update_user), which is predictable and readable. However, there are minor deviations, such as tools like downtimes_cancel and downtimes_list that use a noun_verb format, and some tools with suffixes like _v1 or _v2 (e.g., create_dashboard_v1). Overall, the naming is largely consistent, aiding in navigation despite the large set.
With 670 tools, the count is extremely high, far exceeding the typical well-scoped range of 3-15 tools. While Datadog is a comprehensive monitoring platform, this many tools creates a heavy cognitive load and makes the server difficult to use efficiently. It feels bloated and could overwhelm agents, leading to selection errors or inefficiencies in tool discovery and usage.
The tool set appears highly complete for the Datadog domain, covering a wide range of resources (e.g., monitors, dashboards, logs, integrations) with full CRUD operations (create, get, update, delete) and additional actions like search, aggregate, and validate. There are no obvious gaps; agents should be able to perform most Datadog-related tasks without dead ends, given the extensive coverage across monitoring, security, cost management, and more.
Maintenance
Related MCP Connectors
Manage uptime monitors and incidents and search logs, metrics and traces from an AI assistant.
Query your app's logs, metrics and incidents from your AI assistant.
AI-callable tools for API mocking, testing, monitoring, security, and automation.
Search 16,000+ API operations and 95 built tools by need, then call any of them by name
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with DataDog's observability platform through a standardized interface. Supports monitoring infrastructure, managing events, analyzing logs and metrics, and automating operations like alerts and downtimes.1MIT
- AlicenseBqualityDmaintenanceEnables interaction with Datadog's monitoring and observability platform through the MCP protocol. Supports incident management, monitor status checks, log searches, metrics queries, APM traces, dashboard access, RUM analytics, host management, and downtime scheduling.1327 npmApache 2.0
- FlicenseBqualityDmaintenanceEnables AI assistants to interact with Datadog APIs for querying metrics, logs, events, monitors, and APM traces.164-
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Datadog APIs through natural language, supporting full CRUD operations on metrics, monitors, dashboards, logs, infrastructure, and more.4MIT