Service management built into monitoring
Turn alarms into incidents with owners, measure SLAs and error budgets, map the business services that depend on your systems, and see the blast radius of any failure.
From alarm to incident to service level
Alarms say something is wrong. IT service management says who is working on it, how important it is to the business, and whether you are meeting what you promised. Rapitt keeps the three in one place, so an alarm, the incident it became and the SLA it affects are one click apart.
The service management toolkit
ITIL-style, but practical.
Incidents
Opened from alarms by rule or by hand. Priority from impact and urgency, with business-service impact raising it. Teams, assignment, tasks, a full timeline, reopening when a problem returns, and MTTA and MTTR per priority.
Teams and ownership
Teams own incidents; a person is told on the channels they chose. A My work page lists what is yours and what is waiting.
SLAs and reports
Objectives over hosts, services, API checks and IIS sites, with business hours, maintenance windows, live attainment, error budget and burn rate. Scheduled weekly or monthly PDF reports, by SLA or by client.
Business services
Declare what the business depends on. See each service’s health, the blast radius of any failure and the services that would go down or degrade.
Business KPIs
Numbers from your own databases and APIs, tracked on a schedule against warning and critical thresholds, with history. Failed reads are gaps, never zeros.
Scorecards and DORA
Scorecards over production-readiness, security and incident response. Deployment frequency, lead time, change failure rate and time to restore from deployment events your pipeline reports.
Dashboards you build
An arrangeable overview, and a dashboard builder with widgets over the data feed. Sharing shares the layout, never the data: each viewer sees only what they are allowed to.
Renewals
Domains, certificates, licences and subscriptions with reminders on every channel, sent once and never repeated for the same date.
Impact, not just severity
A disk at 90% on a test box and a disk at 90% under a payment service are different incidents. Rapitt raises an incident’s priority when the host serves a business service that would go down without it, and says why in the incident.
Every rule is printed where it applies: the service health rule on the services page, the SLA formula on every report.
Service management questions
Does Rapitt connect to my existing ticketing tool?
Incidents are managed inside Rapitt. Everything is available through the API and webhooks if you want to feed another system. A named connector to a specific ticketing product is not built yet.
How is SLA attainment calculated?
Up time divided by up plus down time. An hour with no usable reading counts as unknown, not as up or down, and coverage is reported. The formula is printed on the page and in every report.
Is the business-service map discovered?
No. You declare which servers, devices, domains, API checks, tunnels and SLAs each service depends on, and how. The health rule is printed, so you can check why a service shows as down.
Can business KPIs read from my own systems?
Yes. A KPI reads one number from a database you register (a single SELECT, run read-only) or from a path in an API response, on a schedule, against thresholds you set.
See it on your own systems
A walkthrough runs on your own estate. Reserve your workspace address while you book.
