use-datadog-mcp

Locate logs, traces, and user sessions via Datadog MCP to triage production issues.

219|41|Updated Feb 21, 2024
One-click install
npx skills add https://github.com/proto-at-block/bitkey --skill use-datadog-mcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: use-datadog-mcp
Source: https://github.com/proto-at-block/bitkey/tree/main/app/ai-rules/skills/use-datadog-mcp
Command: npx skills add https://github.com/proto-at-block/bitkey --skill use-datadog-mcp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug production issues by locating logs, traces, and user sessions with Datadog MCP to speed incident resolution.

Core Features & Use Cases

  • Locate relevant logs, traces, and sessions across app flavors and backend services to triage incidents.
  • Correlate installation IDs, session IDs, and account IDs to reconstruct coherent user journeys.
  • Provide structured query strategies and oncall guidance to accelerate debugging and issue resolution.

Quick Start

Start by connecting to the Datadog MCP endpoint and begin collecting logs for the active incident.

Frequently Asked Questions about use-datadog-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug production issues using Datadog logs and traces?

Debug production issues using Datadog MCP by locating logs, traces, and user sessions across app flavors and backend services to triage incidents. You connect to the Datadog MCP endpoint to collect and analyze data for the active incident.

How do I correlate user sessions with backend traces during an incident?

Correlate user sessions with backend traces by using installation IDs, session IDs, and account IDs as query filters. This identifier strategy links user journeys across app flavors and backend services to reconstruct a coherent incident timeline.

What is the best way to triage issues across staging and production environments?

Triage issues across staging and production environments by applying structured query strategies through Datadog MCP. This approach filters logs and traces to assemble a coherent incident timeline across different deployment targets.

Can I use Datadog MCP to locate logs across different app flavors?

Yes, Datadog MCP locates relevant logs, traces, and sessions across app flavors and backend services. It works across development, staging, and production environments to speed up incident resolution.

Do I need specific identifiers to query Datadog for incident resolution?

Yes, you need identifiers such as installation IDs, session IDs, and account IDs to filter data. Using these specific identifiers with query strategies helps locate logs and assemble a coherent incident timeline during oncall triage.

Why does assembling an incident timeline require structured query strategies?

Assembling an incident timeline requires structured query strategies to effectively filter logs, traces, and user sessions in Datadog MCP. This methodology provides oncall guidance to accelerate debugging and issue resolution across environments.