datadog-service-analyzer

Which services in datadog are missing from service catalog?

Status

✅ Implemented! The core functionality is ready to use.

What This Does

Ever wonder if you've got services sending telemetry to Datadog that somehow aren't registered in your service catalog? Yeah, me too. That's the gap this tool fills.

This analyzer digs through your Datadog telemetry data to identify services that are actively sending metrics, traces, or logs but are mysteriously absent from your service catalog. Think of it as a detective for your observability setup— finding those orphaned services that are chattering away but nobody officially knows they exist.

Why You'd Want This

Service Discovery: Uncover services you didn't know were running
Catalog Completeness: Ensure your service catalog actually reflects reality
Compliance: Meet those pesky requirements for complete service inventories
Operational Awareness: Stop being surprised by services in production

How It Works

The tool connects to your Datadog instance, pulls telemetry data across different signal types (metrics, traces, logs), and cross-references against your service catalog to identify the gaps. Simple concept, but surprisingly useful when you're dealing with large, distributed systems where services tend to multiply like rabbits.

Prerequisites

Before running the analyzer, you'll need:

1Password CLI (op) - for retrieving API credentials
curl - for making API requests
jq - for JSON processing

Install these on macOS with:

brew install 1password-cli curl jq

Setup

Store your Datadog credentials in 1Password with these fields:
- api_key - Your Datadog API key
- app_key - Your Datadog application key
- site - Your Datadog site (optional, defaults to datadoghq.com)
Make sure you're signed in to 1Password CLI:

op signin

Usage

Basic Usage

# Run with default settings (last 7 days, table output)
./datadog-service-analyzer.sh

Command Line Options

./datadog-service-analyzer.sh [OPTIONS]

OPTIONS:
    -h, --help              Show help message
    -v, --verbose           Enable verbose output
    -o, --output FORMAT     Output format (json|table|csv) [default: table]
    --op-vault VAULT       1Password vault name [default: datadog]
    --op-item ITEM         1Password item name [default: datadog-api]
    --days DAYS            Days of telemetry data to analyze [default: 7]

Service Analyzer Examples

# Analyze last 14 days with JSON output
./datadog-service-analyzer.sh --output json --days 14

# Use custom 1Password vault and item
./datadog-service-analyzer.sh --op-vault production --op-item datadog-prod

# CSV output for spreadsheet analysis
./datadog-service-analyzer.sh --output csv --days 30

# Verbose mode for troubleshooting
./datadog-service-analyzer.sh --verbose

Team Mapper Examples

# Generate team mappings in JSON format (default)
./service-team-mapper.sh

# Table format for human reading
./service-team-mapper.sh --output table

# CSV format for spreadsheet import
./service-team-mapper.sh --output csv

# Use custom 1Password credentials
./service-team-mapper.sh --op-vault production --op-item datadog-prod

Sample Output

Service Analyzer

Table format (default):

=== Datadog Service Analyzer Results ===

Services found in telemetry: 42
Services in service catalog: 38
Services missing from catalog: 4

Missing services:
  - legacy-payment-processor
  - temp-migration-worker
  - experimental-ml-service
  - orphaned-batch-job

JSON format:

{
  "summary": {
    "services_in_telemetry": 42,
    "services_in_catalog": 38,
    "missing_from_catalog": 4
  },
  "missing_services": [
    "legacy-payment-processor",
    "temp-migration-worker",
    "experimental-ml-service",
    "orphaned-batch-job"
  ]
}

Team Mapper

JSON format (default):

{
  "summary": {
    "total_services": 25,
    "services_with_teams": 18,
    "services_with_org_units": 12
  },
  "services": [
    {
      "service": "payment-api",
      "team": "payments-team",
      "org_unit": "commerce",
      "description": "Handles payment processing",
      "links": [{"name": "repo", "url": "github.com/company/payment-api"}]
    },
    {
      "service": "user-service",
      "team": "identity-team",
      "org_unit": "platform",
      "description": "User management and authentication",
      "links": []
    }
  ]
}

Table format:

=== Service Team Mappings ===

SERVICE                        TEAM                 ORG_UNIT        DESCRIPTION
------------------------------ -------------------- --------------- ------------------------------
payment-api                    payments-team        commerce        Handles payment processing
user-service                   identity-team        platform        User management and auth...
legacy-system                  N/A                  N/A             Legacy monolith service

Available Scripts