Sentinel Lookback Mechanism#44282
Conversation
🤖 AI-Powered Code Review AvailableYou can leverage AI-powered code review to assist with this PR! Available Commands:
|
Coverage Report
|
||||||||||||||||||||||||||||||
This comment has been minimized.
This comment has been minimized.
|
🤖 Analysis started. Please wait for results... |
🤖 AI Review DisclaimerThis review was generated by an AI-powered tool and may contain inaccuracies. Please be advised, and we extend our sincere apologies for any inconvenience this may cause. |
marketplace-ai-reviewer
left a comment
There was a problem hiding this comment.
Hi! Thanks for your contribution to the Azure Sentinel integration.
I've reviewed the PR and noticed a few architectural risks with the new lookback mechanism, specifically around potential incident drops, state size limits, and incorrect last_fetch_time advancement. There are also some minor YAML formatting tweaks needed, and the documentation should be simplified and updated using demisto-sdk generate-docs.
Let me know if you have any questions or need help adjusting the lookback logic!
Additionally, please address the following file-level notes:
Packs/AzureSentinel/Integrations/AzureSentinel/AzureSentinel.yml: The.ymlfile must start withnameordisplayas the first key at the root level.
@MLainer1, @noydavidi please review and approve the results generated by the AI Reviewer by responding 👍 on this comment.
…ent into sentinel-lookback-mechanism
This PR was automatically updated by a GitHub Action
To stop automatic version bumps, add the |
This comment has been minimized.
This comment has been minimized.
|
Validate summary Verdict: PR can be force merged from validate perspective? ✅ |
🔍 AI Triage Report AvailableAn automated triage report has been generated for this pipeline. Status: 📋 Triage Report
|

Added a lookback mechanism for fetching incidents.
Status
Related Issues
related: link to the issue
Must have