-
Notifications
You must be signed in to change notification settings - Fork 186
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
Add agent synchronization statistics #3402
Labels
Comments
dariommr
changed the title
Add agent status percentage
Add agent synchronization percentage
Jun 25, 2021
dariommr
changed the title
Add agent synchronization percentage
Add agent synchronization statistics
Jun 30, 2021
frankeros
added
priority/medium
and removed
pending-PO
Taks pending for PO validation and priorization
labels
Jul 8, 2021
Linked issue #9334 |
Current state |
Depends on wazuh/wazuh#9334 |
Resume workAs wazuh/wazuh#9334 is completed, we can resume or work on this issue. Reviewing the current work done in #3874, the remaining work for this issue to be completed is:
|
11 tasks
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello Team,
Summary
It could be very useful to have agent configuration synchronization statistics in percentage (and it could be in numbers also).
Currently, we have to check agent by agent if they are synchronized.
In large environments, it is more useful having that information in the same visualization.
Suggested changes
More precisely, I am looking for:
Thank you in advance.
Update
Agents config synchronization percentage
We will add a widget below
Agents coverage
in theAgents preview
page. This widget will contain the value of the percentage of agents which has its configuration synchronized with the Wazuh manager over the total active agents.The value represents the synchronization and not the application of such configuration. It might happen that the configuration is synchronized but not applied.
The percentage will always be related to the total amount of active agents at the time of visualization and not a group or a filtered set of agents.
There might be a latency between the time a user sends a new configuration to be applied and the update of the indicator, which will depend on the load of the system and the number of agents. It might, at first, decrease its value as the agents are being recognized as being unsynchronized to later raise as the agents are being synchronized.
The new indicator value won't be available for alerting, indexing or building historical reports.
There won't be a clickable area in the widget to perform additional actions in the view, following the design of the
Agents coverage
widget instead of theActive
widget.The widget will use an API call to the agent's summary API method to obtain its value. Because this call is already made to load the
Agents preview
, no further calls need to be done besides what it is already present.Agent list table
The table in the same
Agents preview
page will have a new field "Configuration state" which will show if the agent has its configuration synchronized or not, similarly to the way it is show in the agent configuration panel.This field must behave like the other fields in the table, and should support the filter and visibility rules which are applicable to the other fields of the table.
The information of the table is obtained from the API call to list agents, which already being made in the
Agents preview
. This call will include a new field indicating if the configuration is synchronized or not.Additional tasks
We will use the issue wazuh/wazuh#9334 to follow up the API implementation.
The text was updated successfully, but these errors were encountered: