-
Notifications
You must be signed in to change notification settings - Fork 167
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
7717613
commit 6690d57
Showing
2 changed files
with
29 additions
and
0 deletions.
There are no files selected for viewing
27 changes: 27 additions & 0 deletions
27
docs/en/observability/handle-no-results-found-message.asciidoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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 <<metrics-reference>>. | ||
|
||
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. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters