Server Logs & System Monitoring

Server Logs are crucial for platform administrators, security teams, and developers to monitor system health, troubleshoot issues, investigate incidents, and proactively manage the InnoSynth-Forjinn infrastructure.

Accessing Server Logs

• UI (if enabled):

  • Go to Settings → Logs or Admin → Server Logs
  • Filter by date, type (system, error, audit), user, or service

• Filesystem:

  • Logs are written to /logs or a configured external log sink
  • Typical files: system.log, error.log, access.log, chatflow.log, agent.log, etc.
  • Use tail, grep, or a log viewer for analysis

• Centralized Cloud Logging:

  • Export/logs to ELK (Elasticsearch), Splunk, CloudWatch, or another SIEM platform for advance analytics and retention

Types of Logs

• System Logs: Platform/service events, core operations, deployment activities
• Error Logs: Uncaught exceptions, failed job traces, stack traces
• Access Logs: User API/web activity, auth results, IP/device summaries
• Action/Agent/Flow Logs: Per-run execution traces, performance timings, memory/cpu stats
• Audit Logs: Admin actions, role changes, settings modifications

Monitoring & Alerting

• Use dashboards (e.g. Grafana, Kibana) to monitor log streams, set up alerts for:
  • Server errors (>X in Y min)
  • Login/auth failures spikes
  • Resource (CPU/mem) or disk issues
  • Unusual agent/tool failure patterns

Best Practices

• Rotate logs daily or at platform’s retention setting (default: 7–30 days)
• Backup logs before deletion for compliance requirements
• Mask/anonymize PII in logs where possible
• Set correct file permissions to protect log integrity

Troubleshooting

• Platform slow/hanging: Review error, gc, and system logs for OOM or excessive errors.
• Suspected security incident: Audit access, action, and error logs for anomalous patterns.
• Log storage full: Set up log rotation/compression; offload to cold storage.
• Can't see logs in UI: Check admin role/permissions, or filesystem path in platform config.

Regularly reviewing and monitoring server logs is critical for robust, secure, and compliant operations—always audit periodically and after incidents.