-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Palo Alto Workbooks Error / no results showing with correct configs and data logs #8893
Comments
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. |
Hi @johnB007, thanks for flagging this issue, we will soon get back to you on this. Thanks! |
|
@v-sudkharat - I ran the query and it doesn't have threat for activity type but wildfire is active with the license and showing in wildfire GUI. Some data is shown in the workbooks but a majority is not. Not sure why Threat would populate in "some places" in workbook, with some graphics/data but not the rest. If you have an explanation or if the workbook needs updating, it would be most helpful. Thanks. |
Hello @johnB007, we are checking this issue, and we will get back to you. Thanks. |
Further inspection, break / inspect on logs isnt formatted thus no wildfire alerts/logs |
@devikamehra
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Both workbooks show all graphics, data, etc in each section as all products have licenses and confirmed in logs and setup correctly per connectors.
Screenshots
See attacched
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Several other customer environments to include Microsoft demo environment, reproduces the exact same exact behavior and result with no graphics or data in both workbooks.
The text was updated successfully, but these errors were encountered: