You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These are the errors we have found testing our app before the 3.11 release:
Monitored files table in Integrity Monitoring is getting stuck when the user is monitoring a huge amount of files.
Fixed here: Refactor syscheck table #1941
A wrong command is being used in the agent installation guide for macOS:
The correct command is:
The whodata field is not being shown correctly in the groups generated pdf.
The problem is that this field can have 2 different names: whodata and check_whodata, we have to normalize this field for the group reporting.
Fixed here: 78f9b34
Agents -> Ciscat dashboard is loading indefinitely so there is no way to view that dashboard.
Fixed here: 8945efd
Some visualizations are not loading correctly for AWS or Docker.
The problem is that some of the fields that we are using on these visualizations are not found in the Wazuh template for Elasticsearch. Adding these fields to our known fields method could solve this.
Fixed here: 6058d18
The text was updated successfully, but these errors were encountered:
These are the errors we have found testing our app before the 3.11 release:
Monitored files
table in Integrity Monitoring is getting stuck when the user is monitoring a huge amount of files.Fixed here: Refactor syscheck table #1941
A wrong command is being used in the agent installation guide for macOS:
The correct command is:
Fixed here: #1926
The
whodata
field is not being shown correctly in the groups generated pdf.The problem is that this field can have 2 different names:
whodata
andcheck_whodata
, we have to normalize this field for the group reporting.Fixed here: 78f9b34
Agents -> Ciscat
dashboard is loading indefinitely so there is no way to view that dashboard.Fixed here: 8945efd
Some visualizations are not loading correctly for AWS or Docker.
The problem is that some of the fields that we are using on these visualizations are not found in the Wazuh template for Elasticsearch. Adding these fields to our
known fields
method could solve this.Fixed here: 6058d18
The text was updated successfully, but these errors were encountered: