Cloudlab

Solution 05 / Managed & supervised

Coordinate accommodation and interventions.

Cloudlab carries the data center component. System monitoring and outsourcing are organized with Agedis, and application developments with Dtouch. You keep a clear understanding of responsibilities.

Your offer in plain language

What we define
before your estimate.

For what use?
Hosted services to monitor, maintain and track.
What perimeter?
Equipment monitored, indicators, recipients of alerts and actions supported.
Where is the data?
Accommodation is offered in France. The reception environments and speakers are specified for your project.
What protection?
Distinguish between alert, availability of assistance and response times.
What assistance?
Contact channels, support periods, maintenance and responsibilities are described in the successful offer.
How to change next?
Access, export formats, volumes and restitution conditions must be planned before commitment.

The proposal distinguishes the hosting environment, system administration, application maintenance and backups. The migration specifies the accesses to be recovered, the checks and the cutover schedule.

Preparing my project →

Capacity, prices and commitments are detailed in your proposal, depending on your applications, volumes and operating methods chosen.

SupervisionMaintenanceDiagnosis
Park tracking view with demonstration data
Real application capture with demo data. It illustrates the monitoring of the fleet, without presenting live supervision.
01

Observe the right signals

Service availability, disk space, resource consumption and error logs: controls are chosen for your environment. An alert must enable understanding and action.

02

Intervene methodically

With Agedis for systems, we start from the real state: logs, load, storage, database and configuration. Changes are prepared, saved and controlled to avoid blind interventions.

03

Make the service readable

The scope of support, intervention periods, escalations and exclusions are specified in the proposal. We distinguish between system maintenance, application support and developments.

Preparing your project

A clear breakdown for monitoring services.

The operation of a hosted service depends on several perimeters. The data center environment, servers, software and user access must be able to be monitored together. The project therefore begins with a clear breakdown: who hosts the infrastructure, who administers the systems and who knows the constraints of the application? This organization facilitates exchanges during an evolution or an incident.

Cloudlab carries the data center component. Agedis supports servers and IT; Dtouch is involved in business developments and integrations. Support modalities, contacts and interventions are defined within the agreed scope. A maintenance or migration must also provide for checks of the services after the operation and the monitoring of any open points.

Identify responsibilities

Distinguish between hosting, systems and applications, then define the contacts and information to transmit according to the subject encountered.

Preparing for operations

Describe planned maintenance, affected dependencies, and users to notify. The conditions of intervention must take the activity into account.

Follow the return to service

Check the intended uses and share remaining points with the right interlocutors. The technical inspection is supplemented by the return of the persons who use the service.

Preparation questions

Decisions to be made together.

Who to contact in case of difficulty?

Contact persons and reporting procedures are specified for the project. Qualification of the subject makes it possible to direct monitoring towards the data center, systems or application.

Are the support conditions the same for all projects?

They depend on the agreed scope. Schedules, intervention methods and possible commitments must be specified in the proposal and contractual documents.

Understand and prepare

Make an alert the start of a useful diagnosis.

Supervision provides value when it allows a gap to be recognized and the right stakeholder to be mobilized. We connect technical measures, operating context and functions used by the company.

Choose what is worth observing

A service that responds, a base that fills and a processing that no longer performs produce different signals. The study identifies the important services, dependencies and symptoms that should trigger attention. Thresholds are adapted to the observed activity. A measurement of memory or processor makes sense with the expected time, processing and application behavior. The probes and notification procedures shall be defined according to the monitoring scope.

Qualify before changing

The diagnostic gathers the time of the problem, affected users, requested action and recent changes. Agedis scans systems, resources and useful logs; Cloudlab processes elements related to the hosting base. When the service can be reached but the business action fails, the study can continue with Dtouch or the publisher. This sharing allows us to examine the problem as a whole and justify the planned intervention.

Preparing for recurring operations

An update must take into account compatibility, backups, ongoing tasks and the availability of those who will verify the result. The operation is planned with its prerequisites and points of return. After intervention, the checks shall be carried out on the services concerned and on the uses chosen. Observations before and after change provide support for follow-up, particularly if another problem arises or if a change is to be continued by the publisher.

A service perimeter that can be read again

The support document specifies the machines and applications monitored, the schedules, the reporting methods and the escalation contacts. It distinguishes between planned operations, changes to the estimate and the responsibilities that remain with the client or a partner. This reading must also indicate what happens when a problem comes from another perimeter: what information to transmit, to whom and with what follow-up. Possible commitments are defined in the proposal.

A worker's hands connect cords in a white patch panel rack.
Intervention archives, August 2020: a gesture of connection and monitoring of connections.

Complementary skills

A follow-up that connects the right stakeholders.

Monitoring a service can lead to examining its connections and environment, in addition to logs and technical metrics. Observations are shared with the specialist in the area concerned.

The hosting base, the system and the application must be able to be examined together. Cloudlab, Agedis and Dtouch each bring their skills according to the needs of the project.

Our method

From the first exchange
to the care.

01

Understand

Your uses, existing, constraints and priorities.

02

Prepare

The perimeter, access, recovery and verifications.

03

Accompany

Commissioning and monitoring agreed with you.

Supervision · Monitoring and diagnosis

Understand the status of your hosting.

Availability, capacity, services and backups: the same screen helps identify what is working, what is drifting and what requires verification.

Understanding our outsourcing
Écran de supervision : état des services, alertes de capacité et de sauvegarde, puis incident résolu. Données de démonstration.
Presentation inspired by our supervision screen. Demonstration data; no actual customer or equipment.Enlarge screen
  1. 01 · Read the indicators

    Distinguish between the services available, the thresholds exceeded and the treatments to be verified.

  2. 02 · Qualify the alert

    Check the cause, impact and priorities before choosing the intervention.

  3. 03 · Check the resolution

    Confirm the return to normal and keep track of what has been done.

The equipment monitored, thresholds, notifications and intervention methods are defined with you according to your environment.

Complementary expertise, the same high standards.