Service areas
Show only services that are actually monitored.
SERVICE TELEMETRY
Status should come from monitoring — not assumptions.
The status surface is connected to EPTT's public status integration. When telemetry is available it is shown from the authoritative source; missing data is shown as unknown rather than guessed.
SERVICE TELEMETRY
Service status
The status surface is connected to EPTT's public status integration. When telemetry is available it is shown from the authoritative source; missing data is shown as unknown rather than guessed.
Public websiteeptt.dk product and resource pages
Awaiting telemetry
EPTT CloudCentral runtime where relevant
Awaiting telemetry
Dedicated environmentsCustomer-specific dedicated environments
Awaiting telemetry
On-Prem integrationsCustomer-operated environments
Awaiting telemetry
STATUS CONTRACT
Status is valuable only when it comes from a real data source.
A status surface should distinguish normal operation, planned maintenance and incidents. If telemetry is unavailable, the page must not guess.
Timeline
Maintenance and incidents need time, scope and updates.
Source of truth
Status comes from monitoring/incident data — not manual green lights.
01Operational
Normal service based on connected telemetry.
02Maintenance
Planned change with a known window and impact.
03Incident
Active event with the next expected update.
04History
Resolved incidents can support traceability and learning.
All service cards remain not connected until the concrete monitoring integration exists.