[APM] Remove the java agent auto-attacher from the APM onbarding#249043
Merged
jennypavlova merged 5 commits intoelastic:mainfrom Jan 15, 2026
Conversation
jennypavlova
added
release_note:skip
Contributor
|
Pinging @elastic/obs-presentation-team (Team:obs-presentation) |
…er-from-the-apm-onbarding
miloszmarcinkowski
approved these changes
Jan 14, 2026
Contributor
miloszmarcinkowski
left a comment
miloszmarcinkowski
left a comment
There was a problem hiding this comment.
LGTM (code review only)
…er-from-the-apm-onbarding
…er-from-the-apm-onbarding
jackshirazi
approved these changes
Jan 15, 2026
Contributor
jackshirazi
left a comment
jackshirazi
left a comment
There was a problem hiding this comment.
Thanks! I didn't see any problems when testing with this snapshot
…er-from-the-apm-onbarding
Contributor
💛 Build succeeded, but was flakyFailed CI StepsTest Failures
Metrics [docs]Module Count
Async chunks
Page load bundle
Unknown metric groupsESLint disabled line counts
Total ESLint disabled count
History
|
Contributor
|
Starting backport for target branches: 8.19, 9.1, 9.2, 9.3 https://github.com/elastic/kibana/actions/runs/21038488863 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jan 15, 2026
…stic#249043) Closes elastic#248894 ## Summary This PR removes the Java agent auto-attacher from the APM onboarding. The Java agent "Auto-Attachment" tab is no longer visible in the Fleet APM integration UI. All related runtime attachment components and code have been removed. The onboarding now only shows manual instrumentation steps for all agents. ## Changes: - Files Deleted: entire `runtime_attachment/` directory + unused translations: - Changed to use PackagePolicyEditExtensionComponentProps for proper Fleet integration typing - Extracts `apmServerUrl` and `secretToken` from `newPolicy` and passes them to child components - Fixed the key prop to use ${agentName}-${variantId} for uniqueness ## How to test - I am creating a cloud deployment with this PR and we should be able to test there - @jackshirazi Could you please verify if everything still works on the agent side with those changes - [x] Tested on cloud ✅ Tested using the PR cloud deployment: - Go to APM -> Fleet -> Agent policies -> Elastic Cloud agent policy -> Edit integration (Edit Elastic APM integration) - The Java auto-attacher tab is not present ✅ <img width="1913" height="1010" alt="image" src="https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068" /> - [x] Tested with Java agent (if needed ❓) (cherry picked from commit da35df4)
Contributor
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
jennypavlova
added a commit
to jennypavlova/kibana
that referenced
this pull request
Jan 15, 2026
…stic#249043) Closes elastic#248894 ## Summary This PR removes the Java agent auto-attacher from the APM onboarding. The Java agent "Auto-Attachment" tab is no longer visible in the Fleet APM integration UI. All related runtime attachment components and code have been removed. The onboarding now only shows manual instrumentation steps for all agents. ## Changes: - Files Deleted: entire `runtime_attachment/` directory + unused translations: - Changed to use PackagePolicyEditExtensionComponentProps for proper Fleet integration typing - Extracts `apmServerUrl` and `secretToken` from `newPolicy` and passes them to child components - Fixed the key prop to use ${agentName}-${variantId} for uniqueness ## How to test - I am creating a cloud deployment with this PR and we should be able to test there - @jackshirazi Could you please verify if everything still works on the agent side with those changes - [x] Tested on cloud ✅ Tested using the PR cloud deployment: - Go to APM -> Fleet -> Agent policies -> Elastic Cloud agent policy -> Edit integration (Edit Elastic APM integration) - The Java auto-attacher tab is not present ✅ <img width="1913" height="1010" alt="image" src="https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068" /> - [x] Tested with Java agent (if needed ❓) (cherry picked from commit da35df4) # Conflicts: # x-pack/solutions/observability/plugins/apm/public/components/fleet_integration/apm_agents/runtime_attachment/runtime_attachment.tsx
jennypavlova
added a commit
to jennypavlova/kibana
that referenced
this pull request
Jan 15, 2026
…stic#249043) Closes elastic#248894 ## Summary This PR removes the Java agent auto-attacher from the APM onboarding. The Java agent "Auto-Attachment" tab is no longer visible in the Fleet APM integration UI. All related runtime attachment components and code have been removed. The onboarding now only shows manual instrumentation steps for all agents. ## Changes: - Files Deleted: entire `runtime_attachment/` directory + unused translations: - Changed to use PackagePolicyEditExtensionComponentProps for proper Fleet integration typing - Extracts `apmServerUrl` and `secretToken` from `newPolicy` and passes them to child components - Fixed the key prop to use ${agentName}-${variantId} for uniqueness ## How to test - I am creating a cloud deployment with this PR and we should be able to test there - @jackshirazi Could you please verify if everything still works on the agent side with those changes - [x] Tested on cloud ✅ Tested using the PR cloud deployment: - Go to APM -> Fleet -> Agent policies -> Elastic Cloud agent policy -> Edit integration (Edit Elastic APM integration) - The Java auto-attacher tab is not present ✅ <img width="1913" height="1010" alt="image" src="https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068" /> - [x] Tested with Java agent (if needed ❓) (cherry picked from commit da35df4) # Conflicts: # x-pack/platform/plugins/private/translations/translations/de-DE.json # x-pack/solutions/observability/plugins/apm/public/components/fleet_integration/apm_agents/runtime_attachment/discovery_rule.tsx # x-pack/solutions/observability/plugins/apm/public/components/fleet_integration/apm_agents/runtime_attachment/edit_discovery_rule.tsx # x-pack/solutions/observability/plugins/apm/public/components/fleet_integration/apm_agents/runtime_attachment/runtime_attachment.tsx
jennypavlova
added a commit
to jennypavlova/kibana
that referenced
this pull request
Jan 15, 2026
…stic#249043) Closes elastic#248894 ## Summary This PR removes the Java agent auto-attacher from the APM onboarding. The Java agent "Auto-Attachment" tab is no longer visible in the Fleet APM integration UI. All related runtime attachment components and code have been removed. The onboarding now only shows manual instrumentation steps for all agents. ## Changes: - Files Deleted: entire `runtime_attachment/` directory + unused translations: - Changed to use PackagePolicyEditExtensionComponentProps for proper Fleet integration typing - Extracts `apmServerUrl` and `secretToken` from `newPolicy` and passes them to child components - Fixed the key prop to use ${agentName}-${variantId} for uniqueness ## How to test - I am creating a cloud deployment with this PR and we should be able to test there - @jackshirazi Could you please verify if everything still works on the agent side with those changes - [x] Tested on cloud ✅ Tested using the PR cloud deployment: - Go to APM -> Fleet -> Agent policies -> Elastic Cloud agent policy -> Edit integration (Edit Elastic APM integration) - The Java auto-attacher tab is not present ✅ <img width="1913" height="1010" alt="image" src="https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068" /> - [x] Tested with Java agent (if needed ❓) (cherry picked from commit da35df4) # Conflicts: # x-pack/platform/plugins/private/translations/translations/de-DE.json # x-pack/platform/plugins/private/translations/translations/fr-FR.json # x-pack/platform/plugins/private/translations/translations/zh-CN.json # x-pack/solutions/observability/plugins/apm/public/components/fleet_integration/apm_agents/runtime_attachment/discovery_rule.tsx # x-pack/solutions/observability/plugins/apm/public/components/fleet_integration/apm_agents/runtime_attachment/edit_discovery_rule.tsx # x-pack/solutions/observability/plugins/apm/public/components/fleet_integration/apm_agents/runtime_attachment/java_agent_version_input.tsx # x-pack/solutions/observability/plugins/apm/public/components/fleet_integration/apm_agents/runtime_attachment/runtime_attachment.tsx
Member
Author
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
jennypavlova
added a commit
that referenced
this pull request
Jan 15, 2026
#249043) (#249279) # Backport This will backport the following commits from `main` to `9.2`: - [[APM] Remove the java agent auto-attacher from the APM onbarding (#249043)](#249043) <!--- Backport version: 10.2.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2026-01-15T16:25:29Z","message":"[APM] Remove the java agent auto-attacher from the APM onbarding (#249043)\n\nCloses #248894\n\n## Summary\nThis PR removes the Java agent auto-attacher from the APM onboarding.\nThe Java agent \"Auto-Attachment\" tab is no longer visible in the Fleet\nAPM integration UI. All related runtime attachment components and code\nhave been removed.\nThe onboarding now only shows manual instrumentation steps for all\nagents.\n\n## Changes: \n- Files Deleted: entire `runtime_attachment/` directory + unused\ntranslations:\n- Changed to use PackagePolicyEditExtensionComponentProps for proper\nFleet integration typing\n- Extracts `apmServerUrl` and `secretToken` from `newPolicy` and passes\nthem to child components\n- Fixed the key prop to use ${agentName}-${variantId} for uniqueness\n\n## How to test\n- I am creating a cloud deployment with this PR and we should be able to\ntest there\n- @jackshirazi Could you please verify if everything still works on the\nagent side with those changes\n\n- [x] Tested on cloud\n\n✅ Tested using the PR cloud deployment: \n- Go to APM -> Fleet -> Agent policies -> Elastic Cloud agent policy ->\nEdit integration (Edit Elastic APM integration)\n- The Java auto-attacher tab is not present ✅ \n\n<img width=\"1913\" height=\"1010\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068\"\n/>\n\n\n- [x] Tested with Java agent (if needed ❓)","sha":"da35df416e9ac9e5c4145828cd69dccc32ebffb4","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","ci:cloud-deploy","v9.4.0","Team:obs-presentation"],"title":"[APM] Remove the java agent auto-attacher from the APM onbarding","number":249043,"url":"https://github.com/elastic/kibana/pull/249043","mergeCommit":{"message":"[APM] Remove the java agent auto-attacher from the APM onbarding (#249043)\n\nCloses #248894\n\n## Summary\nThis PR removes the Java agent auto-attacher from the APM onboarding.\nThe Java agent \"Auto-Attachment\" tab is no longer visible in the Fleet\nAPM integration UI. All related runtime attachment components and code\nhave been removed.\nThe onboarding now only shows manual instrumentation steps for all\nagents.\n\n## Changes: \n- Files Deleted: entire `runtime_attachment/` directory + unused\ntranslations:\n- Changed to use PackagePolicyEditExtensionComponentProps for proper\nFleet integration typing\n- Extracts `apmServerUrl` and `secretToken` from `newPolicy` and passes\nthem to child components\n- Fixed the key prop to use ${agentName}-${variantId} for uniqueness\n\n## How to test\n- I am creating a cloud deployment with this PR and we should be able to\ntest there\n- @jackshirazi Could you please verify if everything still works on the\nagent side with those changes\n\n- [x] Tested on cloud\n\n✅ Tested using the PR cloud deployment: \n- Go to APM -> Fleet -> Agent policies -> Elastic Cloud agent policy ->\nEdit integration (Edit Elastic APM integration)\n- The Java auto-attacher tab is not present ✅ \n\n<img width=\"1913\" height=\"1010\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068\"\n/>\n\n\n- [x] Tested with Java agent (if needed ❓)","sha":"da35df416e9ac9e5c4145828cd69dccc32ebffb4"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/249043","number":249043,"mergeCommit":{"message":"[APM] Remove the java agent auto-attacher from the APM onbarding (#249043)\n\nCloses #248894\n\n## Summary\nThis PR removes the Java agent auto-attacher from the APM onboarding.\nThe Java agent \"Auto-Attachment\" tab is no longer visible in the Fleet\nAPM integration UI. All related runtime attachment components and code\nhave been removed.\nThe onboarding now only shows manual instrumentation steps for all\nagents.\n\n## Changes: \n- Files Deleted: entire `runtime_attachment/` directory + unused\ntranslations:\n- Changed to use PackagePolicyEditExtensionComponentProps for proper\nFleet integration typing\n- Extracts `apmServerUrl` and `secretToken` from `newPolicy` and passes\nthem to child components\n- Fixed the key prop to use ${agentName}-${variantId} for uniqueness\n\n## How to test\n- I am creating a cloud deployment with this PR and we should be able to\ntest there\n- @jackshirazi Could you please verify if everything still works on the\nagent side with those changes\n\n- [x] Tested on cloud\n\n✅ Tested using the PR cloud deployment: \n- Go to APM -> Fleet -> Agent policies -> Elastic Cloud agent policy ->\nEdit integration (Edit Elastic APM integration)\n- The Java auto-attacher tab is not present ✅ \n\n<img width=\"1913\" height=\"1010\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068\"\n/>\n\n\n- [x] Tested with Java agent (if needed ❓)","sha":"da35df416e9ac9e5c4145828cd69dccc32ebffb4"}},{"url":"https://github.com/elastic/kibana/pull/249264","number":249264,"branch":"9.3","state":"OPEN"}]}] BACKPORT-->
jennypavlova
added a commit
that referenced
this pull request
Jan 15, 2026
#249043) (#249281) # Backport This will backport the following commits from `main` to `9.1`: - [[APM] Remove the java agent auto-attacher from the APM onbarding (#249043)](#249043) <!--- Backport version: 10.2.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2026-01-15T16:25:29Z","message":"[APM] Remove the java agent auto-attacher from the APM onbarding (#249043)\n\nCloses #248894\n\n## Summary\nThis PR removes the Java agent auto-attacher from the APM onboarding.\nThe Java agent \"Auto-Attachment\" tab is no longer visible in the Fleet\nAPM integration UI. All related runtime attachment components and code\nhave been removed.\nThe onboarding now only shows manual instrumentation steps for all\nagents.\n\n## Changes: \n- Files Deleted: entire `runtime_attachment/` directory + unused\ntranslations:\n- Changed to use PackagePolicyEditExtensionComponentProps for proper\nFleet integration typing\n- Extracts `apmServerUrl` and `secretToken` from `newPolicy` and passes\nthem to child components\n- Fixed the key prop to use ${agentName}-${variantId} for uniqueness\n\n## How to test\n- I am creating a cloud deployment with this PR and we should be able to\ntest there\n- @jackshirazi Could you please verify if everything still works on the\nagent side with those changes\n\n- [x] Tested on cloud\n\n✅ Tested using the PR cloud deployment: \n- Go to APM -> Fleet -> Agent policies -> Elastic Cloud agent policy ->\nEdit integration (Edit Elastic APM integration)\n- The Java auto-attacher tab is not present ✅ \n\n<img width=\"1913\" height=\"1010\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068\"\n/>\n\n\n- [x] Tested with Java agent (if needed ❓)","sha":"da35df416e9ac9e5c4145828cd69dccc32ebffb4","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","ci:cloud-deploy","v9.4.0","Team:obs-presentation"],"title":"[APM] Remove the java agent auto-attacher from the APM onbarding","number":249043,"url":"https://github.com/elastic/kibana/pull/249043","mergeCommit":{"message":"[APM] Remove the java agent auto-attacher from the APM onbarding (#249043)\n\nCloses #248894\n\n## Summary\nThis PR removes the Java agent auto-attacher from the APM onboarding.\nThe Java agent \"Auto-Attachment\" tab is no longer visible in the Fleet\nAPM integration UI. All related runtime attachment components and code\nhave been removed.\nThe onboarding now only shows manual instrumentation steps for all\nagents.\n\n## Changes: \n- Files Deleted: entire `runtime_attachment/` directory + unused\ntranslations:\n- Changed to use PackagePolicyEditExtensionComponentProps for proper\nFleet integration typing\n- Extracts `apmServerUrl` and `secretToken` from `newPolicy` and passes\nthem to child components\n- Fixed the key prop to use ${agentName}-${variantId} for uniqueness\n\n## How to test\n- I am creating a cloud deployment with this PR and we should be able to\ntest there\n- @jackshirazi Could you please verify if everything still works on the\nagent side with those changes\n\n- [x] Tested on cloud\n\n✅ Tested using the PR cloud deployment: \n- Go to APM -> Fleet -> Agent policies -> Elastic Cloud agent policy ->\nEdit integration (Edit Elastic APM integration)\n- The Java auto-attacher tab is not present ✅ \n\n<img width=\"1913\" height=\"1010\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068\"\n/>\n\n\n- [x] Tested with Java agent (if needed ❓)","sha":"da35df416e9ac9e5c4145828cd69dccc32ebffb4"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/249043","number":249043,"mergeCommit":{"message":"[APM] Remove the java agent auto-attacher from the APM onbarding (#249043)\n\nCloses #248894\n\n## Summary\nThis PR removes the Java agent auto-attacher from the APM onboarding.\nThe Java agent \"Auto-Attachment\" tab is no longer visible in the Fleet\nAPM integration UI. All related runtime attachment components and code\nhave been removed.\nThe onboarding now only shows manual instrumentation steps for all\nagents.\n\n## Changes: \n- Files Deleted: entire `runtime_attachment/` directory + unused\ntranslations:\n- Changed to use PackagePolicyEditExtensionComponentProps for proper\nFleet integration typing\n- Extracts `apmServerUrl` and `secretToken` from `newPolicy` and passes\nthem to child components\n- Fixed the key prop to use ${agentName}-${variantId} for uniqueness\n\n## How to test\n- I am creating a cloud deployment with this PR and we should be able to\ntest there\n- @jackshirazi Could you please verify if everything still works on the\nagent side with those changes\n\n- [x] Tested on cloud\n\n✅ Tested using the PR cloud deployment: \n- Go to APM -> Fleet -> Agent policies -> Elastic Cloud agent policy ->\nEdit integration (Edit Elastic APM integration)\n- The Java auto-attacher tab is not present ✅ \n\n<img width=\"1913\" height=\"1010\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068\"\n/>\n\n\n- [x] Tested with Java agent (if needed ❓)","sha":"da35df416e9ac9e5c4145828cd69dccc32ebffb4"}},{"url":"https://github.com/elastic/kibana/pull/249264","number":249264,"branch":"9.3","state":"OPEN"}]}] BACKPORT-->
jennypavlova
added a commit
that referenced
this pull request
Jan 15, 2026
…ng (#249043) (#249282) # Backport This will backport the following commits from `main` to `8.19`: - [[APM] Remove the java agent auto-attacher from the APM onbarding (#249043)](#249043) <!--- Backport version: 10.2.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2026-01-15T16:25:29Z","message":"[APM] Remove the java agent auto-attacher from the APM onbarding (#249043)\n\nCloses #248894\n\n## Summary\nThis PR removes the Java agent auto-attacher from the APM onboarding.\nThe Java agent \"Auto-Attachment\" tab is no longer visible in the Fleet\nAPM integration UI. All related runtime attachment components and code\nhave been removed.\nThe onboarding now only shows manual instrumentation steps for all\nagents.\n\n## Changes: \n- Files Deleted: entire `runtime_attachment/` directory + unused\ntranslations:\n- Changed to use PackagePolicyEditExtensionComponentProps for proper\nFleet integration typing\n- Extracts `apmServerUrl` and `secretToken` from `newPolicy` and passes\nthem to child components\n- Fixed the key prop to use ${agentName}-${variantId} for uniqueness\n\n## How to test\n- I am creating a cloud deployment with this PR and we should be able to\ntest there\n- @jackshirazi Could you please verify if everything still works on the\nagent side with those changes\n\n- [x] Tested on cloud\n\n✅ Tested using the PR cloud deployment: \n- Go to APM -> Fleet -> Agent policies -> Elastic Cloud agent policy ->\nEdit integration (Edit Elastic APM integration)\n- The Java auto-attacher tab is not present ✅ \n\n<img width=\"1913\" height=\"1010\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068\"\n/>\n\n\n- [x] Tested with Java agent (if needed ❓)","sha":"da35df416e9ac9e5c4145828cd69dccc32ebffb4","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","ci:cloud-deploy","v9.4.0","Team:obs-presentation"],"title":"[APM] Remove the java agent auto-attacher from the APM onbarding","number":249043,"url":"https://github.com/elastic/kibana/pull/249043","mergeCommit":{"message":"[APM] Remove the java agent auto-attacher from the APM onbarding (#249043)\n\nCloses #248894\n\n## Summary\nThis PR removes the Java agent auto-attacher from the APM onboarding.\nThe Java agent \"Auto-Attachment\" tab is no longer visible in the Fleet\nAPM integration UI. All related runtime attachment components and code\nhave been removed.\nThe onboarding now only shows manual instrumentation steps for all\nagents.\n\n## Changes: \n- Files Deleted: entire `runtime_attachment/` directory + unused\ntranslations:\n- Changed to use PackagePolicyEditExtensionComponentProps for proper\nFleet integration typing\n- Extracts `apmServerUrl` and `secretToken` from `newPolicy` and passes\nthem to child components\n- Fixed the key prop to use ${agentName}-${variantId} for uniqueness\n\n## How to test\n- I am creating a cloud deployment with this PR and we should be able to\ntest there\n- @jackshirazi Could you please verify if everything still works on the\nagent side with those changes\n\n- [x] Tested on cloud\n\n✅ Tested using the PR cloud deployment: \n- Go to APM -> Fleet -> Agent policies -> Elastic Cloud agent policy ->\nEdit integration (Edit Elastic APM integration)\n- The Java auto-attacher tab is not present ✅ \n\n<img width=\"1913\" height=\"1010\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068\"\n/>\n\n\n- [x] Tested with Java agent (if needed ❓)","sha":"da35df416e9ac9e5c4145828cd69dccc32ebffb4"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/249043","number":249043,"mergeCommit":{"message":"[APM] Remove the java agent auto-attacher from the APM onbarding (#249043)\n\nCloses #248894\n\n## Summary\nThis PR removes the Java agent auto-attacher from the APM onboarding.\nThe Java agent \"Auto-Attachment\" tab is no longer visible in the Fleet\nAPM integration UI. All related runtime attachment components and code\nhave been removed.\nThe onboarding now only shows manual instrumentation steps for all\nagents.\n\n## Changes: \n- Files Deleted: entire `runtime_attachment/` directory + unused\ntranslations:\n- Changed to use PackagePolicyEditExtensionComponentProps for proper\nFleet integration typing\n- Extracts `apmServerUrl` and `secretToken` from `newPolicy` and passes\nthem to child components\n- Fixed the key prop to use ${agentName}-${variantId} for uniqueness\n\n## How to test\n- I am creating a cloud deployment with this PR and we should be able to\ntest there\n- @jackshirazi Could you please verify if everything still works on the\nagent side with those changes\n\n- [x] Tested on cloud\n\n✅ Tested using the PR cloud deployment: \n- Go to APM -> Fleet -> Agent policies -> Elastic Cloud agent policy ->\nEdit integration (Edit Elastic APM integration)\n- The Java auto-attacher tab is not present ✅ \n\n<img width=\"1913\" height=\"1010\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068\"\n/>\n\n\n- [x] Tested with Java agent (if needed ❓)","sha":"da35df416e9ac9e5c4145828cd69dccc32ebffb4"}},{"url":"https://github.com/elastic/kibana/pull/249264","number":249264,"branch":"9.3","state":"OPEN"}]}] BACKPORT-->
kibanamachine
added a commit
that referenced
this pull request
Jan 16, 2026
#249043) (#249264) # Backport This will backport the following commits from `main` to `9.3`: - [[APM] Remove the java agent auto-attacher from the APM onbarding (#249043)](#249043) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2026-01-15T16:25:29Z","message":"[APM] Remove the java agent auto-attacher from the APM onbarding (#249043)\n\nCloses #248894\n\n## Summary\nThis PR removes the Java agent auto-attacher from the APM onboarding.\nThe Java agent \"Auto-Attachment\" tab is no longer visible in the Fleet\nAPM integration UI. All related runtime attachment components and code\nhave been removed.\nThe onboarding now only shows manual instrumentation steps for all\nagents.\n\n## Changes: \n- Files Deleted: entire `runtime_attachment/` directory + unused\ntranslations:\n- Changed to use PackagePolicyEditExtensionComponentProps for proper\nFleet integration typing\n- Extracts `apmServerUrl` and `secretToken` from `newPolicy` and passes\nthem to child components\n- Fixed the key prop to use ${agentName}-${variantId} for uniqueness\n\n## How to test\n- I am creating a cloud deployment with this PR and we should be able to\ntest there\n- @jackshirazi Could you please verify if everything still works on the\nagent side with those changes\n\n- [x] Tested on cloud\n\n✅ Tested using the PR cloud deployment: \n- Go to APM -> Fleet -> Agent policies -> Elastic Cloud agent policy ->\nEdit integration (Edit Elastic APM integration)\n- The Java auto-attacher tab is not present ✅ \n\n<img width=\"1913\" height=\"1010\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068\"\n/>\n\n\n- [x] Tested with Java agent (if needed ❓)","sha":"da35df416e9ac9e5c4145828cd69dccc32ebffb4","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","ci:cloud-deploy","v9.4.0","Team:obs-presentation"],"title":"[APM] Remove the java agent auto-attacher from the APM onbarding","number":249043,"url":"https://github.com/elastic/kibana/pull/249043","mergeCommit":{"message":"[APM] Remove the java agent auto-attacher from the APM onbarding (#249043)\n\nCloses #248894\n\n## Summary\nThis PR removes the Java agent auto-attacher from the APM onboarding.\nThe Java agent \"Auto-Attachment\" tab is no longer visible in the Fleet\nAPM integration UI. All related runtime attachment components and code\nhave been removed.\nThe onboarding now only shows manual instrumentation steps for all\nagents.\n\n## Changes: \n- Files Deleted: entire `runtime_attachment/` directory + unused\ntranslations:\n- Changed to use PackagePolicyEditExtensionComponentProps for proper\nFleet integration typing\n- Extracts `apmServerUrl` and `secretToken` from `newPolicy` and passes\nthem to child components\n- Fixed the key prop to use ${agentName}-${variantId} for uniqueness\n\n## How to test\n- I am creating a cloud deployment with this PR and we should be able to\ntest there\n- @jackshirazi Could you please verify if everything still works on the\nagent side with those changes\n\n- [x] Tested on cloud\n\n✅ Tested using the PR cloud deployment: \n- Go to APM -> Fleet -> Agent policies -> Elastic Cloud agent policy ->\nEdit integration (Edit Elastic APM integration)\n- The Java auto-attacher tab is not present ✅ \n\n<img width=\"1913\" height=\"1010\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068\"\n/>\n\n\n- [x] Tested with Java agent (if needed ❓)","sha":"da35df416e9ac9e5c4145828cd69dccc32ebffb4"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/249043","number":249043,"mergeCommit":{"message":"[APM] Remove the java agent auto-attacher from the APM onbarding (#249043)\n\nCloses #248894\n\n## Summary\nThis PR removes the Java agent auto-attacher from the APM onboarding.\nThe Java agent \"Auto-Attachment\" tab is no longer visible in the Fleet\nAPM integration UI. All related runtime attachment components and code\nhave been removed.\nThe onboarding now only shows manual instrumentation steps for all\nagents.\n\n## Changes: \n- Files Deleted: entire `runtime_attachment/` directory + unused\ntranslations:\n- Changed to use PackagePolicyEditExtensionComponentProps for proper\nFleet integration typing\n- Extracts `apmServerUrl` and `secretToken` from `newPolicy` and passes\nthem to child components\n- Fixed the key prop to use ${agentName}-${variantId} for uniqueness\n\n## How to test\n- I am creating a cloud deployment with this PR and we should be able to\ntest there\n- @jackshirazi Could you please verify if everything still works on the\nagent side with those changes\n\n- [x] Tested on cloud\n\n✅ Tested using the PR cloud deployment: \n- Go to APM -> Fleet -> Agent policies -> Elastic Cloud agent policy ->\nEdit integration (Edit Elastic APM integration)\n- The Java auto-attacher tab is not present ✅ \n\n<img width=\"1913\" height=\"1010\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068\"\n/>\n\n\n- [x] Tested with Java agent (if needed ❓)","sha":"da35df416e9ac9e5c4145828cd69dccc32ebffb4"}}]}] BACKPORT--> Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #248894
Summary
This PR removes the Java agent auto-attacher from the APM onboarding. The Java agent "Auto-Attachment" tab is no longer visible in the Fleet APM integration UI. All related runtime attachment components and code have been removed.
The onboarding now only shows manual instrumentation steps for all agents.
Changes:
runtime_attachment/directory + unused translations:apmServerUrlandsecretTokenfromnewPolicyand passes them to child componentsHow to test
I am creating a cloud deployment with this PR and we should be able to test there
@jackshirazi Could you please verify if everything still works on the agent side with those changes
Tested on cloud
✅ Tested using the PR cloud deployment: