See full error toast button exception

[asteriscos]

Wazuh	Elastic	Rev	Security
4.2	7.x	4xxx	Basic, ODFE, Xpack

Browser
Chrome, Firefox, Safari, etc

Description
When an error toast pops up, sometimes the See full error button does nothing and throws an exception in the console.

Steps to reproduce

1. Force an error, like killing wazuh-modulesd process in the manager
   

Expected Result

1. Clicking the See full error button should open a modal with a full description of the error
2. In case there's no additional information, the button should not appear

Actual Result

1. Clicking the button does nothing and throws an exception

Screenshots

[Machi3mfl]

Tested on Kibana 7.10.2 - Opendistro 1.2.0 - Wazuh 4.2.5

This issue doesn't exist on 4.2.5. The error toast doesn't have the button "See full error"

[Machi3mfl]

Research

We found the problem reason. The error occurs when the error toast doesn't receive an error and instead receives only a message.
Because of that, the error toast doesn't have the error context to show it when the user clicks the "See full error" button.

Long Term Solution:

• We must manage the error throws via an error service or something. I will open a new issue to treat this feature.

Short Term Solution:

• Fix all the throw errors on wz-request, ensure all throw error returns a error instance and not a string.

[Machi3mfl]

Solution:

Screen.Recording.2022-04-28.at.16.07.46.mov

[gdiazlo]

Please take a look at this issue: #4104 is this fixed by the PR #4119

[mauceballos]

Test kibana 7.10 OK

[jhaos]

Hi, we are getting the same problem in Wazuh 4.3 in the OVA and in a cloud environment.

Both versions environments: 4.3.0.
Both App revision: 4301-1.

• Ways to replicate the error in cloud environment:

  1. Restarting the service and going to Wazuh > Settings > API Configuration. This will prompt the button but when clicking on it the error in the console triggers.
  2. Restarting the service and going to Wazuh > Modules > Any module. This will prompt the button but when clicking on it the error in the console triggers.
  3. If the configuration file is empty and we click in Save button. This will prompt the button but when clicking on it the error in the console triggers.

• Way to replicate in OVA

  1. Restarting the service and going to Wazuh > Settings > API Configuration. This will prompt the button but when clicking on it the error in the console triggers.

[Machi3mfl]

The initial case detected in this issue was resolved with a hotfix, but we consider that we need to find a better solution to these cases.
So, we opened a new issue to analyze and treat in-depth error management in the app.
New issue: #4145