Monitoring & Management
Monitoring & Alerts
VM charts, with alerts to Slack or your webhook.
Managed Support
Keep your platforms under continuous watch, fix issues before they grow, and give your team its time back
Nesnet watches your environments on the Nesnet cloud and the platforms Nesnet has installed for you: a crossed threshold becomes an alert, an alert becomes a response. Patches, capacity and upgrades run on a plan, and the work done and the capacity trend are reported in writing every month.
Why now
Alerts pile up in an inbox
Monitoring is in place, but alerts sit in a mailbox. Problems are usually noticed when a user calls.
Patches keep waiting
There is never a good maintenance window for security patches, and every postponed month adds risk.
Full disks are a surprise
Nobody watches the capacity trend, so a disk or memory shortage only shows up once the application slows down.
Firefighting crowds out projects
The infrastructure team’s days go to routine work and small incidents, and new projects keep slipping to next quarter.
What changes
| Today | With Nesnet |
|---|---|
| Problems are noticed when a user calls. | A crossed threshold raises an alert and the Nesnet team starts working on it; most issues are fixed before users notice. |
| Patches are postponed and pile up. | Security patches are applied on schedule, in planned maintenance windows. |
| Capacity problems show up when the disk is full. | The capacity trend is in the monthly report, so growth is planned ahead. |
| Nobody is sure who does what during an incident. | Which components are watched and how incidents are handled are set out in the contract. |
| The work done isn’t recorded anywhere. | Every month’s interventions and changes reach you in a written report. |
From today to live: how it works
- 1
Scoping call
The platforms and components to watch, maintenance windows and contacts are agreed together.
- 2
Connecting the platform to monitoring
Your Nesnet cloud environment, or the platform Nesnet installed, is connected to monitoring together with its installation documents.
- 3
Monitoring and alerting
Thresholds are set per component, and who receives which alert, and how, is written down.
- 4
Ongoing operations
Alerts are handled, patches go in during planned windows and every change is recorded.
- 5
Monthly review
The month’s interventions, the capacity trend and recommendations are reviewed together, and the scope is updated when needed.
What you get
Continuous monitoring
Platform components are watched continuously; a crossed threshold becomes an alert, an alert becomes a response.
Written scope of service
Which components are watched and how an incident is handled are set out in the contract.
Version and patch tracking
Security patches are applied in planned maintenance windows.
Monthly report
Interventions, changes and the capacity trend for the month, in writing.
Capacity planning
Usage trends are tracked, so disk, memory or CPU shortages are flagged early and growth is planned.
Change log
Every change on the platform is recorded with who made it, when and why.
Why Nesnet
Alerts and interventions follow the scope written into your contract, and Nesnet’s support team answers your questions in Turkish or English.
Example scenarios
A two-person IT team
Situation
An organization’s two-person IT team handles both user support and its servers on the Nesnet cloud, and patches have been waiting for months.
Outcome
Server and platform monitoring and the patch calendar move to Nesnet; the team gets back to users and applications.
A platform in the customer’s own data center
Situation
Nesnet has installed a private cloud platform in the organization’s data center, but there aren’t enough specialists to run it day to day.
Outcome
Nesnet watches the platform remotely and handles upgrades and incidents.
A growing e-commerce stack
Situation
Disk and memory fill up unexpectedly during campaign periods.
Outcome
The capacity trend shows up in the monthly report, and extra resources are planned before the next campaign.
Who does what
| Nesnet | You |
|---|---|
| Watching components and handling alerts | Approving maintenance windows |
| Responding to platform incidents | Application-level work and application owners |
| Security patches and upgrade tracking | Business priorities |
| Capacity tracking and the monthly report | Approving major changes |
| Change log | Authorized contacts |
Related products
Containers & Developers
Managed Kubernetes
Ready Kubernetes clusters with network, load balancer, registry.
Compute
Private Cloud
Your own quota, your own gateway and your own identity provider.
Questions to ask before you decide
- Which platforms are covered?
- Your environments on the Nesnet cloud and platforms Nesnet has installed in your data center. Platforms Nesnet did not install are not taken on, and the scope is written into the contract component by component.
- Does our own team keep access to the platform?
- Yes. Permissions stay with you; the Nesnet team accesses the platform only for the work defined in the contract, and every change it makes is logged.
- How will we hear about an incident?
- Who receives alerts and incident notices, and through which channel, is agreed during scoping and written into the contract.
- Do you look after our applications too?
- The scope is the platform layer: servers, storage, networking and platform components. Application-level work is discussed separately and handled when it is written into the scope.
- What happens when the contract ends?
- Term and exit conditions are set out in the contract. When the service ends, documentation and access are handed over to your team in full.
- How is it priced?
- Monthly, by the size of the platforms watched and the work in scope. You receive a written quote after the scoping call.
Questions about these products
Monitoring & Alerts
- Will a short load spike flood me with alerts at midnight?
- No, it won't. With the duration condition, an alert fires only when the breach lasts for the time you set, and a resolved entry is written when it ends. Even if the extension restarts, a firing alert isn't notified twice.
- Can I get alerts by email or SMS?
- Today the notification channels are webhook and Slack; email and SMS aren't supported directly. You can turn alerts into email or SMS by connecting the webhook to your own notification system.
Hand over routine operations in one scoping call
We agree the platforms to watch, the maintenance windows and the contacts, then send a written scope of service and quote.