Operational visibility

Capacity and service health with the source and freshness attached.

Corvus Cloud combines bounded guest measurements, provider observations and independent route probes. Missing or conflicting evidence stays visibly unknown instead of becoming a reassuring but false green badge.

01

Understand resource pressure

CPU, available memory, filesystem bytes and inodes, network activity, load and Odoo environment checks are sampled through a fixed outbound-only node contract. The collector cannot receive commands or inspect arbitrary paths and processes.

  • Visible sample freshness and gaps
  • Sustained thresholds rather than one noisy spike
  • Customer-safe summaries with no process environment or secret data
02

Separate deployment from runtime health

A successful release means the exact image completed its deployment checks. Runtime health is evaluated separately from fresh telemetry, provider state and route probes, with maintenance and deliberate service restriction kept distinct from an outage.

  • Healthy, degraded, down and unknown
  • Maintenance and restricted states
  • Observed availability with clear freshness timestamps
03

Act on one durable alert

Stable alert identities, sustained windows, hysteresis and recovery events prevent repeated email and in-app noise. Corvus staff can acknowledge and investigate while the customer sees only alerts authorized for their project.

  • CPU, memory, disk and inode pressure
  • Telemetry, route, certificate and backup freshness
  • Odoo, console and email delivery policies remain auditable