update docs for internal monitor notification configs

Author: GabrielSalla

docs/configuration_file.md

@@ -8,12 +8,16 @@ This document provides an overview of the configuration parameters available in
 - `load_sample_monitors`: Boolean. Flag to enable the sample monitors.
 - `sample_monitors_path`: String. Path relative to the project root, where the sample monitors are stored.
 - `internal_monitors_path`: String. Path relative to the project root, where the internal monitors are stored.
+- `internal_monitors_notification`: Map. Settings for the notification to be sent by the internal monitors.
+  - `enabled`: Boolean. Flag to enable the internal monitors notification.
+  - `notification_class`: String. Class to be used for the notification. Example: `plugin.my_plugin.notifications.SomeNotificationClass`.
+  - `params`: Map. The desired parameters for the notification. Each notification class will have its own set of parameters. Check the documentation for each notification class to learn more about the available parameters.
 - `monitors_load_schedule`: String using Cron format. Schedule to reload monitors from the database.
 
 ## Logging
 - `logging.mode`: String. Logging mode. Can be "friendly" or "json".
 - `logging.format`: String. Settings for formatting the "friendly" logs.
-- `logging.fields`: Object. Fields to include in the "json" logs and their name from the `logging` module.
+- `logging.fields`: Map. Fields to include in the "json" logs and their name from the `logging` module.
 
 Suggested configuration for `friendly` logs:
 ```yaml
@@ -59,8 +63,8 @@ application_queue:
 ## Controller Settings
 - `controller_process_schedule`: String using Cron format. Schedule to check if monitors need to be processed.
 - `controller_concurrency`: Integer. Number of monitors that can be processed at the same time by the Controller.
-- `controller_procedures`: Object. Procedures to be executed by the Controller and their settings.
-- `controller_procedures.monitors_stuck`: Object. Settings for the procedure to fix monitors stuck in "queued" or "running" status.
+- `controller_procedures`: Map. Procedures to be executed by the Controller and their settings.
+- `controller_procedures.monitors_stuck`: Map. Settings for the procedure to fix monitors stuck in "queued" or "running" status.
 - `controller_procedures.monitors_stuck.schedule`: String using Cron format. Schedule to execute the `monitors_stuck` procedure.
 - `controller_procedures.monitors_stuck.params.time_tolerance`: Integer. Time tolerance in seconds for a monitor to be considered as stuck. This parameter is directly impacted by the `executor_monitor_heartbeat_time` setting and the recommended value is 2 times the heartbeat time.
 

docs/plugins/slack.md

@@ -89,5 +89,15 @@ notification_options = [
 ]
 ```
 
+### Using Slack notification for internal monitors
+To use the Slack notification for internal monitors, the settings for the `internal_monitors_notification` key in the `configs.yaml` file must be configured as follows:
+- `notification_class`: Should be set to `plugin.slack.notifications.SlackNotification`
+- `params`: Should include the desired parameters for the notification.
+    - `channel` and `mention` will be obtained from the environment variables `SLACK_MAIN_CHANNEL` and `SLACK_MAIN_MENTION`, respectively, as specified in [Environment variables](#environment-variables).
+  - `title` and `issues_fields` are specific to each monitor and are already defined in the internal monitors. If configured in the `params` field, they will be ignored.
+  - `min_priority_to_send`, `min_priority_to_mention`, `mention_on_update`, and `issue_show_limit` can be set in the `params` field to customize the notification behavior. If not set, the default values will be used.
+
+The provided settings will be applied to every internal and sample monitors.
+
 ## Services
 The Slack plugin includes a service that connects to the Slack websocket API to receive mentions and button press events. Any event received will queue an action to be processed by Sentinela.