Use Fleet View to gain insight into observability gaps on your hosts, outdated Agents or OTel Collectors, and Agents with integration issues.

For each Datadog Agent, you can see:

• The Agent version
• Whether the Agent has any unconfigured or misconfigured integrations
• The services that the Agent is monitoring
• The Agent’s Remote Configuration status
• The products that are enabled on the Agent
• Agent Audit Trail events including configuration changes, upgrades, and flares

For each OTel Collector, you can see:

• The Collector version
• The distribution of the Collector
• The configuration YAML of the Collector
• Pipeline and topology views of the Collector

Prerequisites

• Configuration view is enabled by default for Agents and OTel Collectors with version 7.47.0 and later. To enable it manually for older versions, set inventories_configuration_enabled to true in your Agent configuration file, or use the DD_INVENTORIES_CONFIGURATION_ENABLED environment variable.
• Agent integration configuration is enabled by default in Agent version 7.49.0 or later. To enable it manually on older versions, set inventories_checks_configuration_enabled to true in your Agent configuration file, or use the DD_INVENTORIES_CHECKS_CONFIGURATION_ENABLED environment variable.

Examine a Datadog Agent or OpenTelemetry Collector

Select a Datadog Agent or OTel Collector to view its configuration, connected integrations, audit events, and a support tab for sending a remote flare.

Search and filter

Use the search bar at the top of Fleet View to find specific Agents, OTel Collectors, or clusters across your fleet. You can:

• Perform free-text search by hostname or cluster name
• Filter by host and Agent tags, such as operating system, environment (env), team, and enabled products (products_enabled)

Visualize OTel pipelines

The Configuration tab for an OTel Collector includes Pipeline and Topology views. These views provide end-to-end visibility into how telemetry flows through your OTel pipelines.

To access these views:

1. Navigate to Fleet Automation.
2. Filter for OTel Collectors.
3. Select a Collector to open the detail panel.
4. Click the Configuration tab.
5. Select Pipeline or Topology from the View as options.

Pipeline view

The Pipeline view displays the telemetry pipeline for a single OTel Collector. Use the pipeline view to:

• Validate telemetry routing between configured receivers, processors, and exporters.
• Identify data flow issues, such as data drops and bottlenecks, by enabling the Show traffic toggle.
• Investigate pipeline alerts by examining active monitor alerts surfaced on component nodes.

Topology view

The Topology view displays the forwarding chain across OTel Collectors deployed as DaemonSets and gateways. Use the topology view to:

• Validate telemetry routing across Collectors in a DaemonSet-to-gateway architecture.
• Spot data drops and bottlenecks by enabling the Show traffic toggle to overlay data flow rates on each edge.
• Investigate pipeline issues by examining active monitor alerts surfaced on Collector nodes.

View Agent Audit Trail events

The Audit Events tab displays Audit Trail events associated with the selected Agent. Use this tab to:

• Identify configuration changes, API key updates, installs, upgrades, and support flares
• Determine when and where changes were made

Audit Trail event visibility depends on your plan. When Audit Trail is enabled in your organization, you can view Agent events for up to 90 days based on your Audit Trail retention settings. If Audit Trail is not enabled in your organization, you can view the past 24 hours of events.

Send a remote flare

You can send a flare from the Datadog Agent or DDOT Collector after enabling Remote Configuration on the Agent. For instructions, see Send a flare from the Datadog site.

When you contact Datadog Support with Remote Configuration enabled, the Support team may initiate a flare from your environment to help resolve your issue faster.

Kubernetes view

The Kubernetes view lets you see Datadog Agents and OTel Collectors running in Kubernetes environments. It provides a unified view of your fleet across both host-based and containerized infrastructure.

By default, Fleet View lists infrastructure as individual hosts. Use the View by infra type toggle to switch to the Kubernetes view, which shows Agents by Kubernetes cluster instead.

Each row is a cluster managed by the Datadog Operator or Helm chart. The cluster’s Node Agents, Cluster Agent, and Cluster Check Runners appear grouped together rather than as individual hosts.

Prerequisites for Kubernetes view

Most Kubernetes view features are available without version requirements. Specific capabilities require:

To edit configuration from Fleet View, also set the following flags in your Operator configuration: remoteConfigEnabled, remoteUpdatesEnabled, and createControllerRevisions. Editing Helm Chart values from Fleet View is not supported.

View Kubernetes clusters

Clusters are listed alphabetically by cluster name. The table lists each cluster’s name, deployment method (Datadog Operator or Helm), namespace, Agent version, Agent pod status, readiness, age, and number of restarts.

To find a specific cluster, you can search by cluster name.

Click a cluster to view:

• Cluster details, such as environment and tags
• Cluster-level Agents (Cluster Agent and Cluster Check Runners)
• Node Agents

On the Configuration tab, you can view configuration:

• Datadog Operator v1.24 or later: View the DatadogAgent custom resource configuration. With Datadog Operator v1.27 or later, you can also edit the configuration from this tab.
• Datadog Helm Chart v3.157.0 or later: View the Helm Chart values (values.yaml).

Limitations

Compared to the default view, the Kubernetes view has the following limitations:

• You cannot send remote support flares.
• You can see which OTel Collectors are running, but you cannot view their configuration in the Kubernetes view.
• Fleet Automation API access is not available.

Further Reading

お役に立つドキュメント、リンクや記事:

Fleet AutomationDOCUMENTATION Send a flareDOCUMENTATION Install the Datadog Agent on KubernetesDOCUMENTATION