Actions
action #69202
closedicinga alert "openqaworker3.suse.de/Number of threads"
Start date:
2020-07-22
Due date:
% Done:
0%
Estimated time:
Description
Observation¶
alert by email:
** PROBLEM Service Alert: openqaworker3.suse.de/Number of threads is WARNING **

From: Monitoring User <nagios@suse.de> resent from: okurz@suse.com
To: okurz@suse.com
Date: 21/07/2020 18.44
Spam Status: Spamassassin 
Notification: PROBLEM
Host: openqaworker3.suse.de
State: WARNING
Date/Time: Tue Jul 21 16:44:39 UTC 2020
Info: WARN - 2111 threads (warning at 2000)
Service: Number of threads
See Online: https://thruk.suse.de/thruk/cgi-bin/extinfo.cgi?type=2&host=openqaworker3.suse.de&service=Number%20of%20threads
Checking logs at the time of alerting I could not find anything obvious in journalctl
output on openqaworker3.
https://nagios-devel.suse.de/pnp4nagios/zoom?host=openqaworker3.suse.de&srv=Number_of_threads&view=0&source=0&end=1595383132&start=1571142185&graph_width=500&graph_height=100 shows that over long time the number of processes / threads is already at the warning threshold of 2000 but I do not remember seeing that as a problem.
Suggestions¶
- Ask SUSE-IT (EngInfra) to disable alert or help debugging
Updated by okurz over 4 years ago
- Status changed from Workable to Blocked
- Assignee set to okurz
Updated by okurz about 4 years ago
- Status changed from Blocked to Resolved
ticket was resolved and alert was put on "ignore" list by SUSE IT
Actions