Runtime Sensors

Enroll each Sensor to authenticate it with Team Server.

Enroll a Runtime Sensor

Only an Administrator can create a Sensor:

1. Open Runtime Sensors > Create; enter name and description.
2. Save and copy the one-time token.
3. Set ENDURA_SENSOR_TOKEN and ENDURA_TEAM_SERVER in the host’s protected environment or secret manager.

Operators can view, edit, and delete Sensors, but cannot create them or rotate tokens.

Monitor Status and Compatibility

The list shows status, version, last contact, and compatibility. Five minutes without a status update makes a Sensor inactive.

Major versions must match; minor/patch differences are allowed. A mismatch retains enforcement and pauses submission. See compatibility behavior.

Rotate a Token

An Administrator selects Rotate Token, copies the replacement, updates the host configuration, and restarts the Sensor. Rotation immediately revokes every earlier token generation.

For local automation, sensor_rotate_token previews the target and requires confirm:true; see Sensor tasks.

Read Runtime Sensor Logs

Administrators select View Logs on a Sensor. See viewer controls and limits. Clear affects only the browser view. Host logs remain available with root-only endura sensor logs.

Failed log batches are not replayed; later batches resume automatically when Team Server responds.

Deleting a Sensor removes its deployments, workloads, workload violations, and centrally stored logs. Pipeline builds and their violations remain. Export required records first.