From 6690d575a462976cae8d125ebdd69595b70a110e Mon Sep 17 00:00:00 2001 From: dedemorton Date: Tue, 20 Aug 2024 18:13:15 -0700 Subject: [PATCH] Add topic about missing fields --- .../handle-no-results-found-message.asciidoc | 27 +++++++++++++++++++ docs/en/observability/index.asciidoc | 2 ++ 2 files changed, 29 insertions(+) create mode 100644 docs/en/observability/handle-no-results-found-message.asciidoc diff --git a/docs/en/observability/handle-no-results-found-message.asciidoc b/docs/en/observability/handle-no-results-found-message.asciidoc new file mode 100644 index 0000000000..9e2d2e7944 --- /dev/null +++ b/docs/en/observability/handle-no-results-found-message.asciidoc @@ -0,0 +1,27 @@ +[[handle-no-results-found-message]] += Fix "no results found" message + +To correctly render visualizations in the {observability} UI, +the expected fields must be present in the data. For a list of required fields, +refer to <>. + +There are several reasons why a field might be missing from your data. + +**The chart in the UI requires a metric that's not relevant to your host** + +The chart may refer to a field that is not relevant to the type of hosts you are observing. For example, if you're only observing windows hosts, the 'load' metric is not collected because 'load' is not a windows concept. + +**You may not be collecting the required metrics** + +This could be for any of these reasons: + +* The integration that collects the missing metric is not installed. +For example, to collect metrics from your host system, the System integration must be installed. + +* You're not using OpenTelemetry, which automatically maps the fields to the Elastic Common Schema (ECS) expected by the UI. + +TIP: Try onboarding data using one of quickstarts to make sure you have all the fields required by visualizations in the {observability} UI. + +* You have explicitly chosen not to send these metrics. +You may choose to limit the metrics emitted to Elastic to save on space and improve cluster performance. For example, the System integration has options to easily choose which metrics you wish to emit. You can edit the agent policy to begin collecting the missing metric. + diff --git a/docs/en/observability/index.asciidoc b/docs/en/observability/index.asciidoc index 6f349be94f..5b89d721e7 100644 --- a/docs/en/observability/index.asciidoc +++ b/docs/en/observability/index.asciidoc @@ -78,6 +78,8 @@ include::monitor-infra/inspect-metric-anomalies.asciidoc[leveloffset=+2] include::monitor-infra/configure-metrics-sources.asciidoc[leveloffset=+2] +include::handle-no-results-found-message.asciidoc[leveloffset=+2] + include::monitor-infra/metrics-reference.asciidoc[leveloffset=+2] // AWS monitoring