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

Add agent synchronization statistics #3402

Closed
dariommr opened this issue Jun 25, 2021 · 4 comments · Fixed by #3874
Closed

Add agent synchronization statistics #3402

dariommr opened this issue Jun 25, 2021 · 4 comments · Fixed by #3874
Assignees
Labels

Comments

@dariommr
Copy link
Member

dariommr commented Jun 25, 2021

Wazuh version Component Install type Install method Platform
4.4.0 App / API / Core - - -

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:

  1. To have the percentage of agents that have their configuration synchronized all in one visualization, in the Agents tab.
  2. Add in the agent's list, the status of synchronization of each agent.
  3. Add the ability to filter the agents by synchronization status.

Thank you in advance.

Update

Agents config synchronization percentage

We will add a widget below Agents coverage in the Agents 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 the Active 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.

@dariommr dariommr added the type/enhancement Enhancement issue label Jun 25, 2021
@dariommr dariommr changed the title Add agent status percentage Add agent synchronization percentage Jun 25, 2021
@frankeros frankeros added the pending-PO Taks pending for PO validation and priorization label Jun 25, 2021
@dariommr dariommr changed the title Add agent synchronization percentage Add agent synchronization statistics Jun 30, 2021
@frankeros frankeros added priority/medium and removed pending-PO Taks pending for PO validation and priorization labels Jul 8, 2021
@matiasmoreno876
Copy link
Contributor

matiasmoreno876 commented Jul 19, 2021

Linked issue #9334

@frankeros frankeros added the 4.3 label Sep 6, 2021
@CPAlejandro CPAlejandro self-assigned this Sep 7, 2021
@CPAlejandro
Copy link
Contributor

Current state
Pending core team to avoid this problem or wazuh/wazuh#9413

@AlexRuiz7
Copy link
Member

Depends on wazuh/wazuh#9334

@gdiazlo gdiazlo moved this to Triage in Release 4.4.0 Jun 9, 2022
@snaow snaow moved this from Triage to In Progress in Release 4.4.0 Jun 13, 2022
@gdiazlo gdiazlo moved this from In Progress to Todo in Release 4.4.0 Jun 28, 2022
@AlexRuiz7
Copy link
Member

AlexRuiz7 commented Jul 18, 2022

Resume work

As 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:

@AlexRuiz7 AlexRuiz7 moved this from In Progress to In Review in Release 4.4.0 Jul 20, 2022
@vikman90 vikman90 added this to the Release 4.4.0 milestone Aug 31, 2022
@asteriscos asteriscos moved this from In Review to Done in Release 4.4.0 Sep 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

8 participants