-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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] Enable JavaRuntimeAttacher component in Fleet UI integration #127414
Comments
Pinging @elastic/apm-ui (Team:apm) |
With elastic/apm-server#7305 being resolved, I don't think this issue is blocked. @stuartnelson3 or @simitt, can you confirm that? What's the best way to test this end-to-end once the UI component is enabled? Can someone from the UI or Server team do some basic testing with the Java agent team doing more extensive testing? |
Agree, I am not aware of anything blocking from the apm-server side at this point.
How about creating a gh issue describing all the test cases and how to verify if everything works as expected. We can then derive automated tests and docs from this? |
We have some test case definitions here: elastic/apm-agent-java#2196 (comment) But also, would you recommend testing this on staging cloud or with apm-integration-testing? What are the steps to get a stack up and running? |
#127414) (#127790) Co-authored-by: Kibana Machine <[email protected]>
Lines 23 and 60 should be uncommented to enable the
JavaRuntimAttachment
component to be displayed with the Java Agent tutorial in the APM Fleet integration:kibana/x-pack/plugins/apm/public/components/fleet_integration/apm_agents/agent_instructions_mappings.ts
Lines 22 to 60 in 67566ab
This is current blocked on the availability with APM Server: elastic/apm-server#7023No longer blockedThe text was updated successfully, but these errors were encountered: