Enriching error messages

[juankaromo]

Hi team,

We need to give more information to the user when an error occurs in the app. Right now we report that an error has occurred in a certain module or service, but we don't specify what type of error.

For example, during the health check if there is an error in the API we are simply told that the connection is unreachable, but we are not told why, even though the response to the request gives us the reason. We have to show it.

• Review errors that appear in health check
• Review errors that appear in API settings section
• Review errors that appear in toasts
• Review errors that appear in file validations

Regards,

[Desvelao]

Update

• Services migrated from AngularJS to ReactJS:
  • ErrorHandler
  • CheckDaemonsStatus
• The references to AngularJS errorHandler service are still in the code.
• Let through errors when they are strings in healthcheck and app settings sections.
• Improved some messages.

TODO:

• remove some console.log found. Pending of accept.
• remove references AngularJS errorHandler service in controllers. Pending of accept.
• review error toasts
• review error in file validations

Strange behavior

A strange behavior has been detected when you wanted to upload a cdb list with the same name as an existing one. The catch block in WzRequest.generiqReq service returns a error.message as Request failed with status code 500 instead the original backend response with Wazuh API error: 1905 - File was not updated because it already exists. It seems that the original response coming in error.response.data. More info about this: axios/axios#960. Same behavior has been experimented in sample data request section.

Screenshot with the problem:

After apply the commented fix:

[pablotr9]

Update :

Fixed the error message when there is something wrong in the wazuh.yml:

Fixed the error message when an API connection failed

---