Jeannette Agents

🧠

06:15:08VPS Monitorai_call

Diagnostic IA: ## 🚨 Analyse des containers arrêtés **Problème détecté :** - 2/17 containers Supabase arrêtés : `supabase-analytics` et `supabase-vector` - 15/17 containers opérationnels (88% uptime) ## 🔧 Actions...

$0.0061

⚡

06:15:00VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

06:15:00VPS Monitoraction

Action restart_container: Container supabase-analytics redémarré

✓

06:15:00VPS Monitorcheck

[error] containers: 2 container(s) arrêté(s) : supabase-analytics, supabase-vector | [ok] cpu: CPU 34% (load 1.36, 4 cores) | [ok] ram: RAM 26% (4.4/16.8 GB) | [ok] disk: Disque 25% (48G/197G, 142G dispo) | [ok] pm2: PM2 OK (9/9 online) | [ok] services: Services OK (Supabase:5ms, Dashboard:7ms, Agents:49ms)

🧠

06:10:06VPS Monitorai_call

Diagnostic IA: ## 🔍 Analyse des containers arrêtés **Problème :** 2 containers Supabase critiques sont arrêtés - `supabase-analytics` : Service d'analyse des données - `supabase-vector` : Service de recherche vect...

$0.0057

⚡

06:10:00VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

06:10:00VPS Monitoraction

Action restart_container: Container supabase-analytics redémarré

✓

06:10:00VPS Monitorcheck

[error] containers: 2 container(s) arrêté(s) : supabase-analytics, supabase-vector | [ok] cpu: CPU 43% (load 1.72, 4 cores) | [ok] ram: RAM 26% (4.4/16.8 GB) | [ok] disk: Disque 26% (48G/197G, 142G dispo) | [ok] pm2: PM2 OK (9/9 online) | [ok] services: Services OK (Supabase:4ms, Dashboard:8ms, Agents:42ms)

✓

06:05:00VPS Monitorcheck

[ok] containers: Tous les containers actifs (17/17) | [ok] cpu: CPU 36% (load 1.42, 4 cores) | [ok] ram: RAM 30% (5.0/16.8 GB) | [ok] disk: Disque 26% (48G/197G, 142G dispo) | [ok] pm2: PM2 OK (9/9 online) | [ok] services: Services OK (Supabase:2ms, Dashboard:7ms, Agents:44ms)

🧠

06:00:07VPS Monitorai_call

Diagnostic IA: ## 🚨 Analyse de l'alerte VPS Monitor **Problème identifié :** - Container `supabase-vector` arrêté (1/17 containers down) ## 🔍 Actions correctives recommandées ### 1. Redémarrage immédiat ```bash...

$0.0057

⚡

06:00:00VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

06:00:00VPS Monitoraction

Action restart_container: Container supabase-vector redémarré

✓

06:00:00VPS Monitorcheck

[error] containers: 1 container(s) arrêté(s) : supabase-vector | [ok] cpu: CPU 7% (load 0.28, 4 cores) | [ok] ram: RAM 27% (4.6/16.8 GB) | [ok] disk: Disque 26% (48G/197G, 142G dispo) | [ok] pm2: PM2 OK (9/9 online) | [ok] services: Services OK (Supabase:4ms, Dashboard:11ms, Agents:55ms)

🧠

05:55:07VPS Monitorai_call

Diagnostic IA: ## 🔴 Analyse des containers arrêtés **Problème identifié :** - 2 containers Supabase critiques arrêtés sur 17 total - `supabase-analytics` : Service d'analyse des données - `supabase-vector` : Servi...

$0.0061

⚡

05:55:00VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:55:00VPS Monitoraction

Action restart_container: Container supabase-analytics redémarré

✓

05:55:00VPS Monitorcheck

[error] containers: 2 container(s) arrêté(s) : supabase-analytics, supabase-vector | [ok] cpu: CPU 12% (load 0.48, 4 cores) | [ok] ram: RAM 23% (3.9/16.8 GB) | [ok] disk: Disque 26% (48G/197G, 141G dispo) | [ok] pm2: PM2 OK (9/9 online) | [ok] services: Services OK (Supabase:2ms, Dashboard:5ms, Agents:34ms)

🧠

05:50:08VPS Monitorai_call

Diagnostic IA: ## 🔍 Analyse des containers arrêtés **Problème identifié :** 2 containers Supabase critiques sont arrêtés - `supabase-analytics` - Service d'analytique Supabase - `supabase-vector` - Service de rech...

$0.0062

⚡

05:50:00VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:50:00VPS Monitoraction

Action restart_container: Container supabase-analytics redémarré

✓

05:50:00VPS Monitorcheck

[error] containers: 2 container(s) arrêté(s) : supabase-analytics, supabase-vector | [ok] cpu: CPU 66% (load 2.65, 4 cores) | [ok] ram: RAM 21% (3.6/16.8 GB) | [ok] disk: Disque 26% (48G/197G, 141G dispo) | [ok] pm2: PM2 OK (9/9 online) | [ok] services: Services OK (Supabase:6ms, Dashboard:10ms, Agents:43ms)

🧠

05:45:32VPS Monitorai_call

Diagnostic IA: ## 🚨 Analyse des alertes VPS Monitor ### Problèmes détectés : **1. Container Check Failed (ETIMEDOUT)** - Le monitoring des containers échoue par timeout - Probable surcharge système empêchant l'ex...

$0.0061

⚡

05:45:24VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:45:24VPS Monitoraction

Action restart_container: No container to restart

⚡

05:45:23VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:45:23VPS Monitoraction

Action restart_container: No container to restart

✓

05:45:21VPS Monitorcheck

[error] containers: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] cpu: CPU 440% (load 17.60, 4 cores) | [ok] ram: RAM 21% (3.6/16.8 GB) | [ok] disk: Disque 26% (48G/197G, 141G dispo) | [ok] pm2: PM2 OK (9/9 online) | [ok] services: Services OK (Supabase:502ms, Dashboard:1097ms, Agents:1203ms)

🧠

05:40:43VPS Monitorai_call

Diagnostic IA: ## 🚨 **ALERTE CRITIQUE VPS** ### **Diagnostic** - **Surcharge CPU massive** : 424% sur 4 cores (load 16.96) - **Timeouts système** : Impossible d'exécuter les commandes de monitoring - **État critiq...

$0.0065

⚡

05:40:33VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:40:33VPS Monitoraction

Action restart_container: No container to restart

⚡

05:40:32VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:40:31VPS Monitoraction

Action restart_container: No container to restart

⚡

05:40:30VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:40:29VPS Monitoraction

Action restart_container: No container to restart

✓

05:40:28VPS Monitorcheck

[error] containers: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] cpu: CPU 424% (load 16.96, 4 cores) | [ok] ram: RAM 22% (3.7/16.8 GB) | [ok] disk: Disque 26% (48G/197G, 141G dispo) | [error] pm2: Check failed: spawnSync /bin/sh ETIMEDOUT | [ok] services: Services OK (Supabase:903ms, Dashboard:1199ms, Agents:3198ms)

🧠

05:35:54VPS Monitorai_call

Diagnostic IA: ## 🚨 Analyse des alertes VPS Monitor ### **Problème principal : Surcharge CPU critique** - **CPU à 891%** (load 35.65 sur 4 cores) = système complètement surchargé - Timeouts en cascade sur les véri...

$0.0066

⚡

05:35:42VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:35:41VPS Monitoraction

Action restart_container: No container to restart

⚡

05:35:41VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:35:40VPS Monitoraction

Action restart_container: No container to restart

⚡

05:35:38VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:35:37VPS Monitoraction

Action restart_container: No container to restart

⚡

05:35:36VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:35:34VPS Monitoraction

Action restart_container: No container to restart

✓

05:35:29VPS Monitorcheck

[error] containers: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] cpu: CPU 891% (load 35.65, 4 cores) | [ok] ram: RAM 24% (4.0/16.8 GB) | [ok] disk: Disque 26% (48G/197G, 141G dispo) | [error] pm2: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] services: 1 service(s) down : Agents

