For the complete documentation index, see llms.txt. This page is also available as Markdown.

Custom check

Description

A monitoring check is an automated probe that periodically sends an HTTP request to one of your application URLs β€” exactly as a real user would β€” and verifies that the response is correct.

πŸ’‘ Think of it as a dedicated robot that tests your application every few minutes, 24/7, and alerts you immediately if something goes wrong β€” before your users notice.

Custom Check is available in ITCare on any URL exposed via an Elastic Secured Endpoint (Load Balancer). cegedim.cloud operates and maintains the monitoring infrastructure. No agent or additional component is required on your application side.

Two check types are available:

  • Custom Check β€” internal probe, included with the Load Balancer

  • External Custom Check β€” external probes from the public internet, available as a paid option

Custom Check
External Custom Check

Source

Internal (within cegedim.cloud)

External (public internet)

Locations

1 internal probe

πŸ”΅ Marseille (Azure) + 🟠 Paris (AWS)

Frequency

Every ~10 min

Every 5 min

Result

Global status

Per-location detailed output

24x7 Monitoring

βœ… Option

βœ… Option

Self-service

βœ…

βœ…

For more information, please visit the Custom Check - Get started page.

Support Level

Both check types share the same support level management in ITCare. At creation, a check has no cegedim.cloud support. The support level can be adjusted on request through your SDM:

Level
Coverage

None

Default at creation

Business hours

On request β€” SDM

24x7

On request β€” SDM

Billing

Custom Check

Included in the Elastic Secured Endpoint (Load Balancer) pricing.

External Custom Check

Paid option β€” billed per batch of 1,000 requests (2 requests every 5 minutes).

  • Billing starts from the first check executed.

  • Cost estimates available through your SDM.

Technical Details

Features

This section lists the features available to the customer, as well as how to request or execute them:

Self-service

The customer can perform the action independently via ITCare.

On request

The customer must open a support ticket.

Feature
Self-service
On request
Comments

Create a Custom Check

βœ…

ITCare β†’ Resources β†’ URLs β†’ Actions β†’ Add Custom Check

Create an External Custom Check

βœ…

Same interface

Delete a check

βœ…

Edit check parameters

βœ…

Some attributes cannot be modified after creation β€” if the update is not possible, delete and recreate the check.

Adjust support level

βœ…

Contact your SDM

Check Naming

Checks created in ITCare follow this naming convention: APPS_CHECK_URL_

This name is used as the alert identifier in ITCare monitoring views.

Status & Results

Custom Check configuration allows you to define triggering thresholds based on the HTTP response code and/or the response body content of your application.

For External Custom Checks, results are available per location. If one location fails while the other succeeds, this indicates a regional network issue rather than an application failure.

A Critical status appears in ITCare within 9 minutes maximum (5-min check cycle + polling + retry).

Last updated