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

Failed to load "Find in Access/Firewall Log" in Workbook - AppGw WAF Triage Workbook #350

Closed
foxdrodd opened this issue Feb 7, 2024 · 3 comments
Assignees

Comments

@foxdrodd
Copy link

foxdrodd commented Feb 7, 2024

Describe the bug
If I click on "Find in Access Log" or "Find in Firewall log", I get an error message from the portal, see

Screenshot 2024-02-07 at 15 17 44

Reproduce
Steps to reproduce the behavior:

  1. Select scope of the WAF Policy
  2. Select Triage by Rule - Rules that got triggered
  3. Select Host affected
  4. Select Hosts and urls impacted by selected rule
  5. Go to "Find in Access Log" in the "Requests on selected host and url"
  6. See error

Expected behavior
Opening of the Logs that match the selected host and url, rule combunation

Desktop (please complete the following information if applicable):

  • Mac, Edge 121.0.2277.98 arm64
Copy link

github-actions bot commented Feb 7, 2024

Message that will be displayed on users' first issue

@mskuratowski
Copy link

Unfortunately, I'm having the same problem. Also, I tried to deploy the workbook again and the result is the same.

@shabaz-github shabaz-github self-assigned this Mar 18, 2024
@shabaz-github
Copy link
Collaborator

@anrub @mskuratowski - This issue has now been resolved. Please redeploy the WAF triage workbook from our GitHub repository and you should be able to open the find in logs blades without any issues now. - https://github.com/Azure/Azure-Network-Security/tree/master/Azure%20WAF/Workbook%20-%20AppGw%20WAF%20Triage%20Workbook

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

No branches or pull requests

3 participants