Skip to main content
Coreflux HUB route card titled MyS7Route with a green status dot in the top-right corner and a row of action icons at the bottom — a gear for Configuration, a monitor icon currently hovered showing a Route Monitor tooltip, a globe for Documentation, and a trash can for Delete

​
Why Monitor Routes?

You need to know whether a route is running correctly — whether it is connected, how many messages it has processed, and whether there are errors. The Monitor window gives you live status metrics and real-time logs filtered to a single route, so you can troubleshoot without searching through broker-wide output.

​
When to Use It

  • Verifying connectivity — Confirm that a route is connected to its target system after creation or configuration changes
  • Tracking activity — Check message counts and error rates to validate that events and mappings are executing
  • Troubleshooting connections — See why a route failed to connect using status details and log entries
  • Exporting for analysis — Download filtered logs as JSON, CSV, or LOG for offline review

​
Accessing the Monitor

Open the Routes Manager, click on a route card, and select Monitor. The Monitor window opens with two tabs: Status and Logs.
Coreflux HUB Routes Manager showing how to click a route card and select Monitor to open the monitoring window

​
Status Tab

The Status tab displays live metrics from the broker for the selected route.
Coreflux HUB Monitor: SiemensS7Route window with the SIEMENS_S7 type badge, Connection Connected, Health Green, and Uptime 00:30:40 in the header; Status tab selected showing an Overview with Connection Connected Since 30m ago, Health Green with Uptime 00:30:40, Messages 1,835 with 1,835 ok and 0 failed, and Errors 0 with 0 consecutive; an Activity Timeline with Last Activity and Last Success 6s ago on 4/16/2026 and Last Error None; and an Advanced Raw JSON panel displaying the SiemensS7Route status payload with name, type, connection, health, errors, messages, lastActivity, lastSuccess, uptime, connectedSince, and timestamp fields
FieldDescription
ConnectionWhether the route is currently connected to its target
HealthHealth indicator (Green, Yellow, Red) based on error rates
MessagesTotal messages processed, with success and failure counts
ErrorsTotal and consecutive error counts
The Activity Timeline shows timestamps for last activity, last success, and last error. The Advanced: Raw JSON section shows the full status payload from the broker, including uptime and connection timestamps.

​
Logs Tab

The Logs tab shows real-time log entries filtered to the selected route.
Coreflux HUB Monitor: SiemensS7Route window with Logs tab selected showing three INFO log entries from 16:40:49 for Category Event, Name ProcessCloudCLICommand, Outcome Success, Description Processing MQTT command -addTraceLog with topics CtrlFlux/SiemensS7Route/Fatal, /Error, and /Warning; plus ALL, Fatal, Error, WARN, and INFO 3 filter buttons, a JSON format selector, an export download icon, a 3 / 3 entry counter in the bottom left, and a red Clear Logs icon in the bottom right

​
Filter by Level

Use the filter buttons to show only certain log levels:
FilterDescription
ALLShow all log entries
FATALFatal errors only
ERRORErrors only
WARNWarnings only
INFOInformational messages only

​
Log Entry Fields

Each log entry displays:
FieldDescription
TimestampWhen the event occurred
Log levelFATAL, ERROR, WARN, or INFO
CategoryEvent category (e.g., Action, Event)
NameEvent or action name
OutcomeSuccess or failure
DescriptionDetailed message or structured data

​
Export

Use the export dropdown to choose a format:
  • JSON — Structured export for parsing or integration
  • CSV — Spreadsheet-friendly format
  • LOG — Plain text log file
Click Export to download the filtered logs.
Coreflux HUB Monitor: SiemensS7Route Logs tab displaying the three INFO ProcessCloudCLICommand entries and a Logs Exported toast in the top-right corner confirming Exported 3 logs as JSON, with level filters, JSON format selector, and export controls still visible

​
Clear Logs

Use Clear Logs to remove displayed entries from the view. This does not affect the broker — it only clears the HUB display.

​
Next Steps

Routes Configuration

Edit route settings if status or logs show connection or configuration issues.

Broker Logs

View broker-wide logs for system-level troubleshooting.
Last modified on May 20, 2026