Public demo · Automatically signed in · Changes reset every 20 minutes · External checks and messages are disabled. Do not enter private data.
Northwind Internal

Bring in

Let your monitoring and jobs keep this page up to date on their own

Connect a source

Pharos changes the component; you decide what sends it

  1. What knows whether it is healthy?

    Pharos can also check websites and ports itself: set that on the component.

  2. Only components without a built in check are listed, so two sources never fight.

  3. Use a token with write access

    The token proves the request comes from you. It only works for this page.
    No write token on this page yet. Create a new token

    A token is shown once, when it is created. Paste it where the examples say YOUR_TOKEN.

  4. Copy this into your tool

    In n8n add an HTTP Request node with these settings.
    Request
    PUThttps://demo-pharos.solutionmax.net/api/v1/pages/internal/components/17
    Header
    Authorization: Bearer YOUR_TOKEN
    Status to send
    Body
    {"status": 1}
    The same as a shell command 
    curl -X PUT 'https://demo-pharos.solutionmax.net/api/v1/pages/internal/components/17' -H 'Authorization: Bearer YOUR_TOKEN' -H 'Content-Type: application/json' -d '{"status": 1}'

    Existing clients may also send the token in an X-Cachet-Token header.

    This changes the component only. It does not open an incident or notify anyone.

    Notification type: Webhook, method POST, body application/json. URL:
    POSThttps://demo-pharos.solutionmax.net/api/v1/pages/internal/integrations/kuma/17
    Additional headers (JSON)
    {"Authorization": "Bearer YOUR_TOKEN"}
    Kuma sends every change on its own. Up sets Operational, down sets Major outage, maintenance sets Under maintenance, pending changes nothing. Kuma's test button sends no state and is refused; test with a real monitor.
    No heartbeat components yet. Add a component with source Heartbeat and its check in URL appears here.

    Add a heartbeat component

    No check in on time: the component goes to Major outage. The next check in sets it back. The secret in the URL is the authorization; no token is needed.
    Need an incident with a message instead of a status change?

    POST this to https://demo-pharos.solutionmax.net/api/v1/pages/internal/incidents with the same header. It appears on the page and is mailed to subscribers. Keep the returned data.id and post follow ups to https://demo-pharos.solutionmax.net/api/v1/pages/internal/incidents/INCIDENT_ID/updates; send status resolved to close it.

    {
    "name": "Service unavailable",
    "status": "investigating",
    "message": "We are investigating a service interruption.",
    "impact": "major",
    "components": {
        "17": "major_outage"
    }
}

Already feeding this page

3 components
  • Billing, Ticket desk, VPNNothing connected: set by hand or through the API Manual

The other direction

To tell n8n or a chat when an incident opens, add a destination under Send out.

Are you sure?