Productivity - Setup Guide

How to set up Datadog

Otto's honest, no-fluff walkthrough. Every step here is what we'd actually do if we were sitting at your keyboard. Real gotchas first, real steps second, and a link to the personalized version at the bottom.

Read these before you start

• **Custom metrics cardinality is the observability world's most infamous surprise bill**: one poorly-tagged metric with a high-cardinality tag like customer_id can jump from a few unique metric combos into the thousands, and at $0.05 per 100 metrics/month a Kubernetes cluster with Prometheus exporters can easily generate 50,000+ custom metrics, adding $2,450/month on top of host costs - engineering teams have received six-figure bills from a single metric misconfiguration (Better Stack Datadog pricing gotchas, SigNoz custom metrics pricing, and OneUptime Datadog pricing analysis, 2026).
• All metrics sent via OpenTelemetry are billed as custom metrics on Datadog - the "OTel is free" instinct is wrong.
• Log ingest and log indexing are separate line items - ingest is cheap, indexing is where the bill grows.
• Enable Log Rehydration only when you need it; long-term retention re-indexed later still costs.
• Retention policies for logs default to short - configure explicitly or historical debugging goes dark.
• APM traces are sampled by default - the sampling rate controls both cost and diagnostic coverage.

The 7-step setup

1. 1

   Create your Datadog account

   Sign up at the link below. Free tier available - no card required. Use your business email so you can invite teammates later.

   Open Datadog signup
2. 2

   Complete the initial onboarding

   Skip the marketing questionnaires when you can. Fill only the fields that actually configure the product - name, timezone, your first workspace or project. If Datadog pushes you into a setup wizard, take it - it usually accelerates the first productive session.

3. 3

   Connect your existing tools

   Wire Datadog into the rest of your stack. The integrations that most people set up first: 600+ native integrations - AWS, GCP, Azure, Kubernetes, Docker, Postgres, MySQL, MongoDB, Redis, Elasticsearch, Nginx, HAProxy, Jenkins, GitHub, GitLab, PagerDuty, Slack, Microsoft Teams, Salesforce, Snowflake, Databricks, OpenAI, Anthropic. Instrumentation libraries in every mainstream language for.... Do these before importing data - clean integration first, data second.

4. 4

   Import your existing data (only what you'll actually use)

   Do NOT bulk-import everything. Import the last 30 days of the ONE workflow you're moving over first. Prove it works. Then import more. Big-bang migrations are how Datadog deployments die in month 3.

5. 5

   Set up your first real workflow

   Pick the single most-frequent task you'll do in Datadog - the daily-driver workflow. Configure it end-to-end. Use it live for a week. Do not touch any other feature yet. Adoption failure comes from teams trying to use everything on day one instead of the one thing that actually pays.

6. 6

   Add your team (if applicable) and set access

   Once your solo workflow works, invite one teammate at a time. Watch them use it. The friction points you missed are the ones they hit. Fix those before scaling to more users. Never invite 20 people at once - you'll get 20 confused people and 0 useful feedback.

7. 7

   Compound with the right pairings

   Recommend Datadog when: business_size is 20+, industry is tech/SaaS/enterprise, engineering headcount is 10+, and the team is already on Kubernetes or complex cloud infrastructure. Do NOT recommend for SMBs, solo founders, agencies, or simple production stacks - the free tier is a trap that leads to shock bills. For small teams that need error tracking, recommend Sentry ($26/month base). For uptime monitoring only, recommend Better Stack or UptimeRobot. Always flag the custom-metrics cardinality...