From 32ab1b5eb677a6ce2b497e1920804f9562a681e7 Mon Sep 17 00:00:00 2001 From: Aleksandra Spilkowska Date: Thu, 24 Jul 2025 14:05:31 +0200 Subject: [PATCH 1/5] Add "No data visible in Kibana" - EDOT troubleshooting --- .../ingest/opentelemetry/no-data-in-kibana.md | 107 ++++++++++++++++++ troubleshoot/ingest/opentelemetry/toc.yml | 3 +- 2 files changed, 109 insertions(+), 1 deletion(-) create mode 100644 troubleshoot/ingest/opentelemetry/no-data-in-kibana.md diff --git a/troubleshoot/ingest/opentelemetry/no-data-in-kibana.md b/troubleshoot/ingest/opentelemetry/no-data-in-kibana.md new file mode 100644 index 0000000000..fd716c066c --- /dev/null +++ b/troubleshoot/ingest/opentelemetry/no-data-in-kibana.md @@ -0,0 +1,107 @@ +--- +navigation_title: No data visible in Kibana +description: Learn what to check when no data (logs, metrics, traces) appears in Kibana after setting up EDOT. +applies_to: + stack: + serverless: + observability: + product: + edot_collector: ga +products: + - id: cloud-serverless + - id: observability + - id: edot-collector +--- + +# No logs, metrics, or traces visible in Kibana + +If the EDOT Collector or SDKs appear to be running, but you see no logs, metrics, or traces in the {{kib}} UI, try to use the solutions below to identify and resolve the issue. + +## Symptoms + +* Collector process is consuming CPU/memory but no telemetry data is visible in {{kib}} +* APM services don’t show up in {{kib}} +* Dashboards appear empty or partially loaded +* The Collector is running without crash logs + +## Causes + +This issue is typically caused by one or more of the following: + +* Incorrect export endpoint +* Missing or invalid API key/token +* Network issues, such as proxy misconfigurations +* TLS verification failures +* Misconfigured pipelines or disabled signals + +## Resolution + +Use the following checks to identify and fix common configuration or connectivity issues that can prevent telemetry data from reaching {{kib}}. + +### Check export endpoint + +Make sure the Collector is configured to send data to the correct Elastic endpoint. For example, if using AWS, the endpoint should match this structure: + +```yaml +endpoint: https://.apm..aws.elastic-cloud.com:443 +``` + +If you’re using the managed OTLP endpoint, confirm the region and cluster ID are correct. + +### Verify authentication headers + +Ensure the Collector or SDK includes an API key in the `Authorization` header: + +```yaml +headers: + Authorization: ApiKey +``` + +If you’re using environment variables, confirm the key is set correctly in the runtime context. + +### Review logs for export errors + +Common log messages include: + +``` +permanent error: rpc error: code = Unavailable desc = connection refused +``` + +Also look for: + +* TLS handshake failures +* Invalid character errors, which may indicate proxy or HTML redirect instead of JSON + +Increase verbosity using `--log-level=debug` for deeper insights. + +### Test network connectivity + +You can validate connectivity using `curl`: + +```bash +curl -v https:// -H "Authorization: ApiKey " +``` + +Or use `telnet` or `nc` to verify port 443 is reachable. + + + +### Validate signal configuration + +Check that each pipeline is defined properly in your configuration: + +```yaml +service: + pipelines: + traces: + receivers: [otlp] + processors: [...] + exporters: [otlp] +``` + +If only logs are configured, metrics and traces will not be sent. \ No newline at end of file diff --git a/troubleshoot/ingest/opentelemetry/toc.yml b/troubleshoot/ingest/opentelemetry/toc.yml index c3d2f4afb2..e42b1fabed 100644 --- a/troubleshoot/ingest/opentelemetry/toc.yml +++ b/troubleshoot/ingest/opentelemetry/toc.yml @@ -12,4 +12,5 @@ toc: - file: edot-sdks/java/index.md - file: edot-sdks/nodejs/index.md - file: edot-sdks/php/index.md - - file: edot-sdks/python/index.md \ No newline at end of file + - file: edot-sdks/python/index.md + - file: no-data-in-kibana.md \ No newline at end of file From f26df08d3ed210ab3275a53af133015d5487b745 Mon Sep 17 00:00:00 2001 From: Aleksandra Spilkowska Date: Thu, 24 Jul 2025 14:13:26 +0200 Subject: [PATCH 2/5] Remove empty urls from commented-out sections --- troubleshoot/ingest/opentelemetry/no-data-in-kibana.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/troubleshoot/ingest/opentelemetry/no-data-in-kibana.md b/troubleshoot/ingest/opentelemetry/no-data-in-kibana.md index fd716c066c..40be4d573a 100644 --- a/troubleshoot/ingest/opentelemetry/no-data-in-kibana.md +++ b/troubleshoot/ingest/opentelemetry/no-data-in-kibana.md @@ -72,7 +72,7 @@ Also look for: * TLS handshake failures * Invalid character errors, which may indicate proxy or HTML redirect instead of JSON -Increase verbosity using `--log-level=debug` for deeper insights. +Increase verbosity using `--log-level=debug` for deeper insights. ### Test network connectivity @@ -86,7 +86,7 @@ Or use `telnet` or `nc` to verify port 443 is reachable. From 143f6b72d32ad12833f7888a4c7e11e3b279ed9d Mon Sep 17 00:00:00 2001 From: Aleksandra Spilkowska Date: Mon, 28 Jul 2025 13:03:53 +0200 Subject: [PATCH 3/5] Apply comments --- troubleshoot/ingest/opentelemetry/no-data-in-kibana.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/troubleshoot/ingest/opentelemetry/no-data-in-kibana.md b/troubleshoot/ingest/opentelemetry/no-data-in-kibana.md index 40be4d573a..af43f41951 100644 --- a/troubleshoot/ingest/opentelemetry/no-data-in-kibana.md +++ b/troubleshoot/ingest/opentelemetry/no-data-in-kibana.md @@ -15,7 +15,7 @@ products: # No logs, metrics, or traces visible in Kibana -If the EDOT Collector or SDKs appear to be running, but you see no logs, metrics, or traces in the {{kib}} UI, try to use the solutions below to identify and resolve the issue. +If the EDOT Collector or SDKs appear to be running, but you see no logs, metrics, or traces in the {{kib}} UI, try to use these solutions to identify and resolve the issue. ## Symptoms @@ -33,6 +33,7 @@ This issue is typically caused by one or more of the following: * Network issues, such as proxy misconfigurations * TLS verification failures * Misconfigured pipelines or disabled signals +* Incomplete setup — to capture all telemetry data, you must use the EDOT Collector together with an appropriate EDOT SDKs ## Resolution From 48087827e7f9cb6cc2da17a164dc5a99b41c1f67 Mon Sep 17 00:00:00 2001 From: Aleksandra Spilkowska Date: Mon, 28 Jul 2025 13:04:56 +0200 Subject: [PATCH 4/5] Fix typo --- troubleshoot/ingest/opentelemetry/no-data-in-kibana.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/troubleshoot/ingest/opentelemetry/no-data-in-kibana.md b/troubleshoot/ingest/opentelemetry/no-data-in-kibana.md index af43f41951..65d3291ada 100644 --- a/troubleshoot/ingest/opentelemetry/no-data-in-kibana.md +++ b/troubleshoot/ingest/opentelemetry/no-data-in-kibana.md @@ -33,7 +33,7 @@ This issue is typically caused by one or more of the following: * Network issues, such as proxy misconfigurations * TLS verification failures * Misconfigured pipelines or disabled signals -* Incomplete setup — to capture all telemetry data, you must use the EDOT Collector together with an appropriate EDOT SDKs +* Incomplete setup — to capture all telemetry data, you must use the EDOT Collector together with an appropriate EDOT SDK ## Resolution From 02359c3f6ea51a06310a5dbdfa81a9f43962e134 Mon Sep 17 00:00:00 2001 From: Aleksandra Spilkowska Date: Fri, 1 Aug 2025 12:09:39 +0200 Subject: [PATCH 5/5] Apply comment --- .../ingest/opentelemetry/no-data-in-kibana.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/troubleshoot/ingest/opentelemetry/no-data-in-kibana.md b/troubleshoot/ingest/opentelemetry/no-data-in-kibana.md index 65d3291ada..cfaf81c2dd 100644 --- a/troubleshoot/ingest/opentelemetry/no-data-in-kibana.md +++ b/troubleshoot/ingest/opentelemetry/no-data-in-kibana.md @@ -41,11 +41,15 @@ Use the following checks to identify and fix common configuration or connectivit ### Check export endpoint -Make sure the Collector is configured to send data to the correct Elastic endpoint. For example, if using AWS, the endpoint should match this structure: +Make sure the Collector is configured to send data to the correct Elastic endpoint. -```yaml -endpoint: https://.apm..aws.elastic-cloud.com:443 -``` +To confirm: + +1. Open {{kib}} for your deployment. +2. In the top right, select **Add data**. +3. Select **Application** > **OpenTelemetry**. +4. In the **APM Agents** panel, locate **OpenTelemetry**. +5. Ensure the `endpoint` in your Collector configuration matches exactly. If you’re using the managed OTLP endpoint, confirm the region and cluster ID are correct.