Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Port PR #4183 to serverless #4204

Merged
merged 1 commit into from
Aug 30, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
@@ -0,0 +1,47 @@
---
slug: /serverless/observability/handle-no-results-found-message
title: Understanding "no results found" message
description: Learn about the reasons for "no results found" messages and how to fix them.
tags: [ 'serverless', 'observability', 'how to' ]
---

<p><DocBadge template="technical preview" /></p>

To correctly render visualizations in the ((observability)) UI,
all metrics used by the UI must be present in the collected data.
For a description of these metrics,
refer to <DocLink slug="/serverless/observability/metrics-reference"/>.

There are several reasons why metrics might be missing from the collected data:

**The visualization requires a metric that's not relevant to your monitored hosts**

For example, if you're only observing Windows hosts, the 'load' metric is not collected because 'load' is not a Windows concept.
In this situation, you can ignore the "no results found" message.

**You may not be collecting all the required metrics**

This could be for any of these reasons:

* The integration that collects the missing metrics is not installed.
For example, to collect metrics from your host system, you can use the [System integration](((integrations-docs))/system).
To fix the problem, install the integration and configure it to send the missing metrics.

<DocCallOut title="Tip">
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.
</DocCallOut>

* 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.

<DocCallOut title="Tip">
Follow our OpenTelemetry quickstart under **Observability** → **Add data** → **Monitor infrastructure** to make sure OpenTelemetry data is correctly mapped to ECS-compliant fields.
</DocCallOut>

{/* TODO: Make quickstart an active link after the docs are merged. */}

* You have explicitly chosen not to send these metrics.
You may choose to limit the metrics sent to Elastic to save on space and improve cluster performance.
For example, the System integration has options to choose which metrics you want to send.
You can [edit the integration policy](((fleet-guide))/edit-or-delete-integration-policy.html) to begin collecting the missing metrics. For example:

![Screenshot showing system cpu and diskio metrics selected for collection](../images/turn-on-system-metrics.png)
23 changes: 23 additions & 0 deletions docs/en/serverless/infra-monitoring/troubleshooting-infra.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
---
slug: /serverless/observability/troubleshooting-infrastructure-monitoring
title: Troubleshooting
description: Learn how to troubleshoot issues with infrastructure monitoring.
tags: [ 'serverless', 'observability', 'how to' ]
---

<p><DocBadge template="technical preview" /></p>

Learn how to troubleshoot common issues on your own or ask for help.

* <DocLink slug="/serverless/observability/handle-no-results-found-message" />

## Elastic Support

We offer a support experience unlike any other.
Our team of professionals 'speak human and code' and love making your day.
[Learn more about subscriptions](https://www.elastic.co/subscriptions).

## Discussion forum

For other questions and feature requests,
visit our [discussion forum](https://discuss.elastic.co/c/observability).
8 changes: 8 additions & 0 deletions docs/en/serverless/serverless-observability.docnav.json
Original file line number Diff line number Diff line change
Expand Up @@ -374,6 +374,14 @@
"slug": "/serverless/observability/configure-intra-settings",
"classic-sources": ["enObservabilityConfigureSettings"]
},
{
"slug": "/serverless/observability/troubleshooting-infrastructure-monitoring",
"items": [
{
"slug": "/serverless/observability/handle-no-results-found-message"
}
]
},
{
"slug": "/serverless/observability/metrics-reference",
"classic-sources": ["enObservabilityMetricsReference"],
Expand Down
Loading