Azure-Sentinel
Azure-Sentinel copied to clipboard
Azure
<Do Not Merge>First Cut - Committing Changes to Support Yaml extension for Functions…
… in PT
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 #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:
Hi, maintainer of the Sentry Next.js SDK here. Very randomly stumbled onto this issue.
These errors show up in the console because adblockers block requests to Sentry (we told them numerous times that Sentry does not collect anything but w/e). The only way to get rid of these errors is to proxy sentry requests through your own server so that the ad blockers cannot pattern match for our ingest endpoint.
Since you're using the Next.js SDK you have an easy way to do this via the tunnelRoute option. Please note that this can massively increase your server usage depending on how many requests you're sending.
