Core
Incidents, events, inventory, sites, resolver groups, notification rules, alarm policies, scheduled work, business hours, and reports, the center of operations in ARGUNIS.
Core brings together what happens when something fails: ARGUNIS receives the events from everything you monitor, groups them into incidents, decides which team gets each one, and escalates it if nobody handles it. This is also where you organize your inventory into groups and place your hosts at sites.
You'll find it in the side menu, under Core. Each menu option has its own section in this guide.
Menu | What it's for |
|---|---|
Core → Incidents | View, acknowledge, take, snooze, and close incidents |
Core → Events | Review everything the platform detected in the last 7 days |
Core → Inventory | Organize services and hosts into groups with their own dashboard |
Core → Proposed relationships | Accept or dismiss dependencies that ARGUNIS learned |
Core → Sites | Edit, rename, or delete the locations of your hosts |
Core → Resolver groups | Define the teams that receive notifications, their escalation, and their on-call |
Core → Notification rules | Decide which group each alert goes to and connect Teams, Slack, Telegram, or webhooks |
Core → Alarm policies | Decide whether an alarm opens an incident, stays as an event only, or is ignored |
Core → Scheduled work | Schedule periods without checks or alerts (maintenance) that don't count toward availability |
Core → Business hours | Define the working days and hours of things that are shut down on purpose (QA, development) |
Core → Reports | Generate reports with charts and KPIs in PDF, Excel, and CSV, save them as templates, and schedule them by email |
Every role sees at least Core, Incidents and events, and Dashboards. What you can change depends on your role: with View you can only browse, with Operate you can also acknowledge and snooze, and with Administer you can also create and change settings.