Hosting and maintenance / monitoring uptime website
Uptime monitoring
Issues of availability reported through agreed evidence and notifications, with a clear investigation and intervention process.
Followed availability with clear responsibilities to the incident
We determine which services and operations are to be pursued for the projects administered at SIDECUBE. Alerts signal problems; investigation and intervention have distinct conditions agreed in the agreement.
- Relevant evidenceWe choose the addresses and services checked. A successful HTTP response does not confirm the operation of a form or order on its own.
- Threes and notificationsWe set up alerts for the events being watched and determine the recipients and the escalation route.
- Investigation and interventionWe correlate the alert with the status of the application and infrastructure. Remediation shall follow the responsibilities and conditions of support assumed.
- Useful historyWe keep the information necessary to understand the incidents and prioritise the stabilisation measures.
What the service can include
Monitoring does not automatically remedy all incidents. The frequency of samples, the support intervals and the intervention times shall be those in the agreement, without implicitly guaranteed availability.
01Followed service inventory
02Availability samples
03Threes and alerts
04Ascending route
05Incident history
Alerts shall be tested before necessary
- We confirm the services and operations pursued.
- We're checking notifications through an appropriate test scenario.
- We determine the responsible and escalation steps.
- We document the limits of the checks and the conditions for intervention.
Recommended pages
Pages related to this type of service: technologies, fields of activity, guides and complementary services.
Frequently Asked Questions
Before we begin the project
Choice, stages and support for up-to-date monitoring.
01 / Service
Purpose and conditions
Does monitoring automatically remedy incidents?
No. The detection and notification shall be distinct from investigation and remedial. Interventions shall be established by the conditions for support.
A successful HTTP response confirms all website functions?
No. Forms, controls or authentication may require separate verification scenarios defined by their importance.
02 / Preparation
take-over and access
How can an existing project be taken over?
We evaluate the platform, data and integration, then clarify compatibility, remedies and migration to SIDECUBE infrastructure. An initial audit can be delivered prior to the takeover decision; the full recurrent administration is done in our environment.
What information is needed for the estimation?
Platform and services used, data volume, important operations and known problems. We determine the works, access and responsibilities prior to intervention; passwords are not sent via public forms.
03 / Verification
Validation and limits
How do you check the result?
We confirm the services and operations pursued. We're checking notifications through an appropriate test scenario. We determine the responsible and escalation steps. We document the limits of the checks and the conditions for intervention.
What conditions and costs need to be clarified?
Monitoring does not automatically remedy all incidents. The frequency of samples, the support intervals and the intervention times shall be those in the agreement, without implicitly guaranteed availability.