Collector Status ​

A collector's console shows one screen today: System Status. It tells you what the collector is doing right now, and — if it isn't connected to its appliance — why. Open it any time you want to confirm a collector is healthy, or to start diagnosing one that isn't.

Alongside the headline, the screen shows whatever it currently knows: how long the collector has been in this state, the appliance address it's configured to reach, its own software version, its serial number, and the appliance's certificate fingerprint. If support needs more detail than the headline gives, the screen also shows a short technical line you can read out to them. The screen refreshes automatically every few seconds, so you don't need to reopen it to see a change.

Connecting to the appliance... ​

The collector is attempting to connect. This is normal right after the service starts, or right after it loses and re-establishes a connection, and it should pass quickly. If the screen stays on this message for more than a minute or two, treat it as The appliance is unreachable.

Connected to the appliance ​

The collector is connected and sending data. No action needed.

The appliance is unreachable ​

The collector can't open a network connection to its appliance. The appliance may be powered off, the configured address may be wrong, or something on the network path between them may be blocking the connection.

Check that the appliance is powered on and reachable on the network, and confirm the address the collector is configured to use is correct. The collector keeps retrying on its own, so once the problem is fixed it reconnects without any further action from you.

The secure connection to the appliance failed ​

The collector reached the appliance, but the encrypted connection between them couldn't be established. This usually points to a certificate problem on the appliance, a clock that has drifted out of sync, or a network device interfering with the connection.

Check the appliance's certificate and the collector's clock. If the problem doesn't clear on its own, contact support and read them the technical detail line shown on screen.

The appliance's certificate does not match the pinned one ​

The collector remembers a specific appliance from when it was paired, and the appliance is now presenting a different identity than the one the collector remembers.

If the appliance's certificate was deliberately renewed or replaced, this is expected — pair the collector again to have it trust the new one. If you didn't make that change, don't re-pair yet: contact support first, since this can also mean the collector is talking to the wrong device.

The appliance rejected this collector's credentials ​

The appliance doesn't accept the credentials this collector is presenting. Pair the collector again to get it a fresh set of credentials from the appliance.

The appliance revoked this collector's credentials ​

An administrator on the appliance has explicitly withdrawn this collector's access — for example, because the collector was decommissioned or replaced.

If this collector should still be connected, pair it again from the appliance. If it's being retired, no action is needed.

The appliance rejected this collector's proof of identity ​

The appliance recognizes this collector but could not confirm its identity when it tried to connect.

Pair the collector again to give it a fresh identity the appliance will accept.

This collector is not paired with an appliance yet ​

This is a freshly installed collector with no connection configured. Pair it with its appliance to get started.

The pairing code was rejected ​

The pairing code entered during setup wasn't accepted — it may have been mistyped, already used, or issued for a different collector. Get a fresh pairing code from the appliance and try again.

The pairing code expired ​

The pairing code was valid, but too much time passed before setup finished. Generate a new pairing code and complete setup promptly.

The collector service has failed ​

The collector's background service has stopped unexpectedly. This takes priority over any other message the screen would otherwise show. Contact support — they may need to restart the service or investigate further.

The collector service is not running ​

This means one of two things: either the collector hasn't been paired yet, so the service is intentionally staying off (see This collector is not paired with an appliance yet), or the service on an already-working collector was stopped.

If this is a new collector, pair it. If it was working before, find out why the service was stopped and start it again.

The collector is starting... ​

The service is coming up and hasn't reported its state yet. This should pass within a few seconds. If it doesn't, contact support.

Unknown collector state (this pulse-cli may be older than the collector) ​

The collector reported a state the console software on this box doesn't recognize yet — usually because the collector has been updated to a newer version than the console software. Update the console software to match. In the meantime, the technical detail line on screen shows what the collector is actually reporting.

  • Collector Pairing — pairing a collector, and re-pairing one whose credentials or pairing code were rejected.
  • Deployment Options — the firewall rules a collector needs, when a message here points at the network path between it and the appliance.