The naigos core we used is core 3;
Sms Notification by /usr/local/share/check_mk/notifications scripts.
Service checked by check_mk_agent.
Every crit service problem will notify Average 20 people .
杜晓伟-监控
【京东金融-网银在线-产品技术部】
···
This can have more then one reason
-
what core do you use?
-
how is your notification setup build?
-
what type of services do you have (passive/active)
The most problems i saw where if you have many contacts for one problem and you use the classic or flexible notification that the time used for one notification will grow very high and the normal nagios core will wait
until all the notifications are send. This will result in more problem because you get some timeouts and so on.
Best regards
Andreas
杜晓伟duxiaowei@jd.com schrieb am Mi., 1. Juli 2015 um 06:36 Uhr:
Hi Check_mk team :
We used check_mk with 4400 hosts and 59033 services, when more crit problem(200) on check_mk, the checks are so slowly. Service checks:1or2/s
Can you help me with this problem? Very thanks.
杜晓伟-监控
【京东金融-网银在线-产品技术部】
手机：18513959220
邮箱：duxiaowei@jd.com
地址：北京市朝阳区北辰东路7号国家会议中心6层（c11门）
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-enWe’ll meet in Munich for the 2nd Check_MK Conference!
Book your place now and be part of it.
October 18th-20th, 2015
http://mathias-kettner.com/conference