Datadog ACTION
Search Events
Search Datadog events: monitor state changes, deployment markers, error spikes, and infrastructure events. Filter by
sources (e.g. nagios,docker), tags (e.g. env:prod,service:web), and priority (normal or low). Time range defaults to last 24h (POSIX timestamps in seconds). To investigate a monitor alert, use Search Monitors first, then search events for the relevant time range. Follow up with Search Logs for deeper investigation. See the docs- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Datadog account once, then configure and run Search Events from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "datadog-search-events",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
datadog: { authProvisionId: "apn_xxxxxxx" },
region: "Region",
start: 10,
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "datadog-search-events",
"configured_props": {
"datadog": { "authProvisionId": "apn_xxxxxxx" },
"region": "Region",
"start": 10
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "datadog",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "datadog-search-events",
arguments: {
region: "Region",
start: 10,
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
region Region | string | The regional site for a Datadog customer Required |
start Start | integer | POSIX timestamp (seconds) for the start of the query window. Defaults to 24 hours ago. Optional |
end End | integer | POSIX timestamp (seconds) for the end of the query window. Defaults to now. Optional |
priority Priority | string | Filter by event priority. Optional |
sources Sources | string | Comma-separated list of sources to filter events. E.g. nagios,hudson. Optional |
tags Tags | string | Comma-separated list of tags to filter events. E.g. env:prod,role:db. Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- datadog-search-events
- Version
- 1.0.2
- App
- Datadog
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