Appearance
Monitoring
Use external monitoring to check the health of your Turbo Server deployment and catch issues early.
What You'll Learn
- How to monitor Turbo Server with Nagios and Datadog
- Which services and checks to track for availability
- Sample alerts for response time, certificates, and disk space
Overview
Monitor Turbo Server services to verify portal availability, certificate validity, Windows service status, and disk capacity. The examples below provide starting points you can adjust to your environment.
Nagios
Use Nagios to monitor HTTP response times and certificate expiration on the Portal.
text
define service {
use local-service
host_name <turbo-server-hostname>
service_description HTTP Response Time
check_command check_http!<turbo-server-hostname>!https://<turbo-server-hostname>!5!10!-S
}
define service {
use local-service
host_name <turbo-server-hostname>
service_description SSL Certificate Expiration Check
check_command check_http_cert!<turbo-server-hostname>!14
}The HTTP response time check raises a warning after 5 seconds and a critical alert after 10 seconds or no response. The certificate check alerts when the certificate expires within 14 days.
Monitor Turbo Server Windows services to ensure they stay online.
text
define service {
use generic-service
host_name <turbo-server-hostname>
service_description Turbo Server Hub/Portal Service
check_command check_nt!SERVICESTATE!-d SHOWALL -l Turbo
}
define service {
use generic-service
host_name <turbo-server-hostname>
service_description Turbo Server Application Service
check_command check_nt!SERVICESTATE!-d SHOWALL -l Turbo.AppServer
}These checks alert when the services are not running.
Monitor free space on the C drive to prevent outages.
text
define service {
use generic-service
host_name <turbo-server-hostname>
service_description Turbo Server Disk Space
check_command WinCheckDriveSize!c!20%!10%
}This check warns when free space drops below 20% and raises a critical alert below 10%.
Datadog
Use Datadog synthetic checks to monitor Portal response time and certificate expiration.
yaml
- name: <turbo-server-hostname>
url: https://<turbo-server-hostname>
seconds_warning: 5
seconds_critical: 10
check_certificate_expiration: true
disable_ssl_validation: false
days_warning: 14This check raises warnings after 5 seconds and critical alerts after 10 seconds or no response, and alerts when the certificate expires within 14 days.
Monitor Turbo Server Windows services from Datadog.
yaml
- services:
- Turbo
- Turbo.AppServerThese checks alert when the services are not running.
Track disk utilization with a Datadog query alert.
json
{
"name": "Disk space is low on {{device.name}} / {{host.name}}",
"type": "query alert",
"query": "avg(last_15m):avg:system.disk.in_use by {host,device} > 0.9",
"message": "message @[email protected]",
"options": {
"include_tags": true,
"thresholds": {
"critical": 0.9,
"warning": 0.8
},
"require_full_window": true,
"notify_no_data": false,
"renotify_interval": 0,
"escalation_message": "",
"no_data_timeframe": null,
"new_group_delay": 300,
"silenced": {}
},
"priority": null,
"restricted_roles": null
}This alert triggers warnings when free space drops below 20% and critical alerts below 10%. Import the configuration through the Datadog UI.
