Skip to content
Tutorials Center
My learning

Topics

Lesson 4 of 37 ยท Getting Started

Datadog UI Tour: Navigation, Products and Key Concepts

A guided tour of the Datadog interface: Infrastructure, Metrics, Logs, APM, Dashboards, Monitors, Notebooks, Service Catalog and the key concepts behind them.

Datadog has many products and the left navigation can feel crowded at first. This lesson gives you a map: what each section is for, which one to open for which question, and the small set of concepts that all sections share. Menu names change as Datadog reorganizes its interface, so treat the names as a guide and use the search box (or Cmd/Ctrl+K) when something has moved.

Where to look

Infrastructure Hosts, containers, processes
Metrics Explore and graph numbers
Logs Search events
APM Traces and services

Four data views

1 / 3

The main sections

Infrastructure lists hosts (Infrastructure List), containers, Kubernetes resources, processes, serverless functions and cloud resources. Open it for "what machines do I have, and are they healthy?". The Host Map colors every host by a metric, so one glance shows the hot ones.

Metrics has the Metrics Summary (search every metric name, see its type, tags and unit) and the Metrics Explorer (graph and compare any metric with scope and grouping).

Logs has the Log Explorer (search, filter, group, visualize) plus Pipelines, Indexes, Archives and Generate Metrics under its configuration area.

APM has the Service Catalog (every service with owner, dependencies and health), Traces, Services pages with latency and error graphs, and Profiling.

Dashboards holds your dashboards, Notebooks and Timeboards/Screenboards (now a single dashboard type with flexible layout). Monitors has the list of monitors, Manage Downtimes, and Triggered Monitors.

Digital Experience has Synthetic Monitoring and Real User Monitoring; Security has code, cloud and workload security; Cost Management covers cloud spend; Organization Settings (from your avatar) has users, keys, roles and audit.

Concepts every page shares

  1. Time range selector. Almost everything has a time picker (past 15 minutes, 1 hour, custom). A global time and a timeframe link keep a dashboard and the explorers in sync.
  2. Scope. The part of your estate you are looking at, written as tags: env:prod, service:checkout, host:web-1. The same scope bar appears in infrastructure, logs and APM.
  3. Facets and tags. A tag is a key:value label on data. A facet is a field you can filter and group by in logs and traces. Reserved ones: host, service, env, version, source, status.
  4. Events. Discrete things that happened: a deploy, an alert, a restart. They appear as markers over graphs.
  5. Unified service tagging. Setting env, service and version on everything so all data lines up. Metrics and tags explains it.

A typical investigation path

flowchart TD
    M["Monitor alert"] --> D["Dashboard for the service"]
    D --> L["Log Explorer, same scope and time"]
    D --> T["APM traces, same scope and time"]
    L --> N["Notebook: record findings"]
    T --> N

A monitor leads to a dashboard, which pivots to logs and traces using the same tags and time window.

Pivots are the product's daily rhythm: from a graph spike you right-click or use View related logs / View related traces, and the new page opens already scoped to the same time and tags.

Reading a query bar

Most places accept the same two small languages. Metric queries look like avg:system.cpu.user{env:prod} by {host}. Log and trace searches look like service:checkout status:error @http.status_code:>=500. You will learn both properly later; for now, recognize that braces {} filter metrics by tags and that @ marks a log attribute rather than a tag.

Python Stand-in: pick the section for a question

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Python Stand-in: build a scope string from tags

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Habits that pay off

  • Use saved views in the Log Explorer and Infrastructure List for the filters you repeat.
  • Favorite dashboards and monitors so they sit at the top of lists.
  • Learn the global search and the keyboard shortcuts; they beat menu hunting.
  • Keep a Notebook per incident: graphs and logs embedded alongside your notes make a ready-made postmortem.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Where do you graph and compare any metric with a scope and grouping?

    The Metrics Explorer lets you choose a metric, filter by tags and group by tags.
  2. 2. What does the @ sign mean in a log search?

    @http.status_code searches a parsed attribute; tags are written without @.
  3. 3. Which page lists every service with its owner and dependencies?

    The Service Catalog (under APM) is the inventory of services.
  4. 4. Why does a pivot from a graph to logs open already scoped?

    Shared tags (env, service, host) and the time range carry over between products.

Summary

  • Infrastructure, Metrics, Logs and APM show data; Dashboards, Monitors and Notebooks act on it; Synthetics, Security and Cost extend it.
  • Tags, facets, scope and the time selector are shared by every page.
  • Investigations move from monitor to dashboard to logs and traces through pivots.
  • Use search, saved views and notebooks to work faster.

Next: Agent Architecture