Skip to content

Commit 6cbbbb6

Browse files
committed
add APM infrastructure
1 parent 5dee56d commit 6cbbbb6

File tree

1 file changed

+27
-5
lines changed

1 file changed

+27
-5
lines changed

solutions/observability/apps/infrastructure.md

Lines changed: 27 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,33 @@ mapped_urls:
44
- https://www.elastic.co/guide/en/serverless/current/observability-apm-infrastructure.html
55
---
66

7-
# Infrastructure
7+
# Infrastructure [observability-apm-infrastructure]
88

9-
% What needs to be done: Align serverless/stateful
9+
::::{admonition} Applications UI Infrastructure is in beta
10+
:class: important
1011

11-
% Use migrated content from existing pages that map to this page:
12+
The Applications UI Infrastructure functionality is in beta and is subject to change. The design and code is less mature than official generally available features and is being provided as-is with no warranties.
1213

13-
% - [ ] ./raw-migrated-files/observability-docs/observability/apm-infrastructure.md
14-
% - [ ] ./raw-migrated-files/docs-content/serverless/observability-apm-infrastructure.md
14+
::::
15+
16+
17+
The **Infrastructure** tab provides information about the containers, pods, and hosts that the selected service is linked to.
18+
19+
* **Pods**: Uses the `kubernetes.pod.name` from the [APM metrics data streams](../../../solutions/observability/apps/metrics.md).
20+
* **Containers**: Uses the `container.id` from the [APM metrics data streams](../../../solutions/observability/apps/metrics.md).
21+
* **Hosts**: If the application is containerized—​if the APM metrics documents include `container.id`-- the `host.name` is used from the infrastructure data streams (filtered by `container.id`). If not, `host.hostname` is used from the APM metrics data streams.
22+
23+
24+
:::{image} ../../../images/serverless-infra.png
25+
:alt: Example view of the Infrastructure tab in the Applications UI
26+
:class: screenshot
27+
:::
28+
29+
IT ops and software reliability engineers (SREs) can use this tab to quickly find a service’s underlying infrastructure resources when debugging a problem. Knowing what infrastructure is related to a service allows you to remediate issues by restarting, killing hanging instances, changing configuration, rolling back deployments, scaling up, scaling out, and so on.
30+
31+
::::{admonition} Why is the infrastructure tab empty?
32+
:class: tip
33+
34+
If there is no data in the Application UI’s infrastructure tab for a selected service, you can read more about why this happens and how to fix it in the [troubleshooting docs](../../../troubleshoot/observability/apm/common-problems.md#troubleshooting-apm-infra-data).
35+
36+
::::

0 commit comments

Comments
 (0)