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

[work in progress] [apm] Clarify how data is populated in the APM Infrastructure tab #4692

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

colleenmcginnis
Copy link
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>

Copy link
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 added backport-8.x Automated backport to the 8.x branch with mergify backport-8.15 Automated backport with mergify backport-8.16 Automated backport with mergify backport-8.17 Automated backport with mergify needs-dev-review needs-product-review labels Dec 13, 2024
@roshan-elastic
Copy link
Contributor

Hey @colleenmcginnis,

Thanks for this. Let me ask some of the team how this works - it was made a fair while ago.

@kpatticha / @jasonrhodes - Do you know who might be able to evaluate these docs which are explaining how the 'infrastructure' tab works in the service views?

Preview - Infrastructure Tab
Preview - No data shown in the infrastructure tab

@kpatticha
Copy link
Contributor

@roshan-elastic

@MiriamAparicio would you be able to take a look at these documents? I believe you’re the best person to provide input since you worked on the infrastructure tab in the service views.

If your availability is limited, I’m happy to dig into the code and help out

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-8.x Automated backport to the 8.x branch with mergify backport-8.15 Automated backport with mergify backport-8.16 Automated backport with mergify backport-8.17 Automated backport with mergify needs-dev-review needs-product-review
Projects
None yet
3 participants