Brinkhaus openXEdge
How-to v2

You see a symptom (no new measurement data, an update keeps failing) and want to know which service of the edge is responsible.

Steps

  1. Top-right cog → Settings → Diagnosis in the sidebar.

  2. The list shows every edge service of your device (such as main-ui, datastore, postgres, update-service and — depending on the equipment — grafana, idea4sbridge, iolink-proxy, mosquitto, usb-service, flecs) — each with a status dot and an N messages drawer:

    Settings → Diagnosis with green status dots

  3. Read the status:

    • 🟢 green → no open messages, the service considers itself healthy.
    • 🟡 yellow → at least one warning. Service still runs, but something is off.
    • 🔴 red → at least one error. Service may be degraded or failed.

  4. For any non-green dot expand the N messages drawer — individual messages appear with their code and an explanation.

  5. Look the code up in the Diagnosis codes table — it explains the meaning and the typical action.

Common patterns

  • All green but Grafana has no data: usually a data-pipeline issue below the diagnosis threshold. Check the IO-Link master (see Configure IO-Link master) and the MQTT subscriptions.
  • update-service red shortly after an update: the update was rolled back — the previous state is running again; see Diagnosis codes 2xxx.
  • datastore reports code 7002 (FleetManager not reachable): a notice, not a fault — the DataStore keeps working. Typical for a device without internet access, or right after first install before the device is known in the fleet — see Fleet onboarding.

If you’re stuck

Brinkhaus personnel can read the edge’s diagnosis centrally once it is connected to the FleetManager (see Fleet onboarding). Send the hotline the serial number (the machine ID on older devices) and the symptom; they read the codes in parallel.