Nobody has to watch the screen.
Every alert lands in one place. What matters becomes an incident and pages whoever is on call — on their phone, their computer and the panel. If nobody acknowledges, nuvem.team calls the next person.
Incidents · nuvem.team
Too many alerts, too few owners.
Monitoring is work enough. Handling what monitoring finds — at three in the morning, with the client waiting for news — is another story.
The group nobody reads
Alerts in WhatsApp or Teams, all with the same weight and none with an owner.
Every alert lands in one place, and every incident has an assignee.
When everything screams
If everything is urgent, nothing is. The team learns to ignore it.
Severity comes in words — critical, high, medium, info — and only critical and high wake anyone up.
Someone watching the screen
In the middle of the night, nobody is looking at the dashboard.
The coverage calendar knows who answers at each hour, and nuvem.team pages that person.
The alert that rang and nobody saw
The phone was on silent, and the problem waited until morning.
Paging escalates step by step until someone acknowledges. A schedule with nobody on it and a phone that isn't ready to ring show up beforehand.
“So, how is it going?”
Those affected call to find out, and whoever is fixing it stops to answer.
Client and manager follow the same conversation, with the next update scheduled.
The incident that comes back
Nobody remembers what was done last time.
What repeats becomes a Problem, with the known error and workaround at hand.
Monitoring set up in a rush
Too many alerts where it doesn't matter, too few where it does.
With assisted onboarding, Nuvem.online designs the right monitoring and rules with you.
From alert to resolved, without switching places.
Every source follows the same path. Your monitoring stays where it is: nuvem.team keeps the alerts, not your metrics, logs or traces.
Event
The source sends what it saw. Every event is stored before the response.
Alert
Repeats become a single alert, with severity in words.
Incident
Critical and high open an incident on their own. Medium and info stay in the alert stream until a rule promotes them.
Paging
Whoever covers now is called in the app. No answer, it escalates.
Resolution
Acknowledge, talk with the client in the room and resolve. What repeats becomes a Problem.
- Alertmanager
- Grafana
- Datadog
- Webhook
- Heartbeat
- HTTP monitor
In your pocket, on the desk and on the wall. Nowhere else.
Paging goes only through the official apps and the web application. No email, no SMS, no group chat: that's how you know whether it arrived, to whom and when.
Acknowledge without unlocking
On iPhone and Android, the notification's Acknowledge works with the phone locked.
Breaks through Do Not Disturb
The phone keeps ringing until someone acknowledges, and stops on its own when paging ends.
On top of every window
On Mac and Windows, a panel stays on top, with looping sound, Acknowledge and Open.
NOC dashboard for the wall
Readable from three meters away, with sound and the same notice on screen.
Ready to ring
The app says, in words, which permission is missing — before the shift starts.
- macOS
- Windows
- Web
- iOS · coming soon
- Android · coming soon
The client in the room, not on the phone.
Those affected see the same incident as the team: what happened, what is being done and when the next update comes. The conversation is public by default — there is no hidden note.
- The same view as the team, limited to their own organization.
- Clear roles: owner, responder and viewer.
- A living summary for whoever joins halfway through.
Checkout latency above 2 s
- 03:14 · Incident opened by Alertmanager, critical severity
- 03:19 · Not acknowledged in 5 min: step 2 paged
- MarinaResponder · 03:20
Acknowledged. Looking at the payment gateway now.
- CarlaViewer · 03:21
Thanks. We have a campaign at 8 AM — can you prioritize it?
- MarinaResponder · 03:23
Cause still unknown; next update at 03:40.
Next update at 03:40
Nothing fails silently.
Every route has a coverage calendar: which team answers at each hour, the way it works. When someone is missing, nuvem.team shows it before it becomes a problem.
Coverage calendar
Checkout route · this week- MonNOCPlatform
- TueNOCPlatform
- WedNOCPlatform
- ThuNOCPlatform
- FriNOCPlatform
- SatGapPlatform · rotation
- SunPlatform · rotationNOC
Gap on Saturday, from 2 AM to 6 AM. No team covers the Checkout route in that period.
Escalation policy
Platform Team- 1Designated responderPaged right away, on the phone and on the computer.
- 2Next on the scheduleIf nobody acknowledges within 5 minutes.
- 3The whole teamIf nobody acknowledges within 10 minutes.
- Policy exhaustedShows up on the NOC dashboard for coordination. Nothing is left without an owner.
The way the team works:
- On-call schedule
- Rotation
- Balanced load
- Everyone at once
Coverage gap
A period with no team, or with nobody who can be paged.
On call without a ready phone
Someone on call without a verified device to ring.
Policy exhausted
Every step paged and nobody acknowledged.
Stopped timer
If the escalation clock stops, that shows up too.
Run it yourself. Or with us by your side.
nuvem.team is the same in all three cases. What changes is how much of the operation Nuvem.online does with you.
On your own
Your team sets up and runs on-call in nuvem.team.
- Who answers on-call
- Your team
- Who designs the monitoring
- Your team
- How to sign up
- With Nuvem.online, with a free plan to start
With assisted onboarding
Nuvem.online's consulting team designs the monitoring, rules, schedule and escalation policy with you. Then your team runs it.
- Who answers on-call
- Your team
- Who designs the monitoring
- You and Nuvem.online, with our methodology and open tools, on your infrastructure
- How to sign up
- With Nuvem.online, by proposal
With NOC as a service
Nuvem.online's NOC team joins your on-call: as backup for part of the coverage or for the whole operation.
- Who answers on-call
- Nuvem.online's NOC team, alone or with yours
- Who designs the monitoring
- Nuvem.online, with you
- How to sign up
- With Nuvem.online, by proposal
Frequently asked questions
Do I need to replace my monitoring tool?
No. nuvem.team receives alerts from Alertmanager, Grafana, Datadog, any webhook, heartbeats and the HTTP monitor. Metrics, logs and traces stay on your infrastructure.
Does nuvem.team notify by email, SMS or WhatsApp?
No. Paging goes only through the official apps and the web application. That's how you know whether it arrived, to whom and when — and keep insisting until someone acknowledges.
What happens if nobody acknowledges?
Paging escalates, as the escalation policy says: the next person on the schedule, then the whole team. If the policy is exhausted, that shows up on the NOC dashboard.
Does the client see everything?
They see the same as the team, limited to their own organization. The incident conversation is public by default, and each person joins with a role: owner, responder or viewer.
Is nuvem.team a service desk?
No. It handles alerts, on-call and incidents. Requests and demands stay in your support channel.
Where is my data stored?
In Brazil, in the São Paulo region. The details, under the LGPD, are in the privacy policy.
Can I hire your operation?
Yes. With NOC as a service, Nuvem.online's team joins your on-call — for part of the coverage or the whole operation. You contract it with Nuvem.online, by proposal.
The next alert already has an owner.
Talk with us about your team's on-call and your operation.