AVAVERELI
CompanyProductsKnowledgeResearchDocumentationDevelopersSupportSearchCustomer portal

Observability

Operational claims require external evidence.

Synthetic monitoring is now active across all four governed public routes. Application telemetry, retained evidence export, formal incident integration, and public service claims remain gated.

TelemetryNOT_CONNECTED
Active probes4
Approved alerts0
Owner notificationOWNER_EMAIL_ENABLED
01

Metrics

Availability, latency, errors, deployments, and content integrity—not visitor profiling.

02

Logs

Structured operational events with correlation identifiers and explicit data minimisation.

03

Traces

Future request-path evidence across platform services without recording customer content.

04

Synthetic probes

External, unauthenticated checks from multiple regions against safe public journeys.

Synthetic journey catalogue

Probe public behaviour, not private users.

Active checks run every 5 minutes from Frankfurt and N. Virginia, use HTTPS GET, carry no authentication, and assert HTTP 200. Response bodies are not retained as operational evidence.

01

Public homepage

Homepage reachability and HTTP 200 response

Active
02

Knowledge hub

Knowledge gateway reachability and HTTP 200 response

Active
03

Service status

Service-status route readiness and HTTP 200 response

Active
04

Foundation record

Foundation record reachability and HTTP 200 response

Active

Privacy boundary

Operational telemetry is not behavioural analytics.

Observability may record route class, status, duration, build, service, and pseudonymous correlation identifiers. It must not collect message bodies, search terms, account identifiers, email addresses, document contents, payment details, or notification preferences.

Analytics boundary →Security posture →

Evidence flow

  1. 01Observe signal
  2. 02Evaluate approved rule
  3. 03Notify accountable owner
  4. 04Open incident record
  5. 05Publish verified status
No SLA or SLO published

Targets remain internal and unapproved. Public availability or response-time commitments require measured history, service ownership, and P100-aligned approval.

Service status →