JAMS Incident Management | Alerting, escalation and on-call

Two-way remediation connector

Install the JAMS Incident Connector on your JAMS Scheduler host so on-call engineers can restart, continue, or cancel jobs right from a voice call or SMS reply. The connector only reaches out to JAMS Incident Management — no inbound firewall changes.

Prerequisite — JAMS Scheduler REST API. The Agent runs remediations through your JAMS Scheduler REST API, so it must be installed and running before the Agent can act on jobs. During setup you point the Agent at your JAMS REST API URL. Install the Agent on a host that can reach that URL — the simplest is the same server the REST API runs on (point it at localhost). If your REST API runs on a separate server, install the Agent on that server.

Generate a connector token and copy it.
Download and run the installer on the JAMS host.
Download installer (.msi)
In the installer, paste the token above, then under Connect to JAMS enter your JAMS URL and credentials.

JAMS Service Monitoring

Alerts when a JAMS Windows service stops — the health of JAMS itself, as opposed to the job failures your Connections report. Checked by the connector Agent on the JAMS host, so it still works when the JAMS REST API is down with it.

Service monitoring needs a connector Agent. Install and pair one in Two-way remediation connector above, then come back — this card will list whatever JAMS services it finds.

Your JAMS Connections

Each Connection bundles a JAMS Server credential, a JAMS Incident Management Flow with your chosen recipients, and the inbound webhook your Notification Jobs post to.

No JAMS Connections yet. Create one below.

Create a JAMS Connection

One Connection per JAMS Server. You'll get a webhook URL and a ready-to-paste PowerShell Notification Job at the end — point all of your JAMS Jobs at the same URL and JAMS Incident Management handles the rest.

1. Name this Connection

Connection name

Used to identify this Connection in JAMS Incident Management and as the jamsCredentialRef in the PowerShell snippet.

2. Who gets notified?

No team members or groups loaded. Add team members → or create a group →

JAMS failure alerts go to everyone selected, in escalation order. Groups are expanded to their current members at notification time. Teams/Slack channel posts deliver to that channel on their own — they don't depend on the per-user “Channels to use” checkboxes below.

Channels to use

Voice call is the most reliable for failure alerts.

Escalation interval (minutes)

Wait this long for each recipient to ack before moving to the next.

Rate & runaway controlAlways on

Protects this tenant's notification quota when the same alert keeps repeating. If a repeating alert exceeds the threshold below, the flood collapses into one alert you can mute or pause.

Cooldown between repeats

After the same alert fires, wait this long before it can alert again.

minutes

How chatty is this flow?

Sets how many repeats within 15 minutes trip the storm brake.

Trips when the same alert repeats 10× in 15 min.

Advanced threshold

Collapse afterrepeats withinminutes.

When a storm is detected

3. JAMS Incident Management Webhook Key

This is the JAMS Incident Management-side key. JAMS Notification Jobs include it in every webhook call so JAMS Incident Management knows the request is yours. Pick an existing key or generate a new one.

Generate a new JAMS Incident Management webhook key

On save, we'll generate the PowerShell Notification Job script you paste into JAMS — with your webhook URL, key, and Connection name already filled in.