Host   | Service   | Status   | Last Check   | Duration   | Attempt   | Status Information |
|
|
|
OK |
06-14-2026 14:18:49 |
10d 17h 24m 23s |
1/3 |
Charge CPU 0% (1 moyenne minimale) 0% (5 moyenne minimale) 0% (15 moyenne minimale) |
|
|
OK |
06-14-2026 14:18:24 |
10d 17h 24m 43s |
1/3 |
C: - total: 199,46 Gb - utilisé: 32,53 Gb (16%) - libre 166,93 Gb (84%) |
|
|
OK |
06-14-2026 14:13:43 |
10d 17h 29m 23s |
1/3 |
Memory usage: total:4799,53 MB - used: 1410,30 MB (29%) - free: 3389,23 MB (71%) |
|
|
OK |
06-14-2026 14:16:30 |
10d 17h 26m 33s |
1/3 |
System Uptime - 26 day(s) 11 hour(s) 45 minute(s) |
|
|
OK |
06-14-2026 14:18:24 |
10d 17h 24m 43s |
1/3 |
NSClient++ 0.5.2.35 2018-01-28 |
|
|
CRITICAL |
06-14-2026 14:13:43 |
4d 16h 39m 15s |
1/3 |
Updates: 2 critical, 0 optional |
|
|
|
|
|
OK |
06-14-2026 14:16:09 |
10d 17h 26m 53s |
1/3 |
CHECK_NRPE: Invalid packet version received from server. |
|
|
OK |
06-14-2026 14:16:09 |
10d 17h 26m 53s |
1/3 |
Charge CPU 6% (1 moyenne minimale) 1% (5 moyenne minimale) 1% (15 moyenne minimale) |
|
|
OK |
06-14-2026 14:18:10 |
10d 17h 25m 2s |
1/3 |
C: - total: 175,00 Gb - utilisé: 59,12 Gb (34%) - libre 115,88 Gb (66%) |
|
|
OK |
06-14-2026 14:16:09 |
10d 17h 26m 53s |
1/3 |
Memory usage: total:6591,54 MB - used: 3045,67 MB (46%) - free: 3545,88 MB (54%) |
|
|
OK |
06-14-2026 14:18:10 |
10d 17h 25m 3s |
1/3 |
System Uptime - 26 day(s) 13 hour(s) 47 minute(s) |
|
|
OK |
06-14-2026 14:18:10 |
10d 17h 24m 53s |
1/3 |
NSClient++ 0.4.4.19 2015-12-08 |
|
|
CRITICAL |
06-14-2026 14:19:19 |
2d 1h 43m 39s |
3/3 |
Updates: 2 critical, 0 optional |
|
|
|
|
|
CRITICAL |
06-14-2026 14:14:03 |
11d 20h 39m 3s |
3/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
06-14-2026 14:14:49 |
11d 20h 38m 13s |
3/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
06-14-2026 14:13:00 |
11d 20h 40m 4s |
3/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
06-14-2026 14:19:29 |
11d 20h 33m 33s |
3/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
06-14-2026 14:13:43 |
11d 20h 39m 24s |
3/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
06-14-2026 14:16:23 |
12d 8h 6m 44s |
3/3 |
CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. |
|
|
|
|
|
OK |
06-14-2026 14:15:59 |
10d 17h 27m 3s |
1/3 |
Charge CPU 0% (1 moyenne minimale) 0% (5 moyenne minimale) 1% (15 moyenne minimale) |
|
|
OK |
06-14-2026 14:17:40 |
10d 17h 25m 24s |
1/3 |
C: - total: 149,40 Gb - utilisé: 61,51 Gb (41%) - libre 87,89 Gb (59%) |
|
|
OK |
06-14-2026 14:13:43 |
10d 17h 29m 23s |
1/3 |
Memory usage: total:31407,43 MB - used: 4895,52 MB (16%) - free: 26511,92 MB (84%) |
|
|
OK |
06-14-2026 14:13:39 |
10d 17h 29m 23s |
1/3 |
System Uptime - 24 day(s) 11 hour(s) 11 minute(s) |
|
|
OK |
06-14-2026 14:13:43 |
10d 17h 29m 23s |
1/3 |
NSClient++ 0.5.2.35 2018-01-28 |
|
|
OK |
06-14-2026 14:15:59 |
10d 17h 27m 12s |
1/3 |
scripts/custom/check_windows_updates.ps1 : Le terme ®scripts/custom/check_windows_updates.ps1¯ n'est pas reconnu comme |
|
|
|
|
|
CRITICAL |
06-14-2026 14:17:43 |
0d 19h 55m 13s |
1/3 |
connect to address 192.168.175.224 and port 12489: Aucun chemin d'accès pour atteindre l'hôte cible |
|
|
CRITICAL |
06-14-2026 14:15:49 |
0d 19h 57m 8s |
1/3 |
connect to address 192.168.175.224 and port 12489: Aucun chemin d'accès pour atteindre l'hôte cible |
|
|
CRITICAL |
06-14-2026 14:13:39 |
0d 19h 49m 19s |
1/3 |
connect to address 192.168.175.224 and port 12489: Aucun chemin d'accès pour atteindre l'hôte cible |
|
|
CRITICAL |
06-14-2026 14:15:59 |
0d 19h 56m 59s |
1/3 |
connect to address 192.168.175.224 and port 12489: Aucun chemin d'accès pour atteindre l'hôte cible |
|
|
CRITICAL |
06-14-2026 14:15:44 |
0d 19h 57m 12s |
1/3 |
connect to address 192.168.175.224 and port 12489: Aucun chemin d'accès pour atteindre l'hôte cible |
|
|
CRITICAL |
06-14-2026 14:14:04 |
0d 19h 48m 52s |
1/3 |
(No output on stdout) stderr: connect to address 192.168.175.224 port 5666: No route to host |
|
|
|
|
|
CRITICAL |
06-14-2026 14:13:43 |
22d 12h 33m 4s |
3/3 |
CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. |
|
|
CRITICAL |
06-14-2026 14:13:43 |
22d 12h 33m 4s |
3/3 |
CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. |
|
|
CRITICAL |
06-14-2026 14:18:10 |
22d 12h 35m 5s |
3/3 |
CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. |
|
|
CRITICAL |
06-14-2026 14:15:49 |
22d 12h 37m 34s |
3/3 |
CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. |
|
|
CRITICAL |
06-14-2026 14:19:29 |
22d 12h 33m 44s |
3/3 |
CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. |
|
|
CRITICAL |
06-14-2026 14:17:19 |
22d 12h 36m 4s |
3/3 |
CRITICAL - Le socket n'a pas répondu dans les 10 secondes |
|
|
CRITICAL |
06-14-2026 14:15:50 |
22d 12h 37m 34s |
3/3 |
CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. |
|
|
|
|
|
OK |
06-14-2026 14:15:19 |
10d 2h 17m 53s |
1/3 |
Charge CPU 0% (1 moyenne minimale) 0% (5 moyenne minimale) 0% (15 moyenne minimale) |
|
|
OK |
06-14-2026 14:18:24 |
10d 15h 14m 43s |
1/3 |
C: - total: 125,99 Gb - utilisé: 36,41 Gb (29%) - libre 89,58 Gb (71%) |
|
|
OK |
06-14-2026 14:12:53 |
10d 15h 23m 2s |
1/3 |
Memory usage: total:4350,93 MB - used: 1808,29 MB (42%) - free: 2542,64 MB (58%) |
|
|
OK |
06-14-2026 14:15:40 |
10d 15h 17m 43s |
1/3 |
System Uptime - 0 day(s) 6 hour(s) 14 minute(s) |
|
|
OK |
06-14-2026 14:15:29 |
10d 15h 17m 43s |
1/3 |
NSClient++ 0.4.4.19 2015-12-08 |
|
|
CRITICAL |
06-14-2026 14:12:53 |
0d 2h 0m 3s |
3/3 |
Updates: 1 critical, 0 optional |
|
|
|
|
|
OK |
06-14-2026 14:12:53 |
1d 13h 20m 3s |
1/3 |
Charge CPU 0% (1 moyenne minimale) 0% (5 moyenne minimale) 0% (15 moyenne minimale) |
|
|
OK |
06-14-2026 14:18:49 |
1d 13h 24m 9s |
1/3 |
C: - total: 126,46 Gb - utilisé: 31,65 Gb (25%) - libre 94,81 Gb (75%) |
|
|
OK |
06-14-2026 14:13:50 |
1d 13h 19m 9s |
1/3 |
Memory usage: total:4799,59 MB - used: 1556,86 MB (32%) - free: 3242,73 MB (68%) |
|
|
OK |
06-14-2026 14:15:29 |
1d 13h 27m 28s |
1/3 |
System Uptime - 29 day(s) 20 hour(s) 41 minute(s) |
|
|
OK |
06-14-2026 14:15:19 |
1d 13h 27m 40s |
1/3 |
NSClient++ 0.4.4.19 2015-12-08 |
|
|
CRITICAL |
06-14-2026 14:14:10 |
2d 1h 58m 50s |
3/3 |
Updates: 2 critical, 0 optional |
|
|
|
|
|
CRITICAL |
06-14-2026 14:16:09 |
29d 23h 57m 18s |
3/3 |
(No output on stdout) stderr: connect to address 10.4.0.236 port 5666: Network is unreachable |
|
|
CRITICAL |
06-14-2026 14:17:19 |
29d 23h 55m 58s |
3/3 |
connect to address 10.4.0.236 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:16:30 |
29d 23h 56m 49s |
3/3 |
connect to address 10.4.0.236 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:13:43 |
29d 23h 59m 28s |
3/3 |
connect to address 10.4.0.236 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:19:29 |
30d 0h 4m 0s |
3/3 |
connect to address 10.4.0.236 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:13:43 |
30d 0h 2m 8s |
3/3 |
connect to address 10.4.0.236 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:13:43 |
30d 2h 59m 29s |
3/3 |
(No output on stdout) stderr: connect to address 10.4.0.236 port 5666: Network is unreachable |
|
|
|
|
|
CRITICAL |
06-14-2026 14:13:43 |
30d 0h 2m 59s |
3/3 |
(No output on stdout) stderr: connect to address 10.90.0.1 port 5666: No route to host |
|
|
CRITICAL |
06-14-2026 14:17:19 |
29d 23h 55m 59s |
3/3 |
connect to address 10.90.0.1 and port 12489: Aucun chemin d'accès pour atteindre l'hôte cible |
|
|
CRITICAL |
06-14-2026 14:16:09 |
29d 23h 57m 16s |
3/3 |
connect to address 10.90.0.1 and port 12489: Aucun chemin d'accès pour atteindre l'hôte cible |
|
|
CRITICAL |
06-14-2026 14:15:40 |
29d 23h 58m 0s |
3/3 |
connect to address 10.90.0.1 and port 12489: Aucun chemin d'accès pour atteindre l'hôte cible |
|
|
CRITICAL |
06-14-2026 14:13:43 |
30d 0h 2m 0s |
3/3 |
connect to address 10.90.0.1 and port 12489: Aucun chemin d'accès pour atteindre l'hôte cible |
|
|
CRITICAL |
06-14-2026 14:13:43 |
30d 0h 2m 0s |
3/3 |
connect to address 10.90.0.1 and port 12489: Aucun chemin d'accès pour atteindre l'hôte cible |
|
|
CRITICAL |
06-14-2026 14:13:43 |
30d 3h 2m 36s |
3/3 |
(No output on stdout) stderr: connect to address 10.90.0.1 port 5666: No route to host |
|
|
|
|
|
CRITICAL |
06-14-2026 14:14:59 |
29d 23h 58m 27s |
3/3 |
(No output on stdout) stderr: connect to address 10.4.0.239 port 5666: Network is unreachable |
|
|
CRITICAL |
06-14-2026 14:16:59 |
29d 23h 56m 26s |
3/3 |
connect to address 10.4.0.239 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:16:09 |
29d 23h 57m 17s |
3/3 |
connect to address 10.4.0.239 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:16:09 |
29d 23h 57m 8s |
3/3 |
connect to address 10.4.0.239 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:16:09 |
29d 23h 57m 9s |
3/3 |
connect to address 10.4.0.239 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:16:19 |
29d 23h 57m 16s |
3/3 |
connect to address 10.4.0.239 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:18:10 |
30d 9h 25m 19s |
3/3 |
(No output on stdout) stderr: connect to address 10.4.0.239 port 5666: Network is unreachable |
|
|
|
|
|
CRITICAL |
06-14-2026 14:16:09 |
29d 23h 57m 16s |
3/3 |
(No output on stdout) stderr: connect to address 10.90.0.2 port 5666: No route to host |
|
|
CRITICAL |
06-14-2026 14:17:19 |
29d 23h 55m 59s |
3/3 |
connect to address 10.90.0.2 and port 12489: Aucun chemin d'accès pour atteindre l'hôte cible |
|
|
CRITICAL |
06-14-2026 14:16:09 |
29d 23h 57m 9s |
3/3 |
connect to address 10.90.0.2 and port 12489: Aucun chemin d'accès pour atteindre l'hôte cible |
|
|
CRITICAL |
06-14-2026 14:16:09 |
29d 23h 57m 16s |
3/3 |
connect to address 10.90.0.2 and port 12489: Aucun chemin d'accès pour atteindre l'hôte cible |
|
|
CRITICAL |
06-14-2026 14:15:39 |
29d 23h 57m 49s |
3/3 |
connect to address 10.90.0.2 and port 12489: Aucun chemin d'accès pour atteindre l'hôte cible |
|
|
CRITICAL |
06-14-2026 14:16:09 |
29d 23h 57m 9s |
3/3 |
connect to address 10.90.0.2 and port 12489: Aucun chemin d'accès pour atteindre l'hôte cible |
|
|
CRITICAL |
06-14-2026 14:15:59 |
29d 23h 59m 29s |
3/3 |
(No output on stdout) stderr: connect to address 10.90.0.2 port 5666: No route to host |
|
|
|
|
|
CRITICAL |
06-14-2026 14:18:10 |
30d 11h 55m 26s |
3/3 |
connect to address 10.4.0.244 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:17:29 |
30d 11h 55m 48s |
3/3 |
connect to address 10.4.0.244 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:17:54 |
30d 11h 49m 28s |
3/3 |
connect to address 10.4.0.244 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:19:29 |
30d 11h 53m 49s |
3/3 |
connect to address 10.4.0.244 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:19:49 |
30d 11h 49m 28s |
3/3 |
connect to address 10.4.0.244 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:15:19 |
30d 11h 58m 27s |
3/3 |
(No output on stdout) stderr: connect to address 10.4.0.244 port 5666: Network is unreachable |
|
|
|
|
|
CRITICAL |
06-14-2026 14:18:24 |
30d 11h 55m 6s |
3/3 |
connect to address 10.4.0.226 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:16:59 |
30d 11h 56m 26s |
3/3 |
connect to address 10.4.0.226 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:18:24 |
30d 11h 55m 6s |
3/3 |
connect to address 10.4.0.226 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:18:24 |
30d 11h 55m 6s |
3/3 |
connect to address 10.4.0.226 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:18:24 |
30d 11h 55m 7s |
3/3 |
connect to address 10.4.0.226 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:13:42 |
32d 19h 10m 51s |
3/3 |
(No output on stdout) stderr: connect to address 10.4.0.226 port 5666: Network is unreachable |
|
|
|
|
|
CRITICAL |
06-14-2026 14:17:19 |
30d 11h 55m 58s |
3/3 |
connect to address 10.4.0.231 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:18:24 |
30d 11h 55m 5s |
3/3 |
connect to address 10.4.0.231 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:14:20 |
30d 11h 49m 9s |
3/3 |
connect to address 10.4.0.231 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:18:24 |
30d 11h 55m 7s |
3/3 |
connect to address 10.4.0.231 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:18:24 |
30d 11h 55m 6s |
3/3 |
connect to address 10.4.0.231 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:19:29 |
30d 12h 33m 59s |
3/3 |
(No output on stdout) stderr: connect to address 10.4.0.231 port 5666: Network is unreachable |
|
|
|
|
|
CRITICAL |
06-14-2026 14:19:29 |
30d 11h 53m 58s |
3/3 |
connect to address 10.4.0.235 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:13:43 |
30d 11h 52m 58s |
3/3 |
connect to address 10.4.0.235 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:17:29 |
30d 11h 55m 49s |
3/3 |
connect to address 10.4.0.235 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:13:43 |
30d 11h 52m 58s |
3/3 |
connect to address 10.4.0.235 and port 12489: Le réseau n'est pas accessible |
|
|
CRITICAL |
06-14-2026 14:19:29 |
30d 11h 53m 58s |
3/3 |
connect to address 10.4.0.235 and port 12489: Le réseau n'est pas accessible |
Results 0 - 100 of 267 Matching Services