Get phone and SMS alerts fromBMC Control-M
BMC Control-M schedules and runs the batch jobs and file transfers that businesses depend on overnight. When a job ends not OK, Spike pages whoever is on call: a phone call, SMS, Slack message or email, escalating until someone picks it up.
Set up with AI
I use BMC Control-M for monitoring and Spike for on-call and incident management. Walk me through connecting them: create a BMC Control-M integration in Spike, copy its webhook URL, and add that webhook to BMC Control-M alert settings. Then help me send a test alert to confirm incidents show up in Spike.
What is BMC Control-M?
BMC Control-M is a workload automation platform. It orchestrates the batch jobs, file transfers and data pipelines that settle payments, close ledgers and refresh reports, across mainframes, servers and cloud services. When a job ends not OK, runs too long or misses an SLA, Control-M raises an alert with a severity, the job, the host and the application it belongs to.
Inside Control-M, that alert waits on a console for an operator to notice it. Sent to Spike, it becomes a page: the on-call engineer is called and texted within seconds, and an alert nobody acknowledges climbs the escalation policy until someone answers. The incident title carries Control-M’s message, the job name and the host, so whoever wakes up knows what failed and where before opening anything.
Every Control-M alert has a numeric id, and Spike uses it to keep repeats together. An update to an alert that is already open is added to the same incident instead of paging the team again, and two separate alerts stay two separate incidents. Alert routing rules can read the severity, application and job name, so a test batch doesn’t wake the people a production settlement run does.
When an operator sets the alert to Handled in Control-M, Spike matches it back to the open incident by id and resolves it. Spike resolves only on that Handled status, so an alert that is never handled in Control-M stays open.
How to set up BMC Control-M alerts
Every Spike integration is a unique webhook URL. Paste it into BMC Control-M and alerts start flowing — no agents, no code.
Step 1: Create a BMC Control-M integration in Spike
In your Spike dashboard, open Integrations and choose BMC Control-M. Spike generates a unique webhook URL for this integration — copy it, and attach the integration to the service and escalation policy that should answer these alerts.
Step 2: Point Control-M's External Alerts at Spike
Control-M has no native webhook, so configure an External Alerts script that posts each alert's fields as one flat JSON object to the Spike URL. Use one Spike integration per Control-M environment, since alert ids are only unique within one.
Step 3: Watch an alert become an incident
A new alert opens an incident titled with Control-M's message plus the job and the host it ran on, such as "Ended not OK: nightly-invoice-export on prod-batch-agent-02". Later updates to the same alert join that incident, and when an operator handles the alert in Control-M, the incident resolves itself.
That's it — BMC Control-M alerts now page whoever is on call.
