![]() The two Memory restart commands let you customize when Monit will restart a service and notify you based on their high RAM usage: -mem-restart-mb 900 -mem-restart-cycles 10 Service is using too much Memory restarts This states that if the service consumes more than 800 MB of RAM for 10 cycles then send service High Memory warning. env file: if mem > 800 MB for 10 cycles then exec "/usr/local/bin/gpmonitor SERVICE MEM_HIGH warning" AND repeat every 10 cycles ![]() They set this line in their service-specific. The two high memory usage commands let you customize when Monit sends you warning notifications for a specific service based on their high RAM usage: -mem-high-mb 800 -mem-high-cycles 10 Service is using a lot of Memory Notifications This states that if the services CPU consumption is over 70% for 5 cycles then restart and send restart notification. env file: if cpu > 70% for 5 cycles then exec "/usr/local/bin/gpmonitor SERVICE CPU_RESTART error" The two CPU restart commands let you customize when Monit will restart a service and notify you based on their sustained CPU usage: -cpu-restart-percent 70 -cpu-restart-cycles 5 This states that if the CPU consumption is over 50% for 5 cycles send a service is running hot warning message in the dashboard and slack (if applicable). env file: if cpu > 50% for 5 cycles then exec "/usr/local/bin/gpmonitor SERVICE CPU_HOT warning" AND repeat every 5 cycles The two CPU hot commands let you customize when Monit sends you warning notifications for a specific service based on their sustained CPU usage: -cpu-warning-percent 50 -cpu-warning-cycles 5 Service is using a lot of CPU Notifications
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |