Closed jernesto87 closed 2 years ago
Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.
Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.
Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.
Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.
@v-jayakal : note that I believe this related to https://github.com/Azure/Azure-Sentinel/blob/master/Parsers/InfobloxNIOS/InfobloxNIOS.txt
hi, any updates regarding this parser and reported issue?
Hey.. we are looking into this issue and would get back to you asap... Thanks!!!
Hi @jernesto87,
We have made few changes to the parser to help improve the parser performance https://github.com/Azure/Azure-Sentinel/pull/3850/files. Can you please follow below steps and save the function with a different name and update us if you see any improvement in parser performance?
Let us know, if the query works fine. Thanks!!
Good morning, Many thanks for the improvements made. I just wanted to confirm if the previously reported potential errors were also taken into account in this new version:
"There were also some potential errors in the code in the following lines:
[207] "dhcp" should be "dhcpd" [209] "Type" should be "Log_Type" [211] "Type" should be "Log_Type""
Thanks again.
Hi, We have pushed the changes for fixing potential errors mentioned above, in the same PR. Thanks!!
@jernesto87 : Do we have any update on this issue? Has the performance issue resolved for you? Thanks!!!
Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.
@jernesto87 we are closing this issue as we did not hear back from you. Please feel free to open another issue if still face the issue.
Thank you for submitting an Issue to the Azure Sentinel GitHub repo! You should expect an initial response to your Issue from the team within 5 business days. Note that this response may be delayed during holiday periods. For urgent, production-affecting issues please raise a support ticket via the Azure Portal.
There is a performance degradation once the function is defined within a given workspace and data is progressively being ingested. Several errors are shown on the AS Connector page and when it is able to load, it takes at least more than 5 minutes to do so. Also, the associated Workbook is extremely slow when attempting to load data.
There were also some potential errors in the code in the following lines:
Many thanks in advance for the help. Regards.