-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Users/gaemslie/8504 #9148
Users/gaemslie/8504 #9148
Conversation
….... Only .yaml, .md extensions are allowed under Solution/Parsers folder"
Hi @keyoke, thank you for raising Pull Request with us! You should expect an initial response to your Pull Request from the team within 2 business days. Thanks! |
Hi @keyoke, could you please have a look at below comment. Thanks! |
Hi @keyoke, hope you are doing well, just want to know should we start to review this PR if no, could you please mark it as Draft PR. Thanks! |
@v-sudkharat please review this issue is again resolved on the Microsoft side |
Hi @keyoke, thanks for clarify. V3 Tool Link: - https://github.com/Azure/Azure-Sentinel/blob/master/Tools/Create-Azure-Sentinel-Solution/V3/README.md Thanks! |
hi @v-sudkharat I have done as requested. please review |
Hi @keyoke, thank you for accommodating the suggested changes! We will review the Pull Request and get back to you by - |
@keyoke, Thanks! |
Hi @keyoke, could you please add the I see you added the We are working on review the other content of solution, meanwhile, we don't have the live environment, so, please share the screenshot of all working playbooks and Data Connectors. Thanks! |
Hi @keyoke, please have a look at above comment. Thanks! |
hello @v-sudkharat I have made the required changes screenshots |
Hi @keyoke, thanks for committing the changes. I can see you added the release notes reference in different path - Please refer below screenshot to adding the ReleaseNote reference. - we don't have the live environment, so, please share the screenshot of all working playbooks. Thanks! |
@keyoke, if you don't required, can you please remove the zip which highlighted in Red. |
done |
Hi @keyoke, we are facing some issue, while testing the content. Please update the sample data for below tables: -
Thanks! |
Hi @v-sudkharat, |
Hi @keyoke, we are unable to save the Parser - |
against actual data works fine not sure how you're importing the sample data |
Hello @keyoke, these screenshots are ok. As you may know the Analytic rules is parser dependent, to test those we do need to save the parsers. Due to lack of sample data parsers are showing us below result. Can you please provide updated sample data with us. |
@keyoke, we updated the |
ok that should be done |
Hi @keyoke, I see you removed the below highlighted package. please revert the changes for 2.0.0 instead of deleting it. In CreateUi file the data connector description is common for below highlighted lines. please update it or remove. |
@keyoke , please have a look at this comment -#9148 (comment) |
ok I have added the required sample data |
@keyoke, thanks for providing new the sample data with us, you can keep the old one, which is highlighted below. please have a look at this comment - #9148 (comment) Also, the 3.0.0 zip contains only 2 files - createUiDefinition.json and mainTemplate.json Thanks! |
ok have done this |
@keyoke, thanks. please have a look on below comment - |
ok have reverted |
Hi @keyoke, Thanks for making suggested changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes Looks Good.
Adding the Screenshots of Solution Tested Successfully : -
Analytic Rule Validated and Created Successfully
Workbook Created Successfully -
CreateUi Looks good (logo is visible) -
All Solution content created successfully.
(Note: Data connector Successfully connected, and playbook successfully deployed screenshot is added in PR itself)
Applies connector updates to resolve #8504, to enable paging behaviour changes implemented by Microsoft Team