Conversation
Elastic Docs AI PR menuCheck the box to run an AI review for this pull request.
Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team. |
✅ Vale Linting ResultsNo issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Docs review summary
Focus areas
- Style and clarity: Good overall. One "on-premise" → "on-premises" spelling correction needed (line 28). Structure (Symptoms → Cause → Resolution → Workaround) is clear and well-formed for a troubleshooting page.
- Jargon: "K8s" appears in prose on line 61; should be spelled out as "Kubernetes". All other acronyms (EDOT, OTel) are spelled out on first use.
- Frontmatter and applies_to:
navigation_title,description, andproductsare all present and valid. Theapplies_totag uses correctstack: ga 9.2+syntax but is missing aserverlesskey — needs an explicitserverless: gaorserverless: unavailabledepending on whether the Infrastructure Inventory symptom also affects Serverless Observability users. - Content type fit: Fits the troubleshooting content type well. The Symptoms/Cause/Resolution/Workaround structure matches the expected pattern. No structural concerns.
- Parent issue satisfaction: Satisfied. Issue #5662 requested a public doc for the known EDOT K8s issue. The PR creates a dedicated troubleshooting page and links it from the index. The soft ask to "promote the OTel k8s integration" is partially addressed in the Resolution section.
Nits
- Line 40:
"Add Data"inside a bold list label uses quotation marks for a UI element name; the style guide prefers bold formatting for UI element names. Consider**Add Data**(even if it breaks out of the outer bold label) or restructure the label slightly.
Notes
- The
troubleshooting-infrastructure-monitoring.mdmodification is a single link addition; no issues found there.
Generated by Docs review agent for issue #6243 · ● 516.5K
| navigation_title: Kubernetes Pods and Docker Containers views empty with EDOT | ||
| description: Learn why the Kubernetes Pods and Docker Containers views in the Infrastructure Inventory are empty when using EDOT, and how to resolve it. | ||
| applies_to: | ||
| stack: ga 9.2+ |
There was a problem hiding this comment.
The applies_to frontmatter only tags stack. The parent page (troubleshooting-infrastructure-monitoring.md) covers both stack and serverless observability. Please confirm whether this known issue also affects users sending EDOT Kubernetes data to an Elastic Serverless Observability deployment (the Infrastructure Inventory exists there too). If it does, add serverless: ga (or the correct lifecycle). If it definitely does not apply to serverless, mark it explicitly with serverless: unavailable so the badge renders correctly and readers on serverless know it is out of scope.
applies_to:
stack: ga 9.2+
serverless: unavailable # or: serverless: ga — depending on applicability|
|
||
| This is expected behavior, not a configuration error in the EDOT Collector. | ||
|
|
||
| In version 9.2.0, the `inframetrics` processor was removed from the EDOT Collector Helm charts for Kubernetes and on-premise deployments. Without this processor, data shipped by EDOT is no longer compatible with the Kubernetes Pods and Docker Containers views of the Infrastructure UI, which only support Elastic Agent data formats. |
There was a problem hiding this comment.
"on-premise" → "on-premises". The correct adjective form in standard technical writing is on-premises (referring to the customer's own premises/property). "On-premise" is a common shortening but incorrect.
Suggested fix: ...Helm charts for Kubernetes and on-premises deployments.
|
|
||
| ## Workaround [workaround-kubernetes-pods-docker-containers-empty] | ||
|
|
||
| You can re-add the `inframetrics` processor as it was configured in versions 9.1.x YAML and Helm charts for the EDOT K8s use case. This is not recommended — the future-proof solution is to use the OpenTelemetry Assets dashboards. |
There was a problem hiding this comment.
"K8s" is informal shorthand. Per the Elastic jargon guidelines, spell out "Kubernetes" in documentation prose.
Suggested fix: ...as it was configured in versions 9.1.x YAML and Helm charts for the EDOT Kubernetes use case.
1 participant
This PR:
1/ Creates a new file: troubleshooting-infrastructure-monitoring/kubernetes-pods-docker-containers-empty-otel.md covering symptoms, cause, resolution, and workaround.
2/ Updates the existing file troubleshooting-infrastructure-monitoring.md by adding a link to the new page in the topic list.
Closes #5662
Summary
Generative AI disclosure