Skip to content
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

fix: updated _get_query_status in the azure monitor driver #745

Merged
merged 5 commits into from
Feb 2, 2024

Conversation

aka0
Copy link
Contributor

@aka0 aka0 commented Dec 21, 2023

Changed flow to handle LogsQueryPartialResult query status first (#714)

Test

  • Large query (500,000 rows) completed without error

- Handles LogsQueryPartialResult query status first
@aka0 aka0 changed the title fix: updated _get_query_status in the azure monitor driver #714 fix: updated _get_query_status in the azure monitor driver Dec 21, 2023
@ianhelle
Copy link
Contributor

Thanks for the fix @aka0 - great catch. I've made some minor changes but should have the same results.

@ianhelle
Copy link
Contributor

I found some errors in the build due to vt_py (VirusTotal) library being updated.
I've piggybacked those fixes on to your PR - apologies for the abuse :-)

@ianhelle ianhelle merged commit a5ddc4b into microsoft:main Feb 2, 2024
9 checks passed
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.

[Bug]: MSSentinel Provider - No errors thrown for partial query errors when using split_query_by parameter
2 participants