Githubwebhook

[gokulkate96]

Required items, please complete

Change(s):

• See guidance below

Reason for Change(s):

• See guidance below

Version Updated:

• Required only for Detections/Analytic Rule templates
• See guidance below

Testing Completed:

• See guidance below

Checked that the validations are passing and have addressed any issues that are present:

• See guidance below

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.

Details of the code changes in your submitted PR. Providing descriptions for pull requests ensures there is context to changes being made and greatly enhances the code review process. Providing associated Issues that this resolves also easily connects the reason.

Change(s):

• Updated syntax for XYZ.yaml

Reason for Change(s):

• New schema used for XYZ.yaml
• Resolves ISSUE Add Logstash required version to Readme file #1234

Version updated:

• Yes
• Detections/Analytic Rule templates are required to have the version updated

The code should have been tested in a Microsoft Sentinel environment that does not have any custom parsers, functions or tables, so that you validate no incorrect syntax and execution functions properly. If your submission requires a custom parser or function, it must be submitted with the PR.

Testing Completed:

• Yes/No/Need Help

Note: If updating a detection, you must update the version field.

Before the submission has been made, please look at running the KQL and Yaml Validation Checks locally.
https://github.com/Azure/Azure-Sentinel#run-kql-validation-locally

Checked that the validations are passing and have addressed any issues that are present:

• Yes/No/Need Help

Note: Let us know if you have tried fixing the validation error and need help.

References:

• Guidance for Detection checks
• General contribution guidance
• PR validation troubleshooting

---

[vakohl]

if this upto date?

[gokulkate96]

Yes

[vakohl]

does github webhook provide these 12 event_s or are there more? if more, we should configure all.

[gokulkate96]

Configured 25 with reference to Product document

[v-atulyadav]

Hi @gokulkate96,
Please check above comment and act accordingly. Thanks

[v-atulyadav]

Hi @gokulkate96,
Please act on above comments and also it has validation failures. Thanks

[v-atulyadav]

Hi @gokulkate96,
Please respond. Thanks

[v-atulyadav]

Hi @gokulkate96,
We are waiting for your reply. Thanks

[v-atulyadav]

Hi @gokulkate96,
Please check open comments from @vakohl and act on them. Thanks

[v-atulyadav]

Hi @gokulkate96,
Please check open comments and also failure validations. Thanks

[v-atulyadav]

Hi @gokulkate96,
Please respond on above. Thanks

[v-atulyadav]

Hi @gokulkate96,
We wanted to check on the status of PR #10416. PR is pending for more than 30 days. Please let us know if you need any assistance to review this PR. Per our standard operating procedures if no response is received in the next 7 business days, we will close this PR. Thank you for your cooperation

[v-atulyadav]

Since we have not received a response in the last 7 days, we are closing your PR #10416 per our standard operating procedures. If you still need support for this issue, you can re-open the PR at any time.
If you do re-open, we simply request that you ensure the PR has response to the last request. Thank you for your cooperation.

[v-atulyadav]

Hi @gokulkate96,
Please reply to open comments; PR is having problems with validation. please check. Thanks

[v-atulyadav]

Hi @gokulkate96,
Please act on open comments and also check for failed validations. Thanks

[v-atulyadav]

Hi @gokulkate96,
Please respond on above asks. Thanks

[v-atulyadav]

Hi @gokulkate96,
Please resolve branch conflicts. Thanks

[v-atulyadav]

We wanted to check on the status of PR #10416. PR is pending for more than 60 days. Please let us know if you need any assistance to review this PR. Per our standard operating procedures if no response is received in the next 7 business days, we will close this PR. Thank you for your cooperation

[v-atulyadav]

Since we have not received a response in the last 7 days, we are closing your PR #10416 per our standard operating procedures. If you still need support for this issue, you can re-open the PR at any time.

If you do re-open, we simply request that you ensure the PR has response to the last request. Thank you for your cooperation