New entity store features #954
Merged
Conversation
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
nastasha-solomon
approved these changes
Mar 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Contributes to elastic/security-docs#6423 and elastic/security-docs#6422 by documenting the Engine Status tab on the Entity store page and the new 'service' entity type.
The new 'service' entity type also has its own details flyout, which is very similar to the existing user and host details flyouts. Instead of duplicating the content, I moved the existing user and host details flyouts from the Host and Users pages and created a new page, View entity details, which consolidates all the user/host/service flyout content into an "entity details flyout".
Previews (main changes are on the following pages):
Twin 8.x PR: elastic/security-docs#6634