Create channels for Slack, PagerDuty, Jira, and Shuffle integrations

[gonzaarancibia]

Description

When a user logs into the Wazuh dashboard, we add preconfigured integration channels for Slack, PagerDuty, Jira, and Shuffle on the Notifications plugin. This makes it easier for the user to configure them.

Issues Resolved

#7814

Evidence

Logs from dashboard server when creating default channels

Default channels created

Testing PagerDuty test sending message

Jira test sending message

Shuffle test sending message

Slack test sending message

Running test

Important

Before starting to run the tests, you should apply this patch to resolve permission issues.
See this comment: #7814 (comment)

Test

🟢 Test Legend

Symbol	Meaning
⚫	The test hasn't started yet.
🟢	All checks passed.
🟡	There is at least one expected fail or skipped test and no failures.
🔴	There is at least one failed check.
⚪	Doesn't apply.
🔧	Request changes.
❓	Needs more information.

UI

Test	Chrome	Firefox	Safari
Verify that default channels are created successfully on dashboard initialization (check dashboard server logs).	⚫	⚫	⚫
Verify that all default channels render correctly in the Notification → Channels section.	⚫	⚫	⚫
Test Jira channel by going to Alerting → Monitors → Custom Monitor → Action and sending an event following the example shown in the channel description.	⚫	⚫	⚫
Test PagerDuty channel by going to Alerting → Monitors → Custom Monitor → Action and sending an event following the example shown in the channel description.	⚫	⚫	⚫
Test the rest of the channels directly using the “Send Test Message” button in the Channels section.	⚫	⚫	⚫
Run the tests by attaching a console to the container and running: npm run test:jest notification-default-channels/	⚫	⚫	⚫

⚫ Verify that default channels are created successfully on dashboard initialization (check dashboard server logs).

* Open the Wazuh Dashboard and restart the server. * Check the dashboard server logs and confirm that default channels are created without errors. * Verify the log entries contain proper information for each created channel. Chrome - ⚫
Firefox - ⚫
Safari - ⚫

⚫ Verify that all default channels render correctly in the Notification → Channels section.

* Go to Notification → Channels. * Check that all default channels (e.g., Slack, Jira, PagerDuty, Shuffle, Email, etc.) are displayed correctly. * Verify name, description, and configuration type are rendered as expected. Chrome - ⚫
Firefox - ⚫
Safari - ⚫

⚫ Test Jira channel by going to Alerting → Monitors → Custom Monitor → Action and sending an event following the example shown in the channel description.

* Create a custom monitor and add an action for the Jira channel. * Use the payload example from the channel description. * Confirm that the event is successfully received in Jira and check for any errors in logs. Chrome - ⚫
Firefox - ⚫
Safari - ⚫

⚫ Test PagerDuty channel by going to Alerting → Monitors → Custom Monitor → Action and sending an event following the example shown in the channel description.

* Create a custom monitor and add an action for the PagerDuty channel. * Use the provided example payload from the channel description. * Confirm that PagerDuty receives the event successfully. Chrome - ⚫
Firefox - ⚫
Safari - ⚫

⚫ Test the rest of the channels directly using the “Send Test Message” button in the Channels section.

* Go to Notification → Channels. * Use the “Send Test Message” button for channels like Slack, Email, and Shuffle. * Confirm that each test message is successfully delivered and reflected in the logs. Chrome - ⚫
Firefox - ⚫
Safari - ⚫

⚫ Run the tests by running: yarn test:jest:runner notification-default-channels/ (Before apply the patch)

diff --git a/plugins/main/package.json b/plugins/main/package.json
index 1e0567a2e..bcfc978bb 100644
--- a/plugins/main/package.json
+++ b/plugins/main/package.json
@@ -3,7 +3,7 @@
   "version": "5.0.0",
   "revision": "00",
   "pluginPlatform": {
-    "version": "3.2.0"
+    "version": "3.1.0"
   },
   "description": "Wazuh dashboard",
   "keywords": [

⚫

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

[guidomodarelli]

Test

🟢 Test Legend

Symbol	Meaning
⚫	The test hasn't started yet.
🟢	All checks passed.
🟡	There is at least one expected fail or skipped test and no failures.
🔴	There is at least one failed check.
⚪	Doesn't apply.
🔧	Request changes.
❓	Needs more information.

UI

Test	Chrome
Verify that default channels are created successfully on dashboard initialization (check dashboard server logs).	🟢
Verify that all default channels render correctly in the Notification → Channels section.	🟢
Test Jira channel by going to Alerting → Monitors → Custom Monitor → Action and sending an event following the example shown in the channel description.	🟢
Test PagerDuty channel by going to Alerting → Monitors → Custom Monitor → Action and sending an event following the example shown in the channel description.	🟢
Test the rest of the channels directly using the “Send Test Message” button in the Channels section.	🟢
Run the tests by attaching a console to the container and running: npm run test:jest notification-default-channels/	🟢

---

🟢 Verify that default channels are created successfully on dashboard initialization (check dashboard server logs).

• Open the Wazuh Dashboard and restart the server.
• Check the dashboard server logs and confirm that default channels are created without errors.
• Verify the log entries contain proper information for each created channel.

---

🟢 Verify that all default channels render correctly in the Notification → Channels section.

• Go to Notification → Channels.
• Check that all default channels (e.g., Slack, Jira, PagerDuty, Shuffle, Email, etc.) are displayed correctly.
• Verify name, description, and configuration type are rendered as expected.

---

🟢 Test Jira channel by going to Alerting → Monitors → Custom Monitor → Action and sending an event following the example shown in the channel description.

• Create a custom monitor and add an action for the Jira channel.
• Use the payload example from the channel description.
• Confirm that the event is successfully received in Jira and check for any errors in logs.

---

🟢 Test PagerDuty channel by going to Alerting → Monitors → Custom Monitor → Action and sending an event following the example shown in the channel description.

• Create a custom monitor and add an action for the PagerDuty channel.
• Use the provided example payload from the channel description.
• Confirm that PagerDuty receives the event successfully.

---

🟢 Test the rest of the channels directly using the “Send Test Message” button in the Channels section.

• Go to Notification → Channels.
• Use the “Send Test Message” button for channels like Slack, Email, and Shuffle.
• Confirm that each test message is successfully delivered and reflected in the logs.

Slack 🟢

Shuffler 🟢

---

🟢 Run the tests by attaching a console to the container and running: `npm run test:jest notification-default-channels/`

• See example of evidence

[github-actions]

Wazuh Core plugin code coverage (Jest) test	%	values
Statements	46.12%	( 381 / 826 )
Branches	44.01%	( 169 / 384 )
Functions	40.44%	( 110 / 272 )
Lines	46.26%	( 378 / 817 )

[github-actions]

Wazuh Check Updates plugin code coverage (Jest) test	%	values
Statements	78.72%	( 185 / 235 )
Branches	62.72%	( 69 / 110 )
Functions	61.7%	( 29 / 47 )
Lines	78.72%	( 185 / 235 )

[guidomodarelli]

LGTM! 🟢

[github-actions]

Main plugin code coverage (Jest) test	%	values
Statements	19.33%	( 5730 / 29643 )
Branches	13.68%	( 2510 / 18337 )
Functions	20.03%	( 1462 / 7297 )
Lines	19.56%	( 5579 / 28517 )