Skip to content

Security machine learning rule documentation improvements #2240

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 30 commits into from
Jul 25, 2025

Conversation

jmcarlock
Copy link
Contributor

@jmcarlock jmcarlock changed the title restructure ad page, add tips for linking between these pages Security machine learning rule documentation improvements Jul 23, 2025
Copy link

github-actions bot commented Jul 23, 2025

@jmcarlock jmcarlock marked this pull request as ready for review July 23, 2025 20:30
@jmcarlock jmcarlock requested a review from a team as a code owner July 23, 2025 20:30
Copy link

@sodhikirti07 sodhikirti07 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left one small suggestion, otherwise, everything lgtm!

Copy link
Member

@susan-shu-c susan-shu-c left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll do a more detailed review tomorrow, but I noticed that the previous is not rendering {ml-cap} properly: I do remember this being that variable that should render to Machine Learning so wonder why it's not rendering now in the preview build 🤔

Screenshot 2025-07-23 at 4 49 57 PM

@bmorelli25
Copy link
Member

bmorelli25 commented Jul 23, 2025

Hi @susan-shu-c 👋. That variable is {{ml-app}} now.

ml-app: "Machine Learning"

edit: hmm, we also have ml-cap

ml-cap: "Machine learning"

edit edit: preview looks fine to me:
https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/2240/solutions/security/advanced-entity-analytics/anomaly-detection

Screenshot 2025-07-23 at 4 21 44 PM

@@ -14,9 +14,16 @@ products:
# Anomaly detection
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, it would make sense to link to it from the Data tables sections on those pages.

Copy link
Contributor

@natasha-moore-elastic natasha-moore-elastic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for making these updates, @jmcarlock!

Copy link
Member

@susan-shu-c susan-shu-c left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, ++ to Kirti's suggestion.

@jmcarlock jmcarlock requested a review from a team as a code owner July 24, 2025 14:05
@jmcarlock
Copy link
Contributor Author

Thanks @bmorelli25 @natasha-moore-elastic @susan-shu-c @sodhikirti07 for the review! I made additions/changes based on the feedback. @natasha-moore-elastic can you take one more look?

@natasha-moore-elastic
Copy link
Contributor

Thanks @bmorelli25 @natasha-moore-elastic @susan-shu-c @sodhikirti07 for the review! I made additions/changes based on the feedback. @natasha-moore-elastic can you take one more look?

@jmcarlock, I pushed some minor tweaks – should be good to merge now! 🚀

@jmcarlock jmcarlock enabled auto-merge (squash) July 25, 2025 13:22
@jmcarlock jmcarlock disabled auto-merge July 25, 2025 13:29
@jmcarlock jmcarlock enabled auto-merge (squash) July 25, 2025 13:45
@jmcarlock jmcarlock merged commit c966b11 into main Jul 25, 2025
8 of 9 checks passed
@jmcarlock jmcarlock deleted the security-ml-rules-improvements branch July 25, 2025 13:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants