The ticket that knows the rack.
Monitoring, incidents, changes and runbooks, with the rack, the customer and the SLA already attached. The NOC works one queue with facilities and finance, not three.
Vitana · IT OpsFrom signal to signed-off.
Six moves. Every alert lands on an object the rest of the business already knows.
VitanaOperations / IncidentsDOne incident. Every link.
INC-20417 · Rack 2B-14 · Northwind
01
Monitor what matters.
Infrastructure and environmental signals in one view, mapped to racks, customers and contracts. Noise is grouped by the asset it came from.
- Infra + environment
- Grouped by asset
| Signal | Asset | Customer | Sev | State |
|---|---|---|---|---|
| Inlet temperature | Rack 2B-14 | Northwind | P1 | open 00:38 |
| Link flap | Sw-2C-agg-1 | Shared | P3 | grouped · 14 events |
| UPS B on battery | UPS B | Hall 2 | P1 | cleared 00:02 |
| Disk 91% | nms-02 | Internal | P4 | ack |
02
Alert with context.
An alert carries the rack, the power path, the customer and the SLA clock from the first second. On-call sees who is affected before they pick up.
- SLA clock
- Affected customers
- On-call
03
Incident, shared.
One incident in the shared queue. The NOC, facilities and the account team see the same item with the fields their role needs; the customer sees their slice.
- Shared queue
- Roles
- Customer view
04
Change, with a window.
Planned and emergency changes with approvals, windows, the assets they touch and the incidents they close. Nothing is edited without a who and a when.
- Approvals
- Windows
- Assets touched
| Change | Touches | Window | Approval | State |
|---|---|---|---|---|
| CHG-5531 | CRAH C3 | Thu 09:30 | M. Keller | Done |
| CHG-5540 | Sw-2C-agg-1 · firmware | Sat 01:00 | J. Park | Approved |
| CHG-5544 | PDU 2B-07 breaker | Thu 09:30 | pending | Awaiting |
| CHG-5547 | Rack 2C-19..24 install | Fri 10:00 | L. Moreau | Approved |
05
Runbooks that run.
Runbooks attached to the asset and the alert type, with the steps, the owners and the checks. Half of them can be executed, not just read.
- Attached to asset
- Executable steps
06
Report, and prove the SLA.
Availability, MTTR and breaches per customer and contract, computed from the same incidents that produced the credits. The report and the invoice agree.
- Availability
- MTTR
- Credits
What makes Vitana different.
It is IT operations on the same record as the floor and the contract.
01
Context from the first second
Alerts arrive with the rack, the power path, the customer and the SLA clock already attached.
- Affected customersKnown before the call.
- SLA clockStarts on the alert, not the ticket.
- GroupingBy asset, not by string match.
02
One queue for three teams
Incidents and changes live in DIL. Facilities, the NOC and finance work the same item.
- RolesThe right fields per team.
- Customer sliceTheir tickets, their changes.
- CreditsQueued to Ayana on resolution.
03
Nothing without a who and a when
Approvals, windows and overrides are kept. Audit packs and SLA reports come from the same events.
- AttributedEvery edit, every override.
- RunbooksExecutable, with checks.
- ReportsAgree with the invoice.
Running ServiceNow for the NOC and WhatsApp for facilities? Bring your last P1 and we will show it as one incident on the record.
Speak to our experts →Works with the stack you already run.
Keep your monitoring and your ITSM. Vitana reads alerts, writes incidents back, and keeps the chain in DIL.
ITSM
Two-way incidents and changes.
ServiceNow
Jira Service Management
FreshserviceBMC HelixsoonManageEnginesoonMonitoring
Alerts and metrics in.
Zabbix
Prometheus
Grafana
DatadogPRTGSolarWindssoon
NagiosOn-call & chat
Where people are paged and talk.
PagerDuty
Opsgenie
SlackMicrosoft Teams
WhatsApp BusinesssoonNetwork & identity
Devices and people.
CiscoArista
Juniper
OktaMicrosoft Entra ID
Design partner places are open
Bring your last P1. See it as one incident.
Design partner places are open for operators running 2 MW and up.