[Security] Osquery UI refactor and functionality changes#5766
Conversation
🔍 Preview links for changed docs |
✅ Vale Linting ResultsNo issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
|
@natasha-moore-elastic I think there are some small things to be fixed by @tomsonpl, in that case, let's wait if he can fix them on time and if not, I will approve this. As there are few things where the screenshots and the docs should change:
|
|
hey @tomsonpl is this finally going to be able to be changed? If so, a new screenshot should be taken as the one below would be old @natasha-moore-elastic |
|
Hey, it's been addressed already by @szwarckonrad , we should be able to merge this still today. @natasha-moore-elastic could you use the screenshot provided in the PR elastic/kibana#261394 ? Or do we need another one? |
The screenshot from the dev PR should be good, thanks! I'll make the update. |
Co-authored-by: Florent LB <florent.leborgne@elastic.co>
raqueltabuyo
left a comment
There was a problem hiding this comment.
All good!! Thanks for all the changes and sorry for going back and forth

Summary
Resolves #5512 by updating the Osquery docs to reflect the UI refactor and functionality changes.
Generative AI disclosure
Cursor