Workers (collection points)

What it's for

A worker is a collection point: it is what actually runs your checks and reports their results. SecuMon distributes the executions across the available workers. You can consult the list of your workers to know where the checks run from (location, availability), and remove a worker you no longer use.

The worker model

Using it from the portal

The Workers section lists your collection points with their location, status and last sign of life. You can remove a worker from this view.

Listing: all roles. Remove: owner and admin.

Using it through the API

List workers

GET /api/v2/workers

curl -s https://api.secumon.secuaas.ovh/api/v2/workers \
  -H "Authorization: Bearer $SECUMON_TOKEN"

[
  {
    "id": "9a8b7c6d-1234-4abc-9def-aabbccddeeff",
    "name": "collecteur-bhs-1",
    "location": "OVH BHS",
    "status": "active",
    "checks_executed": 0,
    "last_heartbeat": "2026-06-23T12:00:30Z"
  }
]

The response is always a JSON array.

Remove a worker

DELETE /api/v2/workers/:id

curl -s -X DELETE https://api.secumon.secuaas.ovh/api/v2/workers/9a8b7c6d-1234-4abc-9def-aabbccddeeff \
  -H "Authorization: Bearer $SECUMON_TOKEN"

Response: 204 No Content. An unknown identifier returns 404.

Use cases

• Check the origin of measurements: confirm from which location your checks run (useful for targets sensitive to geolocation).
• Diagnose a silent collection point: an old last_heartbeat or a status: inactive indicates a worker that is no longer reporting results.
• Clean up: remove a decommissioned worker to keep only the collection points that are actually active.

Tips

• Before removing a worker, make sure no critical check depends exclusively on it, to avoid a collection interruption.
• The last_heartbeat is the best health indicator of a worker: compare it to the current time to spot a silent collection point.