Fixed threshold value from 50 to 0.5 - #14874
Conversation
The threshold was originally 50 but the value of "Deviation" from line 40 returns a value from 0 to 1 not 0 to 100.
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Updates the anomaly detection rule to use a deviation threshold consistent with the query’s deviation scale (0–1) and bumps the rule version accordingly.
Changes:
- Changed the deviation threshold from
50to0.5in the KQL query. - Updated the analytic rule
versionfrom1.0.0to1.0.1.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
Hi ripping-at-the-siem, |
|
v-atulyadav I'm sorry but I don't know what you mean by "repackage the solution". This is my first PR ever. |
|
Hi ripping-at-the-siem, |
|
Hi ripping-at-the-siem, |
|
Hi ripping-at-the-siem, |
|
Hi ripping-at-the-siem, |
|
Hi ripping-at-the-siem, |
The threshold was originally 50 but the value of "Deviation" from line 40 returns a value from 0 to 1 not 0 to 100.
Required items, please complete
Change(s):
Reason for Change(s):
Version Updated:
Testing Completed:
Checked that the validations are passing and have addressed any issues that are present:
Guidance <- remove section before submitting
Before submitting this PR please ensure that you have read the following sections and filled out the changes, reason for change and testing complete sections:
Thank you for your contribution to the Microsoft Sentinel Github repo.
Change(s):
Reason for Change(s):
Version updated:
Testing Completed:
Note: If updating a detection, you must update the version field.
Checked that the validations are passing and have addressed any issues that are present:
Note: Let us know if you have tried fixing the validation error and need help.