feat(NetworkMapScheduler): integrate network map scheduler functionality with API routes and frontend components for enhanced network monitoring

backend/server.js

@@ -31,6 +31,8 @@ const mikrotikConfigRoutes = require('./routes/mikrotikConfigRoutes');
 const mikrotikBackupRoutes = require('./routes/mikrotikBackupRoutes');
 const trafficRoutes = require('./routes/trafficRoutes');
 const { initMikrotikBackupScheduler } = require('./services/mikrotikBackupScheduler');
+const { initNetworkMapScheduler } = require('./services/networkMapScheduler');
+const schedulerRoutes = require('./routes/schedulerRoutes');
 
 const app = express();
 const port = Number(process.env.PORT) || 3001;
@@ -476,6 +478,15 @@ app.get('/api/mikrotik/backups/item', mikrotikBackupRoutes.getBackup);
 app.post('/api/mikrotik/backups/diff', mikrotikBackupRoutes.diffBackups);
 app.post('/api/mikrotik/backups/run', writeLimiter, mikrotikBackupRoutes.runBackupNow);
 
+// === NETWORK MAP CACHE (для быстрой загрузки карты сети) ===
+app.get('/api/network-map-cache', schedulerRoutes.getNetworkMapCache);
+
+// === SCHEDULER (карта сети: пинг и скорость по расписанию) ===
+app.get('/api/scheduler/network-map/settings', schedulerRoutes.getNetworkMapSchedulerSettings);
+app.patch('/api/scheduler/network-map/settings', writeLimiter, schedulerRoutes.patchNetworkMapSchedulerSettings);
+app.get('/api/scheduler/network-map/logs', schedulerRoutes.getNetworkMapSchedulerLogs);
+app.post('/api/scheduler/network-map/run-now', writeLimiter, schedulerRoutes.runNetworkMapSchedulerNow);
+
 // === MIKROTIK VALIDATION ===
 app.post('/api/mikrotik/validate', async (req, res) => {
     const { config } = req.body;
@@ -503,12 +514,15 @@ app.use(errorHandler);
 
 app.listen(port, () => {
   console.log(`Server is running on http://localhost:${port}`);
+  try {
+    initMikrotikBackupScheduler(logger);
+  } catch (e) {
+    logger.error({ component: 'mikrotik-backup', err: e && e.message }, 'Failed to start backup scheduler');
+  }
+  try {
+    initNetworkMapScheduler(logger, port);
+  } catch (e) {
+    logger.error({ component: 'network-map-scheduler', err: e && e.message }, 'Failed to start network map scheduler');
+  }
 });
 
-// Запускаем планировщик автоматического бэкапа MikroTik (если включен через ENV)
-try {
-  initMikrotikBackupScheduler(logger);
-} catch (e) {
-  logger.error({ component: 'mikrotik-backup', err: e && e.message }, 'Failed to start backup scheduler');
-}
-