Status Page¶
TrueWatch provides a Status Page (service status page) where you can view the service status of each site, SLO reliability results, and historical incidents and maintenance records.
We continuously monitor the service status of all sites. When a service issue occurs, our team responds and resolves it immediately. If you encounter any anomaly while using the product, we recommend checking the TrueWatch service status first to determine whether it is caused by a temporary fluctuation in platform services. For example, if log reporting fails, first check whether the TrueWatch log service is operating normally.
Service Sites¶
In the navigation bar, go to Help > Status Page:
Click the subscribe button to begin monitoring the service status of this site. After subscribing, you will receive email notifications when the service experiences an anomaly.
Warning
TrueWatch continuously monitors the Features of workspaces under each site: detection runs once per minute, and results are aggregated every 5 minutes. A single anomaly within any 5-minute period marks that period as anomalous. If a module remains anomalous for 30 consecutive minutes (i.e., six consecutive aggregations), an alert email is triggered. After the first alert, if the next 5-minute aggregation for the module returns to normal, the anomaly is considered resolved.
You can click the following links to view the service status of each TrueWatch site:
| Site | Login URL | Cloud Provider |
|---|---|---|
| Americas 1 (Oregon) | https://us1-auth.truewatch.com/ | AWS (US Oregon) |
| Europe 1 (Frankfurt) | https://eu1-auth.truewatch.com/ | AWS (Frankfurt) |
| Asia-Pacific 1 (Singapore) | https://ap1-auth.truewatch.com/ | AWS (Singapore) |
| Indonesia 1 (Jakarta) | https://id1-auth.truewatch.com/ | Tencent Cloud (Jakarta) |
| Africa 1 (South Africa) | https://za1-auth.truewatch.com/ | Huawei Cloud (South Africa) |
Service Status¶
The service at each site may have one of the following statuses:
| Service Status | Description |
|---|---|
| Normal | The service at the current site is running normally. |
| Abnormal | The service at the current site is experiencing anomalies that may affect data reporting, processing, or querying. |
| Delayed | The service at the current site remains usable, but data processing or querying may be delayed. |
| Maintenance | TrueWatch technical staff are performing maintenance on related services. |
Anomaly/Delay Determination Logic¶
Status Page shows service status by top-level Feature and does not break down secondary items such as data reporting, data processing, or data querying. The following modules are currently covered:
| Top-Level Feature | Top-Level Feature |
|---|---|
| Events | Infrastructure |
| RUM | APM |
| Metrics | Logs |
| Synthetic Monitoring | CI Visualization |
| Security | Monitoring |
| Incident Center | Error Center |
| Unified Catalog | Agent Monitoring |
| Platform Access | Scenarios & Dashboards |
| OpenAPI | Notification Service |
The system determines service status based on the monitoring results of each module. Different modules may use different monitoring metrics. The following table shows some examples:
Judgment Item |
Condition | Service Status | Example |
|---|---|---|---|
| Data push failure rate | > 90% | Abnormal | For collected log data, the failure rate of pushing data from Kodo to the message queue exceeds 90%; the log service status is therefore abnormal. |
| Data ingestion failure rate | > 90% | Abnormal | For collected log data, the failure rate of writing data from Kodo-x to the database exceeds 90%; the log service status is therefore abnormal. |
| Message subscription delay P99 | > 5 minutes | Delayed | For collected APM data, the P99 data delay from the message queue to Kodo-x exceeds 5 minutes; the APM service status is therefore delayed. |
Managing Service Status¶
On the service status page, you can:
-
Click the link for each service site to switch to its corresponding service status;
-
Refresh service status in real time;
-
View the current status of each top-level Feature and its status over the last 24 hours;
-
View the service status and SLO reliability results for each site over the last 90 days;
-
Switch to view historical incidents.
Service Reliability¶
Status Page shows the service status of each site for the last 90 days and presents service reliability results based on SLO. SLO (Service Level Objective) measures whether a service meets its expected availability target within a specified period. With SLO results, you can quickly determine whether the service is meeting its target.
Historical Incidents¶
On the historical incidents page, you can:
-
View published service incidents and maintenance records by month;
-
View the top-level Feature associated with an incident and its SLO reliability results;
-
Switch to view service status.
Historical incidents are displayed by site and business date. If an incident record includes the following information, it is displayed on the page as well:
-
Incident status: Abnormal, Delayed, or Maintenance;
-
Affected modules: one or more top-level Features.
Incident records with affected modules are linked to the corresponding top-level Feature and that day's SLO results. If no affected module is specified, the record is displayed as a site-level historical record.
Note
Status Page displays only content officially published by TrueWatch. Drafts, archived content, and SLOs, notes, and knowledge content in regular workspaces are not displayed here.