Skip to content

[8.17](backport #4692) [apm] Clarify how data is populated in the APM Infrastructure tab#4807

Merged
colleenmcginnis merged 1 commit into
8.17from
mergify/bp/8.17/pr-4692
Jan 29, 2025
Merged

[8.17](backport #4692) [apm] Clarify how data is populated in the APM Infrastructure tab#4807
colleenmcginnis merged 1 commit into
8.17from
mergify/bp/8.17/pr-4692

Conversation

@mergify

@mergify mergify Bot commented Jan 29, 2025

Copy link
Copy Markdown
Contributor

Description

Clarifies how data is populated in the Infrastructure tab for a selected service in the Applications UI. This PR also attempts to provide guidance on how to self-diagnose / troubleshoot when the Infrastructure tab does not have any data.

I searched through some GitHub issues and discussion threads in addition to the resources @lucabelluccini linked to in #4359, but I wasn't able to find much information on troubleshooting.

This PR definitely needs more work, but I thought I'd open it to have something for the product/dev teams to respond to. @roshan-elastic can you help me find a technical reviewer? @lucabelluccini does this align with what you were expecting when you opened #4359?

Documentation sets edited in this PR

Check all that apply.

  • Stateful (docs/en/observability/*)
  • Serverless (docs/en/serverless/*)
  • Integrations Developer Guide (docs/en/integrations/*)
  • None of the above

Related issue

Closes #4359

Checklist

  • Product/Engineering Review
  • Writer Review

Follow-up tasks

Select one.

  • This PR does not need to be ported to another doc set because:
    • The concepts in this PR only apply to one doc set (serverless or stateful)
    • The PR contains edits to both doc sets (serverless and stateful)
  • This PR needs to be ported to another doc set:
    • Port to stateful docs: <link to PR or tracking issue>
    • Port to serverless docs: <link to PR or tracking issue>

This is an automatic backport of pull request #4692 done by [Mergify](https://mergify.com).

)

* first draft

* remove code comments

* remove code comment

(cherry picked from commit 6a482ac)
@mergify mergify Bot requested a review from a team as a code owner January 29, 2025 20:57
@mergify mergify Bot added the backport label Jan 29, 2025
@github-actions

Copy link
Copy Markdown
Contributor

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@colleenmcginnis colleenmcginnis enabled auto-merge (squash) January 29, 2025 21:10
@colleenmcginnis colleenmcginnis merged commit 5581a31 into 8.17 Jan 29, 2025
@colleenmcginnis colleenmcginnis deleted the mergify/bp/8.17/pr-4692 branch January 29, 2025 21:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant