service healthmonitor
Syntax
service healthmonitor <option>
Description
Use this command to:
-
Restart the healthmonitor service
-
Check the logs and status of healthmonitor service.
Options
| log |
Display the healthmonitor service logs. |
| restart |
Restart the healthmonitor service. |
| status |
Check the status of healthmonitor service. |
Required Privilege Level
CLI Administrator
Sample Output
service healthmonitor
log$ service healthmonitor log Oct 24 12:28:04 INFO [kubedeployments.py:HealthCheckKubeDeployments]: 42/42 apps are healthy Oct 24 12:28:04 INFO [healthmonitor.py:root]: 8/8 Health checks were successful Oct 24 12:28:04 INFO [healthmonitor.py:root]: Health Checks Completed. Oct 24 12:28:06 INFO [healthmonitor.py:root]: Monitoring again at 2024-10-24 12:33:06 Oct 24 12:33:06 INFO [healthmonitor.py:root]: Verifying System State Oct 24 12:33:06 INFO [clusterowner.py:ClusterOwner]: Lock has successfully been obtained. Verifying system. Oct 24 12:33:06 INFO [clusterowner.py:ClusterOwner]: System install/upgrade status: COMPLETED. Status updated at: 2024-10-21 07:11:44 Oct 24 12:33:06 INFO [healthmonitor.py:root]: System State Verified Oct 24 12:33:06 INFO [healthmonitor.py:root]: Running Health Checks Oct 24 12:33:06 INFO [systemdstatus.py:HealthCheckSystemd]: health monitor is up and running ............
service healthmonitor
status$ service healthmonitor status
HealthMonitor: active
● healthmonitor.service - Health Monitor
Loaded: loaded (/etc/systemd/system/healthmonitor.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2024-10-21 01:18:33 UTC; 3 days ago
Main PID: 15355 (python3)
Tasks: 1 (limit: 96381)
Memory: 70.3M
CPU: 1h 2min 39.372s
CGroup: /system.slice/healthmonitor.service
└─15355 python3 /opt/healthmonitor/scripts/healthmonitor.py --daemon --interval 300 --alert --silent
Oct 21 01:18:33 tejas-juss systemd[1]: Started Health Monitor.Release Information
Command introduced in Juniper Security Director Release 24.4.1.