datadog-observability

Automate Datadog tracing and StatsD metrics for Go services.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/bjaus/dotfiles --skill datadog-observability
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: datadog-observability
Source: https://github.com/bjaus/dotfiles/tree/main/plugin/skills/datadog-observability
Command: npx skills add https://github.com/bjaus/dotfiles --skill datadog-observability

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ddtrace-go, datadog-go, datadog-statsd.

What problem does it solve?

This Skill provides a ready-to-use pattern for integrating Datadog observability into Go services, enabling consistent tracing, metrics, and dashboard visibility without rebuilding instrumentation from scratch.

Core Features & Use Cases

  • APM tracing: automatically instrument HTTP handlers and Go routines to generate traces in Datadog.
  • Metrics: send custom and default metrics via StatsD to Datadog for monitoring service performance.
  • Dashboard conventions: standardize dashboards and tags across services for unified observability.
  • Use Case: when you deploy a new Go API, instrument main startup to emit traces and metrics so latency and error rates are visible in Datadog.

Quick Start

Install and run the Datadog agent locally, then initialize the tracer and metrics client in your Go application before starting the server. Use the provided router instrumentation and helper functions to annotate custom operations and ensure consistent tagging across services.

Frequently Asked Questions about datadog-observability

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

FAQPage Schema
How do I instrument a Go backend for Datadog APM tracing?

To instrument Go backends for Datadog APM tracing, initialize the tracer early in main.go and use router instrumentation to automatically generate spans for HTTP handlers and background workers.

What is needed to send StatsD metrics from a Go service to Datadog?

Sending StatsD metrics to Datadog requires a running Datadog agent, a configured StatsD client in your Go application, and a consistent configuration structure to emit custom and default performance data.

Can I standardize dashboard conventions across multiple Go microservices?

Yes, you can standardize dashboard conventions across Go microservices by applying consistent tagging and manual span helpers during instrumentation, ensuring unified visibility for latency and error rates.

What's the best way to add custom spans to Go routines in Datadog?

The best way to add custom spans to Go routines is using manual span helper functions alongside automatic HTTP handler instrumentation, allowing you to annotate specific operations within your backend workers.

Do I need a Datadog agent running locally to use ddtrace-go instrumentation?

Yes, a running Datadog agent is required to collect traces and StatsD metrics emitted by the ddtrace-go library, acting as the bridge between your Go application and Datadog dashboards.