You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,7 +88,7 @@ Common use cases:
88
88
State machine-related issues often require several data checks and conditional logic to identify. These issues are typically difficult to capture using standard logs and metrics but can be easily addressed using Sentinela Monitoring.
89
89
90
90
# Dashboard
91
-
Sentinela provides a web dashboard with 2 sections:
91
+
Sentinela provides a web dashboard, by default at port `8000`, with 2 sections:
92
92
1. an overview of the monitors and their alerts and issues
93
93
2. a monitor editor, where you can create and edit monitors directly from the browser
Copy file name to clipboardExpand all lines: docs/configuration_file.md
+10-5Lines changed: 10 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,22 +65,27 @@ application_queue:
65
65
## Time Zone
66
66
- `time_zone`: String. Time zone to use for cron scheduling and notification messages.
67
67
68
+
## Heartbeat
69
+
- `heartbeat_time`: Integer. Time, in seconds, between each heartbeat. This heartbeat is used to identify when a task is not yielding the control back to the event loop for too much time, generating a Warning log.
70
+
68
71
## Controller Settings
69
72
- `controller_process_schedule`: String using Cron format. Schedule to check if monitors need to be processed.
70
73
- `controller_concurrency`: Integer. Number of monitors that can be processed at the same time by the Controller.
71
74
- `controller_procedures`: Map. Procedures to be executed by the Controller and their settings.
72
-
- `controller_procedures.monitors_stuck`: Map. Settings for the procedure to fix monitors stuck in "queued" or "running" status.
73
-
- `controller_procedures.monitors_stuck.schedule`: String using Cron format. Schedule to execute the `monitors_stuck` procedure.
74
-
- `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.
75
-
- `controller_procedures.notifications_alert_solved.schedule`: String using Cron format. Schedule to execute the `notifications_alert_solved` procedure.
75
+
- `monitors_stuck`: Map. Settings for the procedure to fix monitors stuck in "queued" or "running" status.
76
+
- `schedule`: String using Cron format. Schedule to execute the `monitors_stuck` procedure.
77
+
- `params`: Map. Configuration parameters for the `monitors_stuck` procedure.
78
+
- `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.
79
+
- `notifications_alert_solved`: Map. Settings for the procedure to identify and fix active notifications linked to alerts that have already been solved.
80
+
- `schedule`: String using Cron format. Schedule to execute the `notifications_alert_solved` procedure.
76
81
77
82
## Executor Settings
78
83
- `executor_concurrency`: Integer. Number of tasks that can be executed at the same time by each Executor.
79
84
- `executor_sleep`: Integer. Time, in seconds, the Executor will sleep when there are no tasks in the queue before trying again.
80
85
- `executor_monitor_timeout`: Integer. Timeout, in seconds, for monitor execution.
81
86
- `executor_reaction_timeout`: Integer. Timeout, in seconds, for reactions execution.
82
87
- `executor_request_timeout`: Integer. Timeout, in seconds, for requests execution.
83
-
- `executor_monitor_heartbeat_time`: Integer. Time, in seconds, between each monitor heartbeat. This parameter impacts the controller procedure `monitors_stuck.time_tolerance` parameter.
88
+
- `executor_monitor_heartbeat_time`: Integer. Time, in seconds, between each executor heartbeat during monitor execution. This parameter impacts the controller procedure `monitors_stuck.time_tolerance` parameter.
84
89
85
90
## Issues Creation
86
91
- `max_issues_creation`: Integer. Maximum number of issues that can be created by each monitor in a single search. Can be overridden by the monitors' configuration.
Copy file name to clipboardExpand all lines: docs/http_server.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,9 @@
1
1
# HTTP server
2
2
The HTTP server provides an API to interact with Sentinela. The available routes are organized into two main categories, based on the deployment setup.
3
3
4
+
> [!IMPORTANT]
5
+
> By default the API is served at port `8000`. The docker compose files also expose the port `8000`, so if the port for the server changes, the compose files should be updated accordingly. Another option is to keep the server port at `8000` and changing only the compose files. Using the configuration `8080:8000`, for example, will keep the server running at port `8000`, but it will be accessible through the container's port `8080`.
6
+
4
7
If the container is deployed with the **Controller** (either standalone or alongside the Executor in the same container), all routes are available, allowing interactions with Monitors, Issues, Alerts and the dashboard.
5
8
6
9
If the container is deployed with only the **Executor**, only base routes are available.
0 commit comments