🧠

05:30:59VPS Monitorai_call

Diagnostic IA: ## 🚨 Analyse Critique - Surcharge CPU Majeure ### **Problème principal :** **CPU à 1042% (charge 41.67 sur 4 cœurs)** - Le système est totalement saturé. ### **Actions correctives immédiates :** #...

$0.0069

⚡

05:30:46VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:30:45VPS Monitoraction

Action restart_container: No container to restart

⚡

05:30:43VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:30:42VPS Monitoraction

Action restart_container: No container to restart

⚡

05:30:41VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:30:41VPS Monitoraction

Action restart_container: No container to restart

⚡

05:30:39VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:30:39VPS Monitoraction

Action restart_container: No container to restart

✓

05:30:32VPS Monitorcheck

[error] containers: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] cpu: CPU 1042% (load 41.67, 4 cores) | [ok] ram: RAM 22% (3.8/16.8 GB) | [ok] disk: Disque 26% (48G/197G, 141G dispo) | [error] pm2: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] services: 1 service(s) down : Agents

⚡

05:16:33VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:16:31VPS Monitoraction

Action restart_container: No container to restart

⚡

05:16:21VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:16:20VPS Monitoraction

Action restart_container: No container to restart

⚡

05:16:10VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:16:09VPS Monitoraction

Action restart_container: No container to restart

⚡

05:16:02VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:16:01VPS Monitoraction

Action restart_container: No container to restart

✓

05:15:36VPS Monitorcheck

[error] containers: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] cpu: CPU 1328% (load 53.13, 4 cores) | [ok] ram: RAM 74% (12.3/16.8 GB) | [ok] disk: Disque 28% (52G/197G, 138G dispo) | [error] pm2: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] services: 1 service(s) down : Agents

🧠

05:11:19VPS Monitorai_call

Diagnostic IA: ## 🚨 **ALERTE CRITIQUE - SURCHARGE SYSTÈME** ### **Analyse rapide** Le VPS est en **surcharge extrême** (CPU 1259% !), causant des timeouts généralisés sur tous les services. ### **Actions correcti...

$0.0067

⚡

05:11:05VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:11:04VPS Monitoraction

Action restart_container: No container to restart

⚡

05:11:01VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:11:00VPS Monitoraction

Action restart_container: No container to restart

⚡

05:10:58VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:10:58VPS Monitoraction

Action restart_container: No container to restart

⚡

05:10:55VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:10:54VPS Monitoraction

Action restart_container: No container to restart

✓

05:10:35VPS Monitorcheck

[error] containers: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] cpu: CPU 1259% (load 50.35, 4 cores) | [ok] ram: RAM 74% (12.3/16.8 GB) | [ok] disk: Disque 28% (52G/197G, 138G dispo) | [error] pm2: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] services: 1 service(s) down : Agents

🧠

05:06:19VPS Monitorai_call

Diagnostic IA: ## 🚨 **ALERTE CRITIQUE - VPS EN SURCHARGE** ### **Analyse des problèmes :** 1. **CPU en surchauffe** : 1467% d'utilisation (58.69 de load sur 4 cores = ~15x la capacité) 2. **Timeouts généralisés**...

$0.0059

⚡

05:06:09VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:06:08VPS Monitoraction

Action restart_container: No container to restart

⚡

05:06:05VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:06:01VPS Monitoraction

Action restart_container: No container to restart

⚡

05:05:59VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:05:57VPS Monitoraction

Action restart_container: No container to restart

⚡

05:05:52VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

05:05:48VPS Monitoraction

Action restart_container: No container to restart

✓

05:05:34VPS Monitorcheck

[error] containers: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] cpu: CPU 1467% (load 58.69, 4 cores) | [ok] ram: RAM 75% (12.6/16.8 GB) | [ok] disk: Disque 28% (52G/197G, 138G dispo) | [error] pm2: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] services: 1 service(s) down : Agents

🧠

04:56:13VPS Monitorai_call

Diagnostic IA: ## 🚨 Analyse des alertes VPS Monitor ### État critique détecté : - **CPU surchargé** : 1444% (charge 57.75 sur 4 cœurs) - **Timeouts généralisés** sur les checks Docker et PM2 - **Service Agents ind...

$0.0062

⚡

04:56:04VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:55:59VPS Monitoraction

Action restart_container: No container to restart

⚡

04:55:58VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:55:57VPS Monitoraction

Action restart_container: No container to restart

⚡

04:55:54VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:55:54VPS Monitoraction

Action restart_container: No container to restart

⚡

04:55:52VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:55:49VPS Monitoraction

Action restart_container: No container to restart

✓

04:55:33VPS Monitorcheck

[error] containers: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] cpu: CPU 1444% (load 57.75, 4 cores) | [ok] ram: RAM 74% (12.3/16.8 GB) | [ok] disk: Disque 28% (52G/197G, 138G dispo) | [error] pm2: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] services: 1 service(s) down : Agents

🧠

04:51:32VPS Monitorai_call

Diagnostic IA: ## 🚨 Analyse des problèmes VPS **Diagnostic principal** : Surcharge CPU extrême (1169%) causant des timeouts généralisés ### Actions correctives immédiates : 1. **Redémarrer le service Agents** (s...

$0.0066

⚡

04:51:18VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:51:17VPS Monitoraction

Action restart_container: No container to restart

⚡

04:51:12VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:51:11VPS Monitoraction

Action restart_container: No container to restart

⚡

04:51:10VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:51:09VPS Monitoraction

Action restart_container: No container to restart

⚡

04:51:04VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:50:59VPS Monitoraction

Action restart_container: No container to restart

✓

04:50:33VPS Monitorcheck

[error] containers: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] cpu: CPU 1169% (load 46.75, 4 cores) | [ok] ram: RAM 74% (12.3/16.8 GB) | [ok] disk: Disque 28% (52G/197G, 138G dispo) | [error] pm2: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] services: 1 service(s) down : Agents

🧠

04:46:44VPS Monitorai_call

Diagnostic IA: ## 🚨 Situation critique détectée ### Analyse Le VPS est en **surcharge extrême** : - CPU à **1197%** (charge 47.88 sur 4 cœurs = ~12x la capacité) - Timeouts généralisés sur les commandes système - ...

$0.0068

⚡

04:46:26VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:46:25VPS Monitoraction

Action restart_container: No container to restart

⚡

04:46:16VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:46:12VPS Monitoraction

Action restart_container: No container to restart

⚡

04:46:08VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:46:03VPS Monitoraction

Action restart_container: No container to restart

⚡

04:45:59VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:45:55VPS Monitoraction

Action restart_container: No container to restart

✓

04:45:34VPS Monitorcheck

[error] containers: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] cpu: CPU 1197% (load 47.88, 4 cores) | [ok] ram: RAM 73% (12.3/16.8 GB) | [ok] disk: Disque 28% (52G/197G, 138G dispo) | [error] pm2: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] services: 1 service(s) down : Agents

🧠

04:41:24VPS Monitorai_call

Diagnostic IA: ## 🚨 Situation critique détectée **Problème principal :** Surcharge CPU extrême (1279% sur 4 cores = ~32x la capacité) ### Actions correctives immédiates : 1. **Redémarrer le VPS** (solution rapid...

$0.0066

⚡

04:41:10VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:41:10VPS Monitoraction

Action restart_container: No container to restart

⚡

04:41:09VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:41:04VPS Monitoraction

Action restart_container: No container to restart

⚡

04:40:59VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:40:54VPS Monitoraction

Action restart_container: No container to restart

⚡

04:40:50VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:40:47VPS Monitoraction

Action restart_container: No container to restart

✓

04:40:34VPS Monitorcheck

[error] containers: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] cpu: CPU 1279% (load 51.15, 4 cores) | [ok] ram: RAM 74% (12.4/16.8 GB) | [ok] disk: Disque 28% (52G/197G, 138G dispo) | [error] pm2: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] services: 1 service(s) down : Agents

🧠

04:36:23VPS Monitorai_call

Diagnostic IA: ## 🚨 **SITUATION CRITIQUE DÉTECTÉE** ### **Analyse** Le VPS est en **surcharge extrême** : - **CPU à 1517%** (charge 60.68 pour 4 cœurs) → Système saturé - **Timeouts généralisés** → Commandes systè...

$0.0068

⚡

04:36:10VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:36:08VPS Monitoraction

Action restart_container: No container to restart

⚡

04:36:06VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:36:03VPS Monitoraction

Action restart_container: No container to restart

⚡

04:35:59VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:35:58VPS Monitoraction

Action restart_container: No container to restart

⚡

04:35:53VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:35:51VPS Monitoraction

Action restart_container: No container to restart

✓

04:35:39VPS Monitorcheck

[error] containers: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] cpu: CPU 1517% (load 60.68, 4 cores) | [ok] ram: RAM 73% (12.3/16.8 GB) | [ok] disk: Disque 28% (52G/197G, 138G dispo) | [error] pm2: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] services: 1 service(s) down : Agents

🧠

04:31:39VPS Monitorai_call

Diagnostic IA: ## 🚨 Analyse des alertes VPS Monitor ### Problème principal **Surcharge CPU critique** : 1661% sur 4 cores (charge 66.45) → Le serveur est totalement saturé ### Actions correctives immédiates ####...

$0.0067

⚡

04:31:24VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:31:19VPS Monitoraction

Action restart_container: No container to restart

⚡

04:31:18VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:31:16VPS Monitoraction

Action restart_container: No container to restart

⚡

04:31:06VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:31:02VPS Monitoraction

Action restart_container: No container to restart

⚡

04:30:58VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:30:57VPS Monitoraction

Action restart_container: No container to restart

✓

04:30:36VPS Monitorcheck

[error] containers: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] cpu: CPU 1661% (load 66.45, 4 cores) | [ok] ram: RAM 74% (12.4/16.8 GB) | [ok] disk: Disque 28% (52G/197G, 138G dispo) | [error] pm2: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] services: 1 service(s) down : Agents

🧠

04:26:17VPS Monitorai_call

Diagnostic IA: ## 🚨 Analyse critique du VPS **État** : Surcharge système critique avec timeouts généralisés ### Problèmes identifiés : - **CPU** : 1229% d'utilisation (49.17 de load sur 4 cores) 🔥 - **Timeouts*...

$0.0066

⚡

04:26:04VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:26:03VPS Monitoraction

Action restart_container: No container to restart

⚡

04:26:00VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:25:59VPS Monitoraction

Action restart_container: No container to restart

⚡

04:25:55VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:25:51VPS Monitoraction

Action restart_container: No container to restart

⚡

04:25:47VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:25:45VPS Monitoraction

Action restart_container: No container to restart

✓

04:25:33VPS Monitorcheck

[error] containers: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] cpu: CPU 1229% (load 49.17, 4 cores) | [ok] ram: RAM 73% (12.3/16.8 GB) | [ok] disk: Disque 28% (52G/197G, 138G dispo) | [error] pm2: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] services: 1 service(s) down : Agents

🧠

04:21:34VPS Monitorai_call

Diagnostic IA: ## 🚨 Analyse des problèmes VPS Monitor ### État critique détecté : - **CPU surchargé** : 1420% (charge 56.8 sur 4 cœurs) - **Timeouts généralisés** sur containers et PM2 - **Service Agents down** (...

$0.0069

⚡

04:21:19VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:21:18VPS Monitoraction

Action restart_container: No container to restart

⚡

04:21:12VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:21:11VPS Monitoraction

Action restart_container: No container to restart

⚡

04:21:07VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:21:05VPS Monitoraction

Action restart_container: No container to restart

⚡

04:20:59VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:20:57VPS Monitoraction

Action restart_container: No container to restart

✓

04:20:36VPS Monitorcheck

[error] containers: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] cpu: CPU 1420% (load 56.80, 4 cores) | [ok] ram: RAM 74% (12.3/16.8 GB) | [ok] disk: Disque 28% (52G/197G, 138G dispo) | [error] pm2: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] services: 1 service(s) down : Agents

🧠

04:17:05VPS Monitorai_call

Diagnostic IA: ## 🚨 Analyse des alertes VPS Monitor ### Problèmes identifiés : 1. **Charge CPU critique** : 1386% avec load average de 55.42 (4 cores) 2. **Timeouts système** : Containers et PM2 inaccessibles 3. *...

$0.0070

⚡

04:16:44VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:16:42VPS Monitoraction

Action restart_container: No container to restart

⚡

04:16:40VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:16:37VPS Monitoraction

Action restart_container: No container to restart

⚡

04:16:32VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:16:28VPS Monitoraction

Action restart_container: No container to restart

⚡

04:16:23VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:16:01VPS Monitoraction

Action restart_container: No container to restart

✓

04:15:40VPS Monitorcheck

[error] containers: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] cpu: CPU 1386% (load 55.42, 4 cores) | [ok] ram: RAM 74% (12.4/16.8 GB) | [ok] disk: Disque 28% (52G/197G, 138G dispo) | [error] pm2: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] services: 1 service(s) down : Agents

🧠

04:11:29VPS Monitorai_call

Diagnostic IA: ## 🚨 Analyse des problèmes critiques ### Diagnostic principal **Surcharge CPU extrême** : 1295% (charge 51.81 sur 4 cœurs) → Système quasi-bloqué ### Impacts en cascade - ❌ **Timeouts généralisés**...

$0.0071

⚡

04:11:13VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:11:08VPS Monitoraction

Action restart_container: No container to restart

⚡

04:11:03VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:11:02VPS Monitoraction

Action restart_container: No container to restart

⚡

04:11:00VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:11:00VPS Monitoraction

Action restart_container: No container to restart

⚡

04:10:57VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:10:55VPS Monitoraction

Action restart_container: No container to restart

✓

04:10:37VPS Monitorcheck

[error] containers: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] cpu: CPU 1295% (load 51.81, 4 cores) | [ok] ram: RAM 75% (12.5/16.8 GB) | [ok] disk: Disque 28% (52G/197G, 138G dispo) | [error] pm2: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] services: 1 service(s) down : Agents

🧠

04:06:22VPS Monitorai_call

Diagnostic IA: ## 🚨 Analyse des problèmes détectés ### Problème principal : **SURCHARGE CPU CRITIQUE** - CPU à **1388%** (charge 55.52 sur 4 cœurs) = système en détresse - Timeouts généralisés dus à la surcharge ...

$0.0068

⚡

04:06:10VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:06:09VPS Monitoraction

Action restart_container: No container to restart

⚡

04:06:06VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:06:06VPS Monitoraction

Action restart_container: No container to restart

⚡

04:05:57VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:05:56VPS Monitoraction

Action restart_container: No container to restart

⚡

04:05:53VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

04:05:50VPS Monitoraction

Action restart_container: No container to restart

✓

04:05:30VPS Monitorcheck

[error] containers: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] cpu: CPU 1388% (load 55.52, 4 cores) | [ok] ram: RAM 75% (12.5/16.8 GB) | [ok] disk: Disque 28% (52G/197G, 138G dispo) | [error] pm2: Check failed: spawnSync /bin/sh ETIMEDOUT | [error] services: 1 service(s) down : Agents

🧠

03:51:28VPS Monitorai_call

Diagnostic IA: ## ⚠️ ALERTE CRITIQUE - Surcharge serveur massive **Problème principal :** CPU à 1194% (load 47.76) - Le serveur est en surcharge critique ### Actions correctives immédiates : #### 1. **Identifier ...

$0.0068

⚡

03:51:16VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

03:51:13VPS Monitoraction

Action restart_container: No container to restart

⚡

03:51:12VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)

⚡

03:51:11VPS Monitoraction

Action restart_container: No container to restart

⚡

03:51:08VPS Monitoraction

Action notify: Notification logged (Telegram pas encore configuré)