Closed TomasTurina closed 2 years ago
Tester | PR commit |
---|---|
@Deblintrake09 | 369876c |
OS | OS version | Deployment | Image/AMI | Notes |
---|---|---|---|---|
Centos | 8 | <LOCAL \| Vagrant |
qactl/centos_8 |
wazuh-manager |
wazuh-agent |
---|---|
.rpm Manager | .rpm agent |
getconfig - global
:green_circle: getconfig - remote
:green_circle: getconfig - internal
:green_circle: getconfig - internal
- invalid section :green_circle: getconfig - internal
- no section :green_circle: getstats
:green_circle: getstats
- no parameters:green_circle: getagentstats
-all agents - last_id = 0 :green_circle: getagentstats
-all agents - no last_id :green_circle: getagentstats
- single agent :green_circle: getagentstats
- multiple agent :green_circle: getconfig - internal
:green_circle: getconfig - wdb
:green_circle: getconfig
:green_circle: getconfig
:green_circle: getstats
:green_circle: getstats
:green_circle: getconfig - global
:green_circle: getconfig - active_response
:green_circle: getconfig - alerts
:green_circle: getconfig - decoders
:green_circle: getconfig - rules
:green_circle: getconfig - command
:green_circle: getconfig - internal
:green_circle: getconfig - labels
:green_circle: getconfig - rule_test
:green_circle: getconfig - invalid section
:green_circle: getconfig - empty parameters
:green_circle: getstats
:green_circle: getagentstats
-all agents - last_id = 0 :green_circle: getagentstats
-all agents - no last_id :green_circle: getagentstats
- single agent :green_circle: getagentstats
- multiple agent :green_circle: 🟢 Everything seems to be working properly
The issue is reopened because we need to complete the testing corresponding to the API part (it was not available before). As it corresponds to the same development, it will be done in this issue.
(1) Automatic EPS limitation tests have reported that the statistics of dropped events do not work correctly. I have tested it locally and it does not seem to work correctly.
This will be discussed with the development team.
Tester | PR commit |
---|---|
@fedepacher | 369876c |
OS | OS version | Deployment | Image/AMI | Notes |
---|---|---|---|---|
Ubuntu | Jammy | AWS|EC2 |
wazuh-manager |
wazuh-agent |
---|---|
.deb Manager | .deb agent |
manager
:green_circle: worker
:green_circle: agent
:green_circle: wazuh-remoted
:green_circle: request/global
:green_circle: request/remote
:green_circle: multiple remote blocks
:green_circle: request/internal
:green_circle: request/invalid
:green_circle: request/empty
:green_circle: wazuh-remoted
:green_circle: request/global
:green_circle: request/remote
:green_circle: multiple remote blocks
:green_circle: request/internal
:green_circle: request/invalid
:green_circle: request/empty
:green_circle: wazuh-remoted
:green_circle: request/global
:green_circle: request/remote
:green_circle: request/internal
:green_circle: wazuh-db
:green_circle: wazuh-db/internal
:green_circle: wazuh-db/wdb
:green_circle: wazuh-db/invalid
:green_circle: wazuh-db/empty
:green_circle: wazuh-db
:green_circle: wazuh-db/internal
:green_circle: wazuh-db/wdb
:green_circle: wazuh-db/invalid
:green_circle: wazuh-db/empty
:green_circle: wazuh-db/internal
:green_circle: wazuh-db/wdb
:green_circle: wazuh-analysisd
:green_circle: analysis/global
:green_circle: analysis/alerts
:green_circle: analysis/command
:green_circle: analysis/decoders
:green_circle: analysis/internal
:green_circle: analysis/rule_test
:green_circle: analysis/invalid
:green_circle: analysis/empty
:green_circle: wazuh-analysisd
:green_circle: analysis/global
:green_circle: analysis/alerts
:green_circle: analysis/command
:green_circle: analysis/decoders
:green_circle: analysis/internal
:green_circle: analysis/rule_test
:green_circle: analysis/invalid
:green_circle: analysis/empty
:green_circle: wazuh-analysisd
:green_circle: analysis/global
:green_circle: analysis/alerts
:green_circle: analysis/command
:green_circle: analysis/decoders
:green_circle: analysis/internal
:green_circle: analysis/rule_test
:green_circle: agent/client
:green_circle: agent/buffer
:green_circle: agent/labels
:green_circle: agent/internal
:green_circle: agentless/agentless
:green_circle: auth/auth
:green_circle: auth/auth
:green_circle: com/active-response
:green_circle: com/logging
:green_circle: com/internal
:green_circle: com/cluster
:green_circle: csyslog/csyslog
:green_circle: integrator/integration
:green_circle: logcollector/localfile
:green_circle: logcollector/socket
:green_circle: logcollector/internal
:green_circle: mail/global
:green_circle: mail/alerts
:green_circle: mail/internal
:green_circle: monitor/global
:green_circle: monitor/internal
:green_circle: syscheck/syscheck
:green_circle: syscheck/rootcheck
:green_circle: syscheck/internal
:green_circle: wmodules/wmodules
:green_circle: agent/client
:green_circle: agent/buffer
:yelow_circle: agent/labels
:green_circle: agent/internal
:green_circle: agentless/agentless
:green_circle: auth/auth
:green_circle: auth/auth
:green_circle: com/active-response
:green_circle: com/logging
:green_circle: com/internal
:green_circle: com/cluster
:green_circle: csyslog/csyslog
:green_circle: integrator/integrator
:green_circle: logcollector/localfile
:green_circle: logcollector/socket
:green_circle: logcollector/internal
:green_circle: mail/global
:green_circle: mail/alerts
:green_circle: mail/internal
:green_circle: monitor/global
:green_circle: monitor/internal
:green_circle: syscheck/syscheck
:green_circle: syscheck/rootcheck
:green_circle: syscheck/internal
:green_circle: wmodules/wmodules
:green_circle: agent/client
:green_circle: agent/buffer
:green_circle: agent/labels
:green_circle: agent/internal
:green_circle: agentless/agentless
:green_circle: auth/auth
:green_circle: auth/auth
:green_circle: com/active-response
:green_circle: com/logging
:green_circle: com/internal
:green_circle: csyslog/csyslog
:green_circle: integrator/integration
:green_circle: logcollector/localfile
:green_circle: logcollector/socket
:green_circle: logcollector/internal
:green_circle: mail/global
:green_circle: mail/alerts
:green_circle: mail/internal
:green_circle: monitor/global
:green_circle: monitor/internal
:green_circle: syscheck/syscheck
:green_circle: syscheck/rootcheck
:green_circle: syscheck/internal
:green_circle: wmodules/wmodules
:green_circle: @jmv74211 I have uploaded this commit https://github.com/wazuh/wazuh/pull/13713/commits/51b4ceef3ae6a24894fdaea2aba37a90e5855e3c to take into account the syslog dropped events in the wazuh-analysisd
state file. Now, you should see that the total dropped events counter increases when the syslog events used in the automatic tests are dropped.
After the fixes that have been applied in https://github.com/wazuh/wazuh/commit/51b4ceef3ae6a24894fdaea2aba37a90e5855e3c, everything seems to work properly.
In addition, the integration tests for EPS limit pass successfully.
========================================= test session starts ==========================================
platform linux -- Python 3.9.7, pytest-6.2.3, py-1.10.0, pluggy-0.13.1
rootdir: /home/vagrant/wazuh-qa-revert-3270-revert-3146-fix-wdb-getconfig/tests/integration, configfile: pytest.ini
plugins: metadata-1.11.0, html-3.1.1, testinfra-5.0.0
collected 15 items
test_analysisd/test_limit_eps/test_basic.py .. [ 13%]
test_analysisd/test_limit_eps/test_configuration.py ........ [ 66%]
test_analysisd/test_limit_eps/test_event_processing.py ..... [100%]
==================================== 15 passed in 379.36s (0:06:19) ====================================
🟢 | Solved |
The development has been approved taking into account the following considerations proposed in the this review:
(1) Automatic EPS limitation tests have reported that the statistics of dropped events do not work correctly. I have tested it locally and it does not seem to work correctly. 🟢
This has been fixed in https://github.com/wazuh/wazuh/commit/51b4ceef3ae6a24894fdaea2aba37a90e5855e3c, and not it works properly.
On the other hand, all the tests performed on the different sockets and API requests seem to work correctly. A tier 0 testing has been performed, being tested each of the requests and responses obtained, but what has not been checked is that the values of each of the statistics are updated correctly. This is something that has been discussed with the development team, and that in part has already been tested during development, plus the tests performed by the cloud team.
During release testing, this development will be testing too so that for code closure it is decided that everything has passed correctly.
Description
In order to validate the changes of the branch https://github.com/wazuh/wazuh/tree/dev-state-counters, some manual testing is required.
As part of https://github.com/wazuh/wazuh/issues/13099, the statistics of the Wazuh manager have been improved.
Now, global statistics in JSON format can be requested using the API for the following daemons:
wazuh-remoted
wazuh-analysisd
wazuh-db
Also, agent's related statistics can be requested for the following daemons:
wazuh-remoted
wazuh-analysisd
Information related to the fields of the JSON can be found here and here.
All requests must point to the following sockets:
wazuh-remoted
->queue/sockets/remote
wazuh-analysisd
->queue/sockets/analysis
wazuh-remoted
->queue/db/wdb
Information related to the fields of the JSON request/response can be found here.
Configuration
No extra configuration is required.
Logs
No logs needed to verify.
Feature validation
Use the new API endpoints to retrieve and validate these counters/configurations.
/var/ossec/queue/db/wdb
/var/ossec/queue/sockets/remote
/var/ossec/queue/sockets/analysis
Also, this python script may be useful: