Monitoring

Monitoring shows how your services are doing and tells you when something breaks — through metrics, alerts, channels, and log drains.

Metrics#

A service’s Metrics tab charts live CPU (cores), memory, and network (in/out) for its containers. Choose a window of 15, 30, 60, or 180 minutes; it refreshes about every 15 seconds.

Alerts#

In settings, admins can add alert rules that fire when a metric crosses a threshold:

Metric

CPU (cores), Memory (MB), or Service down.

Condition

Greater than or Less than a threshold you set.

Scope

A single service, or all services.

Notification channels#

Route events to an Email address or a Webhook URL. Subscribe to specific events — deploy succeeded, deploy failed, member joined, quota warning, SSL expiring — or leave them all unchecked to receive everything. Use “Send test” to verify delivery, and set a signing secret to add an X-Gheima-Signature HMAC header.

Log drains#

Add a log drain to forward deployment logs to an external HTTP endpoint (for example your logging provider). Logs are POSTed as they finish, optionally signed.

History & delivery#

• Each alert keeps a history of its state changes (OK ⇄ Firing).
• Channels record every delivery with its HTTP status; failed ones can be retried.
• The metrics window can be 5–360 minutes (the tab offers 15/30/60/180).
• Signed deliveries include an X-Gheima-Signature HMAC header you can verify.