Fix show call-out warning when there is no data in the vulnerabilities index

[jbiset]

Description

This pull request adds a vulnerability index data check and displays a warning call-out in case the index does not exist or there is no data in it. This applies to both the Dashboard tab and the Inventory tab.
This pull request also fixes the following changes:

• Since the architecture field will not be in the index, it is necessary to remove the architecture field - both tabs vuls
• Since the event field is not going to be in the index, it is necessary:
  • @timestamp is used instead of event.create in the "Accumulation of the most detected vulnerabilities" visualization
  • Delete event.create in inventory
• Capitalize is used on the values in the vulnerability.severity fields.
• In the OS filters of the vulnerabilities dashboard, use the os.full field
• Added WarningError to error handling to recognize vulnerability warnings and adjust the health check accordingly

Issues Resolved

• Show call-out warning when there is no data in the vulnerabilities index #6166

Evidence

Health check warning message when no indices match vulnerability index pattern

Vulnerability detection dashboard when no indices match vulnerability index pattern

Vulnerability detection inventory when no indices match vulnerability index pattern

Health check when the vulnerability index exists

Vulnerability detector dashboard when the vulnerability index exists, but mapping is wrong

Vulnerability detector dashboard when the vulnerability index exists and mapping is correct

Vulnerability detector inventory when the vulnerability index exists and mapping is correct

Test

Before remember to create the mapping of port 9200:9200 in osd1 in the dev.yml

• When raising the environment for the first time. If the vulnerability index does not exist, a Warning should appear in the Health Check. But it should allow you to continue. When going to the vulnerabilities detector (Dashboard and Inventory), Warning should appear because no indices match vulnerability index pattern.
• Create the index (wazuh-states-vulnerabilities) in the manager and insert data (using script of comment). The health-check will correctly create the index pattern and pass the health-check, although the dashboard will not be seen completely, because mapping is wrong.
• Insert the corresponding mapping and see that the healthcheck passes correctly and the dashboard is shown complete (using dev-tools of comment). (Refresh vulnerabilities index-pattern then). The Inventory tab should also appear complete.

Check List

• All tests pass
  • yarn test:jest
• New functionality includes testing.
• New functionality has been documented.
• Update CHANGELOG.md
• Commits are signed per the DCO using --signoff

[Machi3mfl]

Evidence

[lucianogorza]

Evidence

Health check warning message when no indices match vulnerability index pattern

Vulnerability detection dashboard when no indices match vulnerability index pattern

Vulnerability detection inventory when no indices match vulnerability index pattern

Health check when the vulnerability index exists

Vulnerability detector dashboard when the vulnerability index exists, but mapping is wrong

Vulnerability detector dashboard when the vulnerability index exists and mapping is correct

Vulnerability detector inventory when the vulnerability index exists and mapping is correct

[Desvelao]

I reviewed the pull request changes and there is code that is doing other things that are not related to display the callout. Maybe you could mention these changes into the description of the pull request to be aware of these too.

[github-actions]

Wazuh Core plugin code coverage (Jest) test	%	values
Statements	21.47%	( 186 / 866 )
Branches	18.07%	( 79 / 437 )
Functions	14.22%	( 36 / 253 )
Lines	21.7%	( 183 / 843 )

[github-actions]

Wazuh Check Updates plugin code coverage (Jest) test	%	values
Statements	76.68%	( 171 / 223 )
Branches	57.57%	( 57 / 99 )
Functions	61.7%	( 29 / 47 )
Lines	76.68%	( 171 / 223 )

[github-actions]

Main plugin code coverage (Jest) test	%	values
Statements	12.03%	( 4138 / 34377 )
Branches	8.15%	( 1883 / 23089 )
Functions	11.45%	( 934 / 8155 )
Lines	12.21%	( 4027 / 32976 )