--- title: Metrics Summary description: Consult the full list of metrics reporting to Datadog. breadcrumbs: Docs > Metrics > Metrics Summary --- # Metrics Summary ## Overview{% #overview %} The [Metrics Summary page](https://app.datadoghq.com/metric/summary) displays a list of your metrics reported to Datadog under a specified time frame: the past hour, day, or week. Search your metrics by metric name or tag using the **Metric** or **Tag** search fields: {% image source="https://datadog-docs.imgix.net/images/metrics/summary/tag_advanced_filtering.30693412eb94b6f42c5109244943d9b0.png?auto=format" alt="The metrics summary page with NOT team:* entered in the Tag search bar" /%} **Note**: Tag values are retained in the **Tag** search field for 28 hours. Values not submitted in the past 28 hours do not appear as search options, even if they remain visible in the metric details side panel. You can also discover relevant metrics using enhanced fuzzy matching support in the Metrics search field: {% image source="https://datadog-docs.imgix.net/images/metrics/summary/metric_advanced_filtering_fuzzy.867912fb87d3daf07e05467f9715368f.png?auto=format" alt="The metrics summary page with fuzzy search searching shopist checkout" /%} Tag filtering supports Boolean and wildcard syntax so that you can identify: - Metrics that are tagged with a particular tag key, for example, `team`: `team:*` - Metrics that are missing a particular tag key, for example, `team`: `NOT team:*` ## Facet panel{% #facet-panel %} The search bars provide the most comprehensive set of actions to filter the list of metrics. But facets can also filter your metrics by: - **Configuration**: Metrics with tag configurations - **Percentiles**: Distribution metrics enabled by percentiles/advanced query capabilities - **Historical Metrics**: Metrics that have historical metrics ingestion enabled - **Query Activity**: Metrics not queried in Datadog or by the API in the past 30, 60, or 90 days - **Related Assets**: Metrics that are being used on dashboards, notebooks, monitors, and SLOs - **Metric Type**: Differentiate between distribution and non-distribution metrics (counts, gauges, rates) - **Metric Origin**: The product from which the metric originated (for example, metrics generated from Logs or APM Spans). To learn more about the different metric origin types, see [Metric origin definitions](https://docs.datadoghq.com/metrics/summary/#metric-origin-definitions) ### Definitions{% #definitions %} A metric is **unqueried** if it has not been accessed in monitors, SLOs, executed notebooks, opened dashboards, used in Metrics Explorer queries, or accessed through API calls within the past 30, 60, or 90 days. A metric is considered **used** as long as it exists on an asset, regardless if it has been actively queried. {% image source="https://datadog-docs.imgix.net/images/metrics/summary/facet_panel_2025-02-26.7cdef07c3414f72810739483d448c40b.png?auto=format" alt="Metrics Facet Panel" /%} ## Configuration of multiple metrics{% #configuration-of-multiple-metrics %} Clicking **Configure Metrics** gives you multiple options to configure more than one metric at a time: {% image source="https://datadog-docs.imgix.net/images/metrics/summary/configurationbuttons10-11-2024.433a764d1418c892f0626ee4cc63e164.png?auto=format" alt="Bulk configuration buttons" /%} - **Manage tags**: Configure tags on multiple custom metrics matching a namespace using Metrics without Limits™. {% video url="https://datadog-docs.imgix.net/images/metrics/summary/tags-bulk-config.mp4" /%} - **Enable or disable percentiles**: Manage percentile aggregations across multiple distribution metrics. See the [Distributions page](https://docs.datadoghq.com/metrics/distributions/#bulk-configuration-for-multiple-metrics) for more information. {% image source="https://datadog-docs.imgix.net/images/metrics/summary/percentile_aggregations_toggle_2025-04-16.6a400ccb474e464d9ed992269dc3fe38.png?auto=format" alt="Toggle to manage percentile aggregations" /%} - **Enable or disable historical metrics ingestion**: Manage the ingestion of historical metric data. See the [Historical Metrics Ingestion page](https://docs.datadoghq.com/metrics/custom_metrics/historical_metrics/#bulk-configuration-for-multiple-metrics) for more information. ## Metric details sidepanel{% #metric-details-sidepanel %} Click on any metric name to display its details sidepanel for more information regarding the metric's metadata and tags: {% image source="https://datadog-docs.imgix.net/images/metrics/summary/mwl_sidepanel.9bf8e207fa37826aad4c859cd8ad98f1.jpg?auto=format" alt="Metric panel" /%} ### Metric name{% #metric-name %} The name of your metric in the [Metrics Explorer](https://docs.datadoghq.com/metrics/explorer/), [dashboards](https://docs.datadoghq.com/dashboards/), etc. ### Ingested custom metrics{% #ingested-custom-metrics %} A metric name may emit multiple ingested custom metrics depending on its associated tag value combinations. Ingested custom metrics represent all of the data originally submitted with code. Learn more in the [custom metrics](https://docs.datadoghq.com/metrics/custom_metrics/) documentation. ### Indexed custom metrics{% #indexed-custom-metrics %} Unlike ingested custom metrics, indexed custom metrics represent those that remain queryable across the Datadog platform. This number may be impacted by adding or removing percentile aggregations or by use of Metrics without Limits™. Learn more in the [Metrics without Limits™](https://docs.datadoghq.com/metrics/metrics-without-limits) documentation. ### Hosts{% #hosts %} The total number of hosts reporting a metric. ### Tag values{% #tag-values %} The total number of unique tag values attached to a metric. [Learn more about tagging](https://docs.datadoghq.com/getting_started/tagging/). ### Metrics metadata{% #metrics-metadata %} The metadata attached to your metric. Most of the metadata can be edited on the metric summary page or with the [Datadog API](https://docs.datadoghq.com/api/v1/metrics/#edit-metric-metadata). #### Metric unit{% #metric-unit %} The unit for your metric (byte, second, request, query, etc.). See the [metric unit](https://docs.datadoghq.com/metrics/units/) page for more details. When submitting custom metrics to Datadog, it is possible to change the [unit of measurement](https://app.datadoghq.com/metric/summary) that displays when hovering over the metric in your graph. **Note**: This does not change how a metric graph is displayed. It only changes the units of measurement that raw values are considered as when you hover over a metric. Formatting is automatically applied for readability. For example, bytes (`B`) may be displayed as kilobytes (`KiB`). #### Metric type{% #metric-type %} The type for your metric (gauge, rate, count, distribution). See the [metric type](https://docs.datadoghq.com/metrics/types/) page for more details. **Warning**: Editing the metric type changes that metric's behavior for **ALL** your dashboards and monitors. #### Integration name{% #integration-name %} If the metric is coming from a supported [integration](https://docs.datadoghq.com/integrations/), the metadata lists the integration name. This information cannot be edited. #### Interval{% #interval %} The collection interval for the metric in seconds. #### Metric description{% #metric-description %} The metric description helps you understand what a metric represents, why it exists, and how it is typically used. Use this field to view and update descriptions for your [custom metrics](https://docs.datadoghq.com/metrics/custom_metrics/). Descriptions are pre-populated for metrics coming from supported [integrations](https://docs.datadoghq.com/integrations/). #### AI-generated description{% #ai-generated-description %} For custom metrics with connected source code, Datadog can automatically create AI-generated descriptions to provide additional context. These descriptions are fully editable, and human edits always take precedence. To enable auto-generated descriptions from source code, ensure that you've installed Datadog's [GitHub](https://app.datadoghq.com/integrations/github/configuration), [GitLab](https://app.datadoghq.com/integrations/gitlab-source-code), or [Azure DevOps](https://app.datadoghq.com/integrations/azure-devops-source-code?subPath=configuration) integration and that all your [repositories](https://app.datadoghq.com/source-code/repositories) are connected. {% image source="https://datadog-docs.imgix.net/images/metrics/summary/metric_ai_generated_descriptions_03062026.43cb53e689104c21abed4e80bc969c09.png?auto=format" alt="AI generated descriptions in Metrics sidepanel" /%} ## Source Code{% #source-code %} The Source Code section in the metric side panel provides a centralized view of every custom metric and its underlying context. Use the Source Code section in the metric side panel to identify a metric's source code, understand how it is generated, and determine ownership. It provides visibility into context and ownership, helping you troubleshoot and optimize faster by linking directly to the metric's source file, commit history, and blame data. {% image source="https://datadog-docs.imgix.net/images/metrics/summary/metric_source_code_03262026.5aba77af2726f5343164f1069bd23da1.png?auto=format" alt="Source Code Example in Metrics sidepanel" /%} ### Troubleshooting missing metrics{% #troubleshooting-missing-metrics %} If a metric doesn't appear in Source Code, it may be due to how it's defined. Datadog detects metrics best when names are written as explicit strings. Metrics built using variables, constants, or custom helpers may not be detected. Common reasons for missing metrics: - Metric name is generated dynamically - Metric is emitted through custom wrappers - Repository is not fully indexed Best practice: - Define metric names as explicit strings when possible Example: Sending metric using a variable (not recommended) ```java public static final String METRIC_NAME = "my.metric.name"; statsEmitter.distribution(METRIC_NAME, value, tags); ``` Sending metric as explicit string (recommended): ```java timer = meterRegistry.timer("my.metric.name"); ``` To ensure full coverage of your metric's source code, ensure that you've installed Datadog's [GitHub](https://app.datadoghq.com/integrations/github/configuration), [GitLab](https://app.datadoghq.com/integrations/gitlab-source-code), or [Azure DevOps](https://app.datadoghq.com/integrations/azure-devops-source-code?subPath=configuration) integration and that all your [repositories](https://app.datadoghq.com/source-code/repositories) are connected. ### Tags table{% #tags-table %} The tags table offers multiple ways to explore all of the tag keys and tag values that are actively reporting in your metric's data. Use the tags table to: - Sort tag keys by the **Count column** (count of unique tag values). - Search through the paginated table of tags for a particular tag key. - Export the tags table as a downloadable CSV. - Toggle between tags you've configured on your metric vs the metric's originally submitted tags For any particular tag key, you can: - Inspect all tag values of that tag key. - Use a specific tag `key:value` to further filter the list of metrics displayed on the Metrics Summary page. - Open a graph of this metric filtered by your tag `key:value` pair in the Metrics Explorer. - Copy any tag `key:value` for filtering across the application. {% video url="https://datadog-docs.imgix.net/images/metrics/summary/updated_tags_table.mp4" /%} [Learn more about tagging](https://docs.datadoghq.com/getting_started/tagging/). ### Metrics Related Assets{% #metrics-related-assets %} {% image source="https://datadog-docs.imgix.net/images/metrics/summary/related_assets_dashboards_08_05_2025.f461956dd4a1b5909f087c5760065b30.png?auto=format" alt="Related Assets for a specified metrics name" /%} To determine the value of any metric name to your organization, use Metrics Related Assets. Metrics related assets refers to any dashboard, notebook, monitor, or SLO that queries a particular metric. 1. Scroll to the bottom of the metric's details side panel to the **Related Assets** section. 1. Click the dropdown button to view the type of related asset you are interested in (dashboards, monitors, notebooks, SLOs). You can additionally use the search bar to validate specific assets. 1. The **Tags** column shows exactly which tags are used in each asset. ## Custom Metrics Tags Cardinality Explorer{% #custom-metrics-tags-cardinality-explorer %} {% image source="https://datadog-docs.imgix.net/images/metrics/tagsexplorer.6f42dddf4308be966fb4297f3c75fd94.png?auto=format" alt="Custom Metrics Tags Cardinality Explorer for a spiking metric name" /%} To determine why a particular metric name is emitting a large number of custom metrics, or spiking, use the Custom Metrics Tags Cardinality Explorer. This helps you pinpoint the tag keys driving the spike, which you can immediately exclude using Metrics without Limits™ for cost savings. ## Metrics without Limits™{% #metrics-without-limits %} Metrics without Limits™ provides you control over the size of your custom metrics without requiring any agent or code-level changes. **Note**: Metrics without Limits™ is only available for custom metrics. You can configure tags in bulk by going to **Configure Metrics -> Manage tags** in the [Metrics page](https://app.datadoghq.com/metric/overview), or by clicking the **Manage Tags** button in a metric's details side panel. {% image source="https://datadog-docs.imgix.net/images/metrics/distributions/managetags.58bd042cfe3dececa7cc3becb8f23359.png?auto=format" alt="Configuring tags on a distribution" /%} 1. Click on your custom distribution metric name in the **Metrics Summary** table to open the metrics details side panel. 1. Click the **Manage Tags** button to open the tag configuration modal. 1. Select **Include tags…** or **Exclude tags…** to customize the tags you do or don't want to query for. For more information on tag configuration, see the [Metrics without Limits](https://docs.datadoghq.com/integrations/agent_metrics/) documentation. 1. Preview the effects of your proposed tag configuration with the cardinality estimator before selecting **Save**. **Note**: The cardinality estimator requires the metric to be older than 48 hours. ### Queryable tags{% #queryable-tags %} Once your metric has been configured with Metrics without Limits™, you can view which tags remain Queryable – ultimately those that contribute to *Indexed Custom Metrics* volume. And you can toggle back to all originally submitted and ingested tags that contribute to your *Ingested Custom Metrics* volume. ### Metric origin definitions{% #metric-origin-definitions %} This table shows the mapping between the metric origin as seen in the facet and where it was submitted from: | Metric Origin | Submitted from | | ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | API Catalog | Timeseries sent by the Datadog [Software Catalog](https://docs.datadoghq.com/software_catalog/endpoints/) product from the APIM Endpoint. | | APM | Timeseries sent by the Datadog APM product for metrics generated from traces and span metrics. | | Agent | Timeseries sent by the Datadog Agent, collected from [Agent integrations](https://docs.datadoghq.com/integrations/agent_metrics/), [built-in integrations](https://docs.datadoghq.com/integrations/), [DogStatsD](https://docs.datadoghq.com/metrics/custom_metrics/dogstatsd_metrics_submission/), or [custom Agent checks](https://docs.datadoghq.com/metrics/custom_metrics/agent_metrics_submission/). | | Cloud Security | Timeseries sent by the Datadog [Cloud Security](https://docs.datadoghq.com/security/cloud_security_management/) product. | | Cloud Integrations | Timeseries collected from cloud providers like AWS, Azure, and Google Cloud etc. from their respective integrations. | | DBM | Timeseries sent by the Datadog [Database Monitoring](https://docs.datadoghq.com/database_monitoring/) product, including insights into MySQL, Oracle, and Postgres activities/queries/locks. | | DSM | Timeseries sent by the Datadog [Data Streams Monitoring](https://docs.datadoghq.com/data_streams/) product, for metrics generated from the DSM spans and traces. | | Datadog Exporter | Timeseries sent by the [OpenTelemetry Collector](https://docs.datadoghq.com/opentelemetry/setup/collector_exporter/) or the [Datadog Exporter](https://docs.datadoghq.com/opentelemetry/collector_exporter/). | | Datadog Platform | Timeseries sent by metrics intake that are used to [report metrics usage](https://docs.datadoghq.com/account_management/billing/usage_metrics/). | | Events | Timeseries generated from the Datadog Events platform. | | LLM Observability | Timeseries emitted by the LLM Observability product using the `lmobs_to_metrics` service. | | Logs | Timeseries generated from the Datadog [Logs](https://docs.datadoghq.com/logs/) platform. | | Metrics API | Timeseries sent using Datadog's [OTLP Ingestion endpoint](https://docs.datadoghq.com/opentelemetry/setup/otlp_ingest_in_the_agent/) and OTel receiver with a Datadog integration counterparts or points for estimated usage metrics or Datadog API Client. | | CNM | Timeseries sent by the Datadog [Cloud Network Monitoring](https://docs.datadoghq.com/network_monitoring/cloud_network_monitoring/) product. | | Observability Pipelines | Timeseries sent by the Datadog [Observability Pipielines](https://docs.datadoghq.com/observability_pipelines/) including error and performance metrics. | | Other | Timeseries that don't have a DD integration counterpart. | | Processes | Timeseries generated from the Datadog [Processes](https://docs.datadoghq.com/integrations/process/) product. | | RUM | Timeseries generated from the Datadog [Real User Monitoring](https://docs.datadoghq.com/monitors/types/real_user_monitoring/) product. | | SAAS Integrations | Timeseries collected from popular SAAS platforms like Slack, Docker, PagerDuty etc. | | Serverless | Timeseries sent by the Datadog [Serverless](https://docs.datadoghq.com/serverless/) platform including Function, App Services, Cloud Run, and Container App Metrics. | | Software Catalog | Timeseries sent by the Datadog [Software Catalog](https://docs.datadoghq.com/software_catalog/) product including [Scorecard](https://docs.datadoghq.com/software_catalog/scorecards/) metrics. | | Synthetic Monitoring | Synthetic monitoring and continuous testing metrics generated from the Datadog [Synthetic Monitoring](https://docs.datadoghq.com/synthetics/) product. | | USM | Timeseries generated from the Datadog [Universal Service Monitoring](https://docs.datadoghq.com/universal_service_monitoring/) product. | ## Further reading{% #further-reading %} - [Metrics Explorer](https://docs.datadoghq.com/metrics/explorer/) - [Metrics Distributions](https://docs.datadoghq.com/metrics/distributions/)