Alerts that explain themselves
Each alert group states in words why its alerts belong together, so responders trust it.
Know what you run, see what is failing, and fix it with confirmation.
IT operations management keeps an accurate map of your services and items, discovers them from cloud, identity, devices and your own network, and turns monitoring noise into a few explained alert groups. Runbooks fix problems safely: anything that changes a system waits for a person.
Each alert group states in words why its alerts belong together, so responders trust it.
Mapping proposes members with evidence; a person confirms, so the map stays honest.
Outbound only, signed, read-only and limited to your ranges.
Destructive steps need a second person; nothing runs until two people switch runbooks on.
See what breaks, and which customers feel it, before you change an item.
Search or filter. Planned items are labelled; everything else is available now.
A trustworthy record of what the company runs and how it fits together.
13 featuresCloud accounts, directories and device management feed the database on a schedule.
12 featuresA small program inside your network finds what the cloud feeds cannot see.
9 featuresKnow which items make up each service and how much of it was lost.
10 featuresTake in alerts from monitoring tools and turn the flood into a short list of explained groups.
15 featuresAutomate fixes safely, with people confirming anything that changes a system.
9 featuresAlerts reach the right person through the one paging path.
2 featuresIt prepares the work. A person confirms it.
The same four building blocks, specific to IT Operations Management.
Rule promotion, risky IT actions and runbook versions go through the shared workflow module, with the requester or author excluded from approving.
Configuration health and alert reports on the shared reporting module, respecting sensitive items.
Datasets
Dashboards
Configuration items are readable through the API and written through the data integration feed; monitoring tools post signed alerts or are pulled.
/v1 itom_cis, itom_ci_rels (write through the itom.cis integration feed)
Events
Connectors
Configuration item import by CSV is available; dedicated packs for other configuration databases are planned.
Not a phone-first hub. On-call acknowledgement on the phone app is planned.
Impact for tickets and changes; alerts open incidents and page on-call; recent changes explain alerts
Every physical asset is one configuration item; software installs arrive from device sources
Identity directory accounts and device holders
Customer contracts mapped to services
No. Discovery and collector probes are read-only. IT actions are separate, confirm-first and approved by a different person when risky.
A machine in your network that can call AI over HTTPS; it opens no inbound port.
No. Items are retired, never deleted, and merging is a person's decision.
No. Runbooks are off until an administrator and a second person switch them on.
By dependency, service, tag or recent change, with the reason shown on every group.
Not yet; this is planned and depends on a partner feed.
Only people allowed to change or approve configuration.