Skip to main content
Coreflux HUB connector 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 Connector Monitor tooltip, a globe for Documentation, and a trash can for Delete

Connector card for MyS7Route with the monitor icon highlighted and a Connector Monitor tooltip

​
Why Monitor Connectors?

You need to know whether a connector 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 connector, so you can troubleshoot without searching through broker-wide output.

​
When to Use It

  • Verifying connectivity — Confirm that a connector 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 connector 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 Connectors Manager, click on a connector card, and select Monitor. The Monitor window opens with two tabs: Status and Logs.
Coreflux HUB Connectors Manager showing how to click a connector card and select Monitor to open the monitoring window

Opening the Monitor from a connector card in the Connectors Manager

​
Status Tab

The Status tab displays live metrics from the broker for the selected connector.
Coreflux HUB Monitor window for the BACNET connector TwinEnergyBms with Connection Connected, Health Green, and Uptime in the header; the Status tab shows Overview cards for Connection, Health, Messages, and Errors, and an Activity Timeline with Last Activity, Last Success, and Last ErrorCoreflux HUB Monitor window for the BACNET connector TwinEnergyBms with Connection Connected, Health Green, and Uptime in the header; the Status tab shows Overview cards for Connection, Health, Messages, and Errors, and an Activity Timeline with Last Activity, Last Success, and Last Error

Monitor window, Status tab: connection, health, and uptime in the header, then the Overview cards and the Activity Timeline

The Activity Timeline shows timestamps for last activity, last success, and last error. When the connector has recent failures, a Recent Errors list appears below the timeline with a link to view them all in the Logs tab. Uptime is shown in the window header.

​
Start and Stop

The header has a Stop button while the connector runs, and Start while it’s stopped. Stop saves the connector with DISABLE true, the same as Disable on its card. The connector stays defined but doesn’t run, and the header says so. Start removes the line. The button follows changes made elsewhere, such as in the LoT Editor.
Coreflux HUB Monitor window for the FILE_STORAGE connector FlightLog, with the header text Stopped. The connector stays defined but does not run. and a Start button, above the Status tab with Connection Disconnected, Health Red, Messages 12 with 12 ok and 0 failed, Errors 0, and the activity timelineCoreflux HUB Monitor window for the FILE_STORAGE connector FlightLog, with the header text Stopped. The connector stays defined but does not run. and a Start button, above the Status tab with Connection Disconnected, Health Red, Messages 12 with 12 ok and 0 failed, Errors 0, and the activity timeline

Monitor window for a stopped FILE_STORAGE connector, with Start in the header

​
Logs Tab

The Logs tab shows real-time log entries filtered to the selected connector.
Coreflux HUB Monitor window for the TwinFillerPlc OPCUA connector with the Logs tab selected: ALL, Fatal, Error, WARN, and INFO level filters, a JSON format selector and export button, an ERROR entry for CheckRouteConnection, and an INFO entry for RouteCertificatesCoreflux HUB Monitor window for the TwinFillerPlc OPCUA connector with the Logs tab selected: ALL, Fatal, Error, WARN, and INFO level filters, a JSON format selector and export button, an ERROR entry for CheckRouteConnection, and an INFO entry for RouteCertificates

Monitor window — Logs tab with level filters, JSON format selector, and export controls

​
Filter by Level

Use the filter buttons to show only certain log levels:

​
Log Entry Fields

Each log entry displays:

​
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

Exporting SiemensS7Route logs as JSON with a Logs Exported confirmation toast in the top-right corner

​
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

Connectors Configuration

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

Broker Logs

View broker-wide logs for system-level troubleshooting.
Last modified on October 21, 2026