|
| 1 | +--- |
| 2 | +slug: /serverless/observability/handle-no-results-found-message |
| 3 | +title: Understanding "no results found" message |
| 4 | +description: Learn about the reasons for "no results found" messages and how to fix them. |
| 5 | +tags: [ 'serverless', 'observability', 'how to' ] |
| 6 | +--- |
| 7 | + |
| 8 | +<p><DocBadge template="technical preview" /></p> |
| 9 | + |
| 10 | +To correctly render visualizations in the ((observability)) UI, |
| 11 | +all metrics used by the UI must be present in the collected data. |
| 12 | +For a description of these metrics, |
| 13 | +refer to <DocLink slug="/serverless/observability/metrics-reference"/>. |
| 14 | + |
| 15 | +There are several reasons why metrics might be missing from the collected data: |
| 16 | + |
| 17 | +**The visualization requires a metric that's not relevant to your monitored hosts** |
| 18 | + |
| 19 | +For example, if you're only observing Windows hosts, the 'load' metric is not collected because 'load' is not a Windows concept. |
| 20 | +In this situation, you can ignore the "no results found" message. |
| 21 | + |
| 22 | +**You may not be collecting all the required metrics** |
| 23 | + |
| 24 | +This could be for any of these reasons: |
| 25 | + |
| 26 | +* The integration that collects the missing metrics is not installed. |
| 27 | +For example, to collect metrics from your host system, you can use the [System integration](((integrations-docs))/system). |
| 28 | +To fix the problem, install the integration and configure it to send the missing metrics. |
| 29 | + |
| 30 | + <DocCallOut title="Tip"> |
| 31 | + Follow one of our quickstarts under **Observability** → **Add data** → **Collect and analyze logs** to make sure the correct integrations are installed and all required metrics are collected. |
| 32 | + </DocCallOut> |
| 33 | + |
| 34 | +* You are not using the Elastic Distribution of the OpenTelemetry Collector, which automatically maps data to the Elastic Common Schema (ECS) fields expected by the visualization. |
| 35 | + |
| 36 | + <DocCallOut title="Tip"> |
| 37 | + Follow our OpenTelemetry quickstart under **Observability** → **Add data** → **Monitor infrastructure** to make sure OpenTelemetry data is correctly mapped to ECS-compliant fields. |
| 38 | + </DocCallOut> |
| 39 | + |
| 40 | +{/* TODO: Make quickstart an active link after the docs are merged. */} |
| 41 | + |
| 42 | +* You have explicitly chosen not to send these metrics. |
| 43 | +You may choose to limit the metrics sent to Elastic to save on space and improve cluster performance. |
| 44 | +For example, the System integration has options to choose which metrics you want to send. |
| 45 | +You can [edit the integration policy](((fleet-guide))/edit-or-delete-integration-policy.html) to begin collecting the missing metrics. For example: |
| 46 | + |
| 47 | +  |
0 commit comments