[8.19] Advanced option for orphaned agent remediation (#236917)#237045
Merged
ashokaditya merged 4 commits intoelastic:8.19from Oct 1, 2025
Merged
[8.19] Advanced option for orphaned agent remediation (#236917)#237045ashokaditya merged 4 commits intoelastic:8.19from
ashokaditya merged 4 commits intoelastic:8.19from
Conversation
## Summary Adds an advanced option to enable or disable orphaned state remediation. When Elastic Endpoint detects orphaned state is may attempt to remediate it by starting Elastic Agent service. ## Release note Adds an advanced option to enable or disable orphaned state remediation. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... (cherry picked from commit 52aaa03) # Conflicts: # x-pack/solutions/security/plugins/security_solution/public/management/pages/policy/models/advanced_policy_schema.ts
10 tasks
ferullo
requested review from
a team,
ashokaditya and
joeypoon
and removed request for
a team
…d have been previously backported
Contributor
Author
|
/ci |
1 similar comment
Member
|
/ci |
Contributor
Author
|
/ci |
Contributor
|
@ferullo that Threat Hunting Investigations Cypress test seems to be failing for other PRs as well. I don't think it's flaky. Someone must have merged a backport to |
Contributor
💚 Build Succeeded
Metrics [docs]Async chunks
History
|
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.
Note:
Something strange happened in the auto backport script. It pulled in #218354 which I removed in commit f78efcb . I do not understand why that other PR was pulled in originally. I suspect it actually ought to be in 8.19 but since this is a backport of #236917 I removed those options.
Backport
This will backport the following commits from
mainto8.19:Questions ?
Please refer to the Backport tool documentation