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

Azure Firewall Workbook - garbage data #374

Closed
nosalan opened this issue Jun 26, 2024 · 4 comments
Closed

Azure Firewall Workbook - garbage data #374

nosalan opened this issue Jun 26, 2024 · 4 comments
Assignees

Comments

@nosalan
Copy link

nosalan commented Jun 26, 2024

Describe the bug
The Network and Rule Hitcount (SUM) and Application Rule Hitcount (SUM) data is pretty useless because the values on the Y axis is changing when time range is changed. Consider the comparison of charts from the last 24 hours vs the last 48 hours.
The last 24 hours:
image

The last 48 hours:
image

Now compare the last 24 hours on both chart, they are inconsistent. One can see that the values on Y axis are increasing when time range is selected.
The chart seems to be aggregating values in some unknown time buckets making the values on the Y axis not understandable. The readings on the Y axis should be consistent for the given time period regardless of the time range selected.

Copy link

Message that will be displayed on users' first issue

@nosalan
Copy link
Author

nosalan commented Jun 26, 2024

The issue is also being triggered by simple browser resize, please see this GIF:

AzureWorkbookIssue

@shabaz-github
Copy link
Collaborator

@gumoden Hey Gustavo, could you please help take a look at this.

@shabaz-github
Copy link
Collaborator

@nosalan This is a built in Metric that is being used in the Firewall workbook, however if you want to define the time buckets, you can choose the Time Granularity parameter as shown in the below image to solve this.
image

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