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

[APM] Document known issue with Dependencies Table for RUM services #88202

Closed
sorenlouv opened this issue Jan 13, 2021 · 4 comments · Fixed by #89789
Closed

[APM] Document known issue with Dependencies Table for RUM services #88202

sorenlouv opened this issue Jan 13, 2021 · 4 comments · Fixed by #89789
Assignees
Labels
documentation Team:APM All issues that need APM UI Team support v7.11.0

Comments

@sorenlouv
Copy link
Member

The Dependencies table doesn't show any dependencies even when there are some:

Dependencies Table No dependencies shown
image.png

Service Map shows there are clearly downstream dependencies
image.png

This discrepancy is caused by a bug/missing feature in the RUM agent. It will be fixed in the future but until then the Dependencies table will be empty for RUM services.

Questions

  • How do we communicate this to users?
  • Can we add this to the docs as a known issue?

cc @vigneshshanmugam @jahtalab

@sorenlouv sorenlouv added [zube]: Inbox documentation Team:APM All issues that need APM UI Team support labels Jan 13, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/apm-ui (Team:apm)

@jakommo
Copy link
Contributor

jakommo commented Feb 18, 2021

Hey @sqren is there an issue to track the bug/missing feature?

@vigneshshanmugam
Copy link
Member

@jakommo The issue was already fixed in the APM RUM agent - elastic/apm-agent-rum-js#953 and released as part of v5.6.3

@bmorelli25
Copy link
Member

Updated docs in #91964.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Team:APM All issues that need APM UI Team support v7.11.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants