[Entity Analytics][Privileged Monitoring]Fix index update failing due to invalid API payload#250758
Merged
CAWilson94 merged 3 commits intoelastic:mainfrom Jan 29, 2026
Merged
Conversation
CAWilson94
added
Team:Entity Analytics
Contributor
|
Pinging @elastic/security-entity-analytics (Team:Entity Analytics) |
hop-dev
approved these changes
Jan 29, 2026
Contributor
hop-dev
left a comment
hop-dev
left a comment
There was a problem hiding this comment.
Sorry this is definitely my bad, I added the extra API validation
Contributor
|
Starting backport for target branches: 9.3 https://github.com/elastic/kibana/actions/runs/21477780397 |
Contributor
Author
@hop-dev Nothing to apologise for - easy to miss and no one spotted in the PR either. Ty for approval ^^ |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jan 29, 2026
… to invalid API payload (elastic#250758) **Copilot:** This pull request makes a minor update to the API call in the `useEntityAnalyticsRoutes` hook. The change removes the unnecessary `type: 'index'` property from the request body, simplifying the payload. ### Summary This fixes a bug causing an issue where, after creating the initial index in the management page, no new indices could be selected, as the update payload no longer supports the type field. **Desk Testing Steps:** 1. Load up kibana 2. Add a couple of indicies from the manage sources page of privmon 3. Add a user or two to both indicies 4. Add one index to manage sources - index, update privileged users. 5. Try to delete that index from the options, and add the second instead. OR add the second index and try to update privileged users. 6. Should see - both / either indicies are available on update. **Desk Test Demo:** https://github.com/user-attachments/assets/1c4f5e87-9b03-4b75-92ca-450c5f5cfca3 (cherry picked from commit 412a84d)
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
hannahbrooks
pushed a commit
to hannahbrooks/kibana
that referenced
this pull request
Jan 30, 2026
… to invalid API payload (elastic#250758) **Copilot:** This pull request makes a minor update to the API call in the `useEntityAnalyticsRoutes` hook. The change removes the unnecessary `type: 'index'` property from the request body, simplifying the payload. ### Summary This fixes a bug causing an issue where, after creating the initial index in the management page, no new indices could be selected, as the update payload no longer supports the type field. **Desk Testing Steps:** 1. Load up kibana 2. Add a couple of indicies from the manage sources page of privmon 3. Add a user or two to both indicies 4. Add one index to manage sources - index, update privileged users. 5. Try to delete that index from the options, and add the second instead. OR add the second index and try to update privileged users. 6. Should see - both / either indicies are available on update. **Desk Test Demo:** https://github.com/user-attachments/assets/1c4f5e87-9b03-4b75-92ca-450c5f5cfca3
kibanamachine
added
the
backport missing
Contributor
|
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
3 similar comments
Contributor
|
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
Contributor
|
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
Contributor
|
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
kibanamachine
added a commit
that referenced
this pull request
Feb 5, 2026
…ng due to invalid API payload (#250758) (#250885) # Backport This will backport the following commits from `main` to `9.3`: - [[Entity Analytics][Privileged Monitoring]Fix index update failing due to invalid API payload (#250758)](#250758) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Charlotte Alexandra Wilson","email":"CAWilson94@users.noreply.github.com"},"sourceCommit":{"committedDate":"2026-01-29T12:16:02Z","message":"[Entity Analytics][Privileged Monitoring]Fix index update failing due to invalid API payload (#250758)\n\n**Copilot:** This pull request makes a minor update to the API call in\nthe `useEntityAnalyticsRoutes` hook. The change removes the unnecessary\n`type: 'index'` property from the request body, simplifying the payload.\n\n### Summary\nThis fixes a bug causing an issue where, after creating the initial\nindex in the management page, no new indices could be selected, as the\nupdate payload no longer supports the type field.\n\n**Desk Testing Steps:**\n\n1. Load up kibana\n2. Add a couple of indicies from the manage sources page of privmon\n3. Add a user or two to both indicies\n4. Add one index to manage sources - index, update privileged users.\n5. Try to delete that index from the options, and add the second\ninstead. OR add the second index and try to update privileged users.\n6. Should see - both / either indicies are available on update. \n\n**Desk Test Demo:** \n\n\nhttps://github.com/user-attachments/assets/1c4f5e87-9b03-4b75-92ca-450c5f5cfca3","sha":"412a84d1770299490a22e551272bac27dac2d635","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Entity Analytics","backport:version","v9.3.0","v9.4.0"],"title":"[Entity Analytics][Privileged Monitoring]Fix index update failing due to invalid API payload","number":250758,"url":"https://github.com/elastic/kibana/pull/250758","mergeCommit":{"message":"[Entity Analytics][Privileged Monitoring]Fix index update failing due to invalid API payload (#250758)\n\n**Copilot:** This pull request makes a minor update to the API call in\nthe `useEntityAnalyticsRoutes` hook. The change removes the unnecessary\n`type: 'index'` property from the request body, simplifying the payload.\n\n### Summary\nThis fixes a bug causing an issue where, after creating the initial\nindex in the management page, no new indices could be selected, as the\nupdate payload no longer supports the type field.\n\n**Desk Testing Steps:**\n\n1. Load up kibana\n2. Add a couple of indicies from the manage sources page of privmon\n3. Add a user or two to both indicies\n4. Add one index to manage sources - index, update privileged users.\n5. Try to delete that index from the options, and add the second\ninstead. OR add the second index and try to update privileged users.\n6. Should see - both / either indicies are available on update. \n\n**Desk Test Demo:** \n\n\nhttps://github.com/user-attachments/assets/1c4f5e87-9b03-4b75-92ca-450c5f5cfca3","sha":"412a84d1770299490a22e551272bac27dac2d635"}},"sourceBranch":"main","suggestedTargetBranches":["9.3"],"targetPullRequestStates":[{"branch":"9.3","label":"v9.3.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/250758","number":250758,"mergeCommit":{"message":"[Entity Analytics][Privileged Monitoring]Fix index update failing due to invalid API payload (#250758)\n\n**Copilot:** This pull request makes a minor update to the API call in\nthe `useEntityAnalyticsRoutes` hook. The change removes the unnecessary\n`type: 'index'` property from the request body, simplifying the payload.\n\n### Summary\nThis fixes a bug causing an issue where, after creating the initial\nindex in the management page, no new indices could be selected, as the\nupdate payload no longer supports the type field.\n\n**Desk Testing Steps:**\n\n1. Load up kibana\n2. Add a couple of indicies from the manage sources page of privmon\n3. Add a user or two to both indicies\n4. Add one index to manage sources - index, update privileged users.\n5. Try to delete that index from the options, and add the second\ninstead. OR add the second index and try to update privileged users.\n6. Should see - both / either indicies are available on update. \n\n**Desk Test Demo:** \n\n\nhttps://github.com/user-attachments/assets/1c4f5e87-9b03-4b75-92ca-450c5f5cfca3","sha":"412a84d1770299490a22e551272bac27dac2d635"}}]}] BACKPORT--> Co-authored-by: Charlotte Alexandra Wilson <CAWilson94@users.noreply.github.com>
kibanamachine
removed
the
backport missing
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
4 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.
Copilot: This pull request makes a minor update to the API call in the
useEntityAnalyticsRouteshook. The change removes the unnecessarytype: 'index'property from the request body, simplifying the payload.Summary
This fixes a bug causing an issue where, after creating the initial index in the management page, no new indices could be selected, as the update payload no longer supports the type field.
Desk Testing Steps:
Desk Test Demo:
Screen.Recording.2026-01-28.at.16.18.05.mov