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

Integration of the APM RUM instrumentation on New Platform. #53466

Closed
vigneshshanmugam opened this issue Dec 18, 2019 · 1 comment · Fixed by #67633
Closed

Integration of the APM RUM instrumentation on New Platform. #53466

vigneshshanmugam opened this issue Dec 18, 2019 · 1 comment · Fixed by #67633

Comments

@vigneshshanmugam
Copy link
Member

Integration of the APM RUM instrumentation on Kibana new Platform.

  • We already have a working instrumentation on the old platform through the injected metadata service.
  • With the instrumentation, we should be able to hook in to the page-load and route-change events and capture those changes via the RUM agent.

More details on how its done for the old platform - #44281

@pgayvallet
Copy link
Contributor

Ping @elastic/kibana-platform for the legacy platform, APM is hooked into the angular router event (see #44281)

Not sure how we want to address this in NP: is ApplicationService.currentAppId$ enough for this, or should we implements a way to 'hook' into ApplicationService.navigateToApp?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants