System Logs
View application logs and diagnostics for troubleshooting and monitoring Konnect’s internal operations.
Overview
Section titled “Overview”The System Logs page provides real-time access to Konnect’s application logs. Use it to:
- Monitor application health and activity
- Debug connection issues with data sources
- View API request and response details
- Track AI assistant operations and tool usage
- Diagnose errors and unexpected behaviour
Opening the System Logs
Section titled “Opening the System Logs”- Click System Logs in the sidebar navigation.
- The log viewer opens with the most recent log entries displayed.
Understanding the log display
Section titled “Understanding the log display”Each log entry shows:
| Field | Description |
|---|---|
| Timestamp | When the event occurred |
| Level | Severity — DEBUG, INFO, WARN, or ERROR |
| Source | Which component generated the log (e.g., MQTT, OPC-UA, Database, AI) |
| Message | The log message with details |
Log levels
Section titled “Log levels”| Level | Colour | Meaning |
|---|---|---|
| DEBUG | Grey | Detailed diagnostic information for developers |
| INFO | Blue | Normal operational events (connections, queries, etc.) |
| WARN | Yellow | Potential issues that don’t prevent operation |
| ERROR | Red | Failures that require attention |
Filtering logs
Section titled “Filtering logs”Step-by-step:
- Use the Level dropdown to filter by severity (e.g., show only WARN and ERROR).
- Use the Source dropdown to filter by component (e.g., only MQTT logs).
- Use the Search field to find logs containing specific text.
- Filters combine — you can filter by level AND source AND search text simultaneously.
Common log patterns
Section titled “Common log patterns”Successful database connection
Section titled “Successful database connection”INFO [Database] Connected to PostgreSQL at host.docker.internal:5432/manufacturingINFO [Database] Discovered 12 tables in schema 'public'MQTT broker connection
Section titled “MQTT broker connection”INFO [MQTT] Connecting to mqtt://broker.example.com:1883INFO [MQTT] Connected successfully, client ID: konnect-abc123INFO [MQTT] Subscribed to topic: factory/#AI assistant query
Section titled “AI assistant query”INFO [AI] User query: "Show me temperature readings for the last hour"INFO [AI] Selected tools: [database_query, chart_generation]INFO [AI] Executed query on PostgreSQL (42ms, 360 rows)INFO [AI] Generated line chart for dashboardConnection error
Section titled “Connection error”ERROR [Database] Failed to connect to MySQL at 192.168.1.100:3306 — Connection refusedWARN [Database] Retrying connection in 5 seconds...ERROR [Database] Connection retry failed after 3 attemptsAuto-scroll and live updates
Section titled “Auto-scroll and live updates”- Logs update in real time as events occur.
- Auto-scroll is enabled by default — new log entries scroll into view automatically.
- Scroll up manually to pause auto-scroll and review older entries.
- Click Resume to re-enable auto-scroll.
Log retention
Section titled “Log retention”Logs are stored in memory during the current session. When Konnect restarts, previous logs are cleared. For persistent logging, configure Docker logging drivers:
docker run -d \ --name konnect \ --log-driver json-file \ --log-opt max-size=10m \ --log-opt max-file=3 \ -p 7080:7080 \ -v konnect_data:/app/data \ ghcr.io/kyanitesolutions/konnect:beta-latestYou can then access persistent logs with:
docker logs konnect --tail 100 --followNext steps
Section titled “Next steps”- Troubleshooting & FAQ → — Solutions to common issues.
- Configuration → — Environment variables and settings.