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

Statistics analysis engine dashboard queue usage is misleading #7181

Closed
1 task
asteriscos opened this issue Nov 28, 2024 · 1 comment · Fixed by #7192
Closed
1 task

Statistics analysis engine dashboard queue usage is misleading #7181

asteriscos opened this issue Nov 28, 2024 · 1 comment · Fixed by #7192
Assignees
Labels
level/task Task issue type/enhancement Enhancement issue

Comments

@asteriscos
Copy link
Member

Description

Currently, the analysis engine queue usage visualizations display not only the absolute value of the amount of decoded events, but also shows the queue usage percentages. Using the same visualization to display both values has proven to be misleading, therefore we have to design and propose a better and easier-to-understand way to show the percentages of the events queue usage.

image

Tasks

  • Redesign queue usage statistics visualizations
@guidomodarelli
Copy link
Contributor

guidomodarelli commented Nov 28, 2024

I have looked into the issue and analyzed the problem.
I am unclear about what the term 'syscheck_queue_usage' represents. Does it represent a value between 0 and 1 or a percentage from 0 to 100?

Peek 2024-11-28 16-30

The value of each queue usage is always zero. So, What represents this property?

I've modified the script source to return a more logical value.
Reference:

image

image

I don't understand what *_queue_usage means but I can guess that it refers to those analyses that have not yet been processed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level/task Task issue type/enhancement Enhancement issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants