Incidents
Open, yours and resolved, with take, reassign, snooze, resolve and declare fix.
Argunis/Operations/Incidents and CMDB
Every alert, to the right person.
Argunis turns alerts into incidents with their probable cause, routes them to the right resolver group, escalates if nobody answers and records everything in the inventory, reports and audit log.
Core · incidents
Open7
Untaken2
Resolved today23
Mean time14 min
INC-2047 · api-paymentsPlatform · Carla Rojastaken
INC-2046 · switch-dcNetwork · probable cause6 affected
INC-2045 · db-salesDBA · on-callescalating
INC-2041 · web-storeresolved by Argunisclosed
Groups, on-call and escalation
Each resolver group has its leads, weekly on-call and escalation. The first alert goes to whoever is on call; if nobody takes the incident, Argunis notifies the next person after the minutes you define.
- Resolver groups with leads
- Weekly on-call with substitutes
- Escalation by minutes
- Simulator of who gets it
Escalation · DBA
Pablo Díazon call this weeknotified 03:12
Andrea Muñozleadnotified 03:22
- 1Alert
- 2On-call (0 min)
- 3Lead (10 min)
- 4Management (25 min)
- 5Taken
Alerts wherever you are, with actions
Email, browser push, Microsoft Teams, Slack, Telegram, signed webhook or voice. From the alert itself you acknowledge, snooze or declare the fix, without opening the platform.
- Email, push, Teams, Slack and Telegram
- Signed webhook for your systems
- Acknowledge, snooze or fix from the alert
- Quiet hours per person
Channels · INC-2045
Acknowledgefrom Telegram03:24
Snooze 30 minfrom Teams03:31
Declare fixfrom email04:02
EmailPushMicrosoft TeamsSlackTelegramWebhookVoice
Probable cause, not a hundred symptoms
Alarm policies decide what opens an incident and what stays an event. With the inventory’s dependencies, Argunis groups outages that go together and points to the cause and the affected items.
- Alarm policies with a simulator
- Correlation by dependencies
- Learned relationships to accept
- Live CMDB per inventory group
Correlation · 03:121 incident · 6 alerts
switch-dcprobable causedown
srv-erp-01affectedno response
db-salesaffectedno response
api-paymentsaffected5xx errors
Everything the Core includes
Events
Everything detected in 7 days and which incident each event was correlated to.
Resolver groups
Teams with leads, weekly on-call and escalation.
Alert rules
Which group gets each alert, with a simulator and channels.
Alarm policies
Thresholds, sustained times, auto-closing and correlation by dependencies.
Inventory and CMDB
Groups with criticality and owner, and the live CMDB with its relationships.
Sites
Where each machine is, on the dashboard map.
Reports
PDF with your company logo, Excel and CSV, as templates or scheduled by email.
Scheduled maintenance and business hours
Windows without checks or alerts, and working days and hours per service.
Dashboards and NOCFrequently asked questions
Does an incident close on its own?
Outage incidents close when the service is back; event incidents after the minutes without new events you define. The rest stay open until someone closes them.
Can I test who will get an alert?
Yes. The simulator shows which group receives it, by which rule, who is on call and through which channels each person gets it.
Do reports carry my logo?
Yes. They are generated as PDF with your company logo, as Excel and CSV, and can be scheduled by email or requested from the assistant.
See the failure before your customers do.
We show you Argunis on your own operations and answer your questions in one call.