GET /api/v1/monitors/status/all — Status of All Monitors

When you call this endpoint, OpsMind iterates over every monitor stored in the database and fires a real-time HTTP GET request to each registered URL — no cached results are served. Each probe is executed sequentially using checker.js, which enforces a 5-second per-request timeout. The raw HTTP result is then fed into the trend analyzer (analyzer.js), which computes a state and a trend by comparing the current check against the last persisted log entry for that monitor. The final per-monitor snapshot is written to the Log table before being included in the response, so calling this endpoint also advances each monitor’s historical record.

Endpoint

GET /api/v1/monitors/status/all

Authorization

string

required

A valid JWT issued by the /api/v1/auth/login endpoint.
Format: Bearer <token>

Request

This endpoint takes no query parameters, path parameters, or request body.

Example

curl -X GET https://opsmind-e07b.onrender.com/api/v1/monitors/status/all \
  -H "Authorization: Bearer <token>"

Response

200 — Success

Returns a JSON object with a success flag and a data array. Each element represents one registered monitor after its live health check has been executed.

{
  "success": true,
  "data": [ ... ]
}

success

boolean

Always true on a successful response.

data

array

Array of status result objects — one entry per registered monitor.

Show Status result object fields

integer

The unique numeric identifier of the monitor as stored in the Monitor table.

name

string

The human-readable display name assigned to the monitor at creation time.

url

string

The full URL that was probed during this health check cycle.

status

integer

The HTTP response code returned by the target service. Common values:

Code	Meaning
`200`	Service responded successfully
`404`	Endpoint or resource not found
`500`	Target server encountered an internal error
`0`	No response received — connection timed out or refused

message

string

A concise, human-readable interpretation of the HTTP status code produced by the analyzer. Examples: "OK - Service Operational", "Resource Not Found", "Internal Server Error", "No Response".

trend

TrendStatus enum

Describes how the service’s health has changed relative to its previous recorded state. Possible values:

Value	Description
`STABLE`	State has not changed or is healthy from the start
`DROP_DETECTED`	Service degraded or went down compared to last check
`RECOVERED`	Service came back up after a prior `DOWN` or `DEGRADED` state
`OFFLINE`	Service has been unreachable across consecutive checks

state

ServiceStatus enum

The current operational state of the monitor derived from the live probe. Possible values:

Value	Condition
`UP`	Online and responding within 1500 ms
`DEGRADED`	Online but response time exceeded 1500 ms
`DOWN`	Probe failed — no HTTP response received
`PENDING`	No prior log record exists to compare against

Sample Response

{
  "success": true,
  "data": [
    {
      "id": 1,
      "name": "Payments API",
      "url": "https://payments.internal.example.com/health",
      "status": 200,
      "message": "OK - Service Operational",
      "trend": "STABLE",
      "state": "UP"
    },
    {
      "id": 2,
      "name": "Auth Service",
      "url": "https://auth.internal.example.com/ping",
      "status": 500,
      "message": "Internal Server Error",
      "trend": "DROP_DETECTED",
      "state": "DOWN"
    },
    {
      "id": 3,
      "name": "Notification Worker",
      "url": "https://notify.internal.example.com/status",
      "status": 0,
      "message": "No Response",
      "trend": "OFFLINE",
      "state": "DOWN"
    }
  ]
}

Each call to this endpoint runs live HTTP probes sequentially — one after another, not in parallel. Total response time therefore scales with the number of registered monitors multiplied by their individual latencies. A deployment with 20 monitors each averaging 300 ms will take roughly 6 seconds to complete. Plan polling intervals and client timeouts accordingly.

Error Responses

401 — Unauthorized

Returned when the Authorization header is missing, malformed, or contains an expired or invalid JWT.

{
  "success": false,
  "error": "Unauthorized"
}

500 — Internal Server Error

Returned when an unexpected error occurs during the health check execution loop or database interaction.

{
  "success": false,
  "error": "Internal server error"
}

Authentication

Monitors

Observability

GET /api/v1/monitors/status/all — Status of All Monitors

Endpoint

Request

Example

Response

200 — Success

Sample Response

Error Responses

401 — Unauthorized

500 — Internal Server Error

Build docs developers (and LLMs) love

Authentication

Monitors

Observability

Documentation Index

​Endpoint

​Request

​Example

​Response

​200 — Success

​Sample Response

​Error Responses

​401 — Unauthorized

​500 — Internal Server Error

Build docs developers (and LLMs) love

Endpoint

Request

Example

Response

200 — Success

Sample Response

Error Responses

401 — Unauthorized

500 — Internal Server Error