Side by side
Splunk On-Call (formerly VictorOps) is paging plus collaboration tied into the Splunk observability suite. Argus takes a different approach: AI-native classification, embedding-powered similar-incident search, and a calm interface designed to lower cognitive load during incidents — without the legacy ITSM weight.
Argus, first read
I've stood watch alongside Splunk On-Call in plenty of NOCs. Here is what I'd take off your plate the moment you let me on the watch — and what Splunk On-Call would still ask of you tomorrow.
Argus · alongside Splunk On-Call
I can run alongside Splunk On-Call for the first month — I watch, I classify, I draft. Splunk On-Call keeps paging. When you trust my reads, you wind it down at your pace.
Argus · for teams comparing Splunk On-Call
Three chapters, ten observations. Each row is what I do on one side, what a human still does with Splunk On-Call on the other — sourced, ranked, and reversible.
Chapter one · How a shift starts
Human-led with Splunk On-Call
You spend the first week mapping a CMDB, building workflows, and configuring escalation policies before Splunk On-Call watches anything.
I start watching the moment you connect a datasource. No CMDB, no workflow editor, no setup form.
Human-led with Splunk On-Call
A human watches the dashboard, or no one does. Splunk On-Call sends a page only after a threshold rule someone wrote months ago fires.
I watch every service you've shown me — 24/7. I name what I see, I rank what matters.
Chapter two · When something moves
Human-led with Splunk On-Call
On-call reads the alert, decides severity, looks up the service owner, opens a Slack thread, asks who's around.
I classify with confidence and sources. Severity, scope, likely owner — all named, all sourced.
Human-led with Splunk On-Call
Splunk On-Call surfaces past tickets by keyword match. If you didn't tag it the same way last time, you won't find it now.
I cross-reference past incidents by vector similarity — same shape, same hour, same service, surfaced in seconds.
Human-led with Splunk On-Call
Runbook lookup, manual throttle, manual rollback. Every keystroke is yours, every decision is yours, every typo is yours.
I draft the remediation and stage it. Safe-to-auto runs; high-risk waits on your nod.
Human-led with Splunk On-Call
Splunk On-Call pages whoever the rotation says, whatever the hour, whether or not the page could have been a click on a runbook.
I only wake someone when I can't move it myself. Pages are the last resort, not the first move.
Chapter three · When it's over and the lesson lands
Human-led with Splunk On-Call
Splunk On-Call hands you a blank template and a calendar invite three days later. Someone has to remember what happened from memory.
I draft the postmortem from the timeline I just watched. Yours to revise; mine to file.
Human-led with Splunk On-Call
Activity log shows clicks and field changes. Reconstructing why a decision was made is a project, not a query.
The trail is my diary. Every decision, every confidence, every source — logged with actor and timestamp.
Human-led with Splunk On-Call
Keyword search across tickets and KB articles, with quotes around the right terms and luck on your side.
Ask me anything — plain English. I read my own diary back to you with the receipts attached.
Human-led with Splunk On-Call
License + consulting + per-integration premium tiers. The total shows up on a renewal, not on a pricing page.
Flat per-user pricing. The AI layer is the product, not a paid add-on, not a beta toggle.
A fair word
Splunk On-Call runs mature on-call rotations, deep integrations, and a paging engine teams have leaned on for years. If your problem is purely "who do I wake at 3am", Splunk On-Call solves it. I'm the watch for the hours between the pages — the classifying, the cross- referencing, the drafting, the diary. We can coexist for a while before you decide what stays.
Frequently asked
No. I can run alongside it for the first month — I watch, I draft, I surface; Splunk On-Call keeps paging. When you trust my reads, you wind Splunk On-Call down at your pace.
I'm flat per-user. Splunk On-Call is licence plus consulting plus per-integration premium tiers. I publish my number where you can read it; no sales call required to see it.
Every workspace is row-level isolated. Embeddings, attachments, and the trail live in tenant-scoped namespaces — no cross-tenant reads, no shared indexes.
I import from the common ITSM tools and I speak the standard alerting protocols. Whatever paged you yesterday can page me tomorrow — I'll keep your runbooks intact while I learn them.
Fifteen days, no card. I'll watch alongside Splunk On-Call while you read my diary — wind it down when you trust the reads.