Skip to content

Operations And Monitoring ​

Page Guide ​

Use CasesFor inspecting service status, locating faults, viewing logs, and maintaining scheduled tasks after the production environment goes live.
PrerequisitesDeployment is complete, and you have server, container, database, and platform administrator permissions.
Check TargetsBackend, frontend, MySQL, Redis, EMQX, time-series database, ZLMediaKit, scheduled tasks, and business logs.
Acceptance CriteriaCore services run stably, key links are available, logs are traceable, and alerts and work orders form a closed loop.

1. Daily Inspection Checklist ​

Check ItemCheck ContentException Handling
Web pagesLogin, home, product, and device pages are accessibleCheck Nginx, the backend, and the browser console
Backend serviceProcess or container is running, logs have no continuous exceptionsCheck backend logs and restart abnormal services
MySQLConnections, slow SQL, disk spaceOptimize SQL, expand disk, clean up logs
RedisMemory, connections, key expiration policyClean up abnormal cache, check password and network
EMQXClient connections, authentication, subscriptions, rulesCheck authentication APIs and ports
Time-series databaseWrites, queries, disk usageCheck the data retention policy
ZLMediaKitLive streaming, playback, Hook, recordingCheck media service logs
Scheduled tasksWhether report, maintenance, and sync tasks are executedCheck task logs and Quartz status

2. Common Commands ​

Docker deployment environment:

shell
cd /var/data
docker-compose ps
docker ps
docker logs -n 300 java
docker logs -n 200 nginx
docker logs -n 200 emqx
docker stats

Linux service checks:

shell
free -h
df -h
top
ss -lntup

3. Operations Entries In The Platform ​

EntryPurpose
System Monitoring > Online UsersView currently logged-in online users
System Monitoring > Operation LogsView key user operations
System Monitoring > Login LogsView login success and failure records
System Monitoring > Scheduled TasksView and maintain Quartz tasks
Operations Management > Notification LogsView notification delivery results
Device Detail > Device LogsView device reporting, delivery, and exceptions
Video CenterView channel, streaming media, and recording status

After each go-live or upgrade, run through the minimal business link at least once:

  1. Log in to the admin console.
  2. Create or select a test product.
  3. Bring a simulated device online with MQTTX.
  4. Report property data.
  5. Deliver commands from the platform.
  6. Trigger a rule or alert.
  7. Send a notification.
  8. Generate a work order or report.

5. FAQ ​

Pages open but APIs report errors ​

Check the backend service, Nginx proxy, API prefix, login token, backend logs, and database connection.

Devices go offline on a large scale ​

Check EMQX, MQTT ports, authentication APIs, server network, security groups, and whether the protocol configuration was recently upgraded.

Reports or maintenance tasks do not run automatically ​

Check scheduled task status, server time, Quartz tables, task logs, and whether tasks are duplicated or missed in a cluster environment.

Video playback is unstable ​

Check ZLMediaKit, bandwidth, browser protocol compatibility, camera network, and streaming media ports.

FastBee | fastbee.cn