Status Page¶
TrueWatch provides a Status Page where you can view the service operational status, SLO reliability results, and historical incidents and maintenance records for each site.
We continuously monitor the service health of all sites. When a service issue occurs, the team responds and addresses it promptly. If you encounter anomalies during usage, it is recommended to first check the service status of TrueWatch to determine whether it is caused by a temporary platform fluctuation. For example, if log submission fails, you can first verify whether the log service of TrueWatch is functioning normally.
Service Sites¶
Navigate to Help > Status Page in the sidebar:
Click the Subscribe button to start monitoring the service operational status of this site. After subscribing, you will receive email notifications when the service experiences anomalies.
Note
TrueWatch continuously monitors the Features of the workspace under the site: it checks at a frequency of once per minute and aggregates results every 5 minutes. If any single anomaly occurs within a 5-minute window, that period is marked as anomalous. If a module remains anomalous for 30 consecutive minutes (i.e., 6 consecutive aggregated results), an alert email is triggered. After the first alert, if the next 5-minute aggregation of that module returns to normal, the anomalous event is considered resolved.
You can directly click the following links to view the service status of each TrueWatch site:
| Site | Login URL | Hosting 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/ | AWS (UAE) |
Service Status¶
The service of each site can be in one of the following states:
| Service Status | Description |
|---|---|
| Normal | The service of the current site is running normally. |
| Anomaly | The service of the current site has encountered an anomaly, which may affect data submission, processing, or querying. |
| Delay | The service of the current site is still usable, but data processing or querying may experience delays. |
| Maintenance | Technical personnel of TrueWatch are performing maintenance on the related service. |
Anomaly/Delay Determination Logic¶
On the Status Page, you can view the status of key Features including Events, Infrastructure, Real User Monitoring (RUM), Application Performance Monitoring (APM), Metrics, Logs, Synthetic Monitoring, and CI Visibility.
Based on the data processing pipeline above, the Status Page determines service status at two stages: data processing and data storage, as shown in the following table:
Judgment Item |
Judgment Condition | Service Status | Example Explanation |
|---|---|---|---|
| Data Push Failure Rate | Greater than 90% | Anomaly | When collecting log data, the failure rate of pushing data from Kodo to the message queue exceeds 90%, the log service status is Anomaly. |
| Data Ingestion Failure Rate | Greater than 90% | Anomaly | When collecting log data, the failure rate of writing data from Kodo-x to the database exceeds 90%, the log service status is Anomaly. |
| Message Subscription Delay P99 | Greater than 5 minutes | Delay | When collecting APM data, the P99 delay of data sent from the message queue to Kodo-x exceeds 5 minutes, the APM service status is Delay. |
Managing Service Status¶
On the service status page, you can:
-
Click the link of each service site to switch and view the corresponding service status.
-
Refresh the service status in real time.
-
View the current status and the last 24-hour status of Features: Events, Infrastructure, RUM, APM, Metrics, Logs, Synthetic Monitoring, and CI.
-
View the service status and SLO reliability results of each site for the last 90 days.
-
Switch to view Historical Incidents.
Service Reliability¶
The Status Page displays the service status of each site for the last 90 days and shows service reliability results based on SLO. SLO (Service Level Objective) measures whether the service meets the expected availability target within a specified time. Through the SLO results, you can quickly understand whether the service is meeting its target.
Historical Incidents¶
On the historical incidents page, you can:
-
View publicly disclosed service incidents and maintenance records by month.
-
View the SLO reliability results associated with incidents.
-
Switch to view service status.
If an incident record contains the following information, it will be displayed on the page:
-
Incident status: Anomaly, Delay, or Maintenance.
-
Affected modules: Logs, Metrics, or Infrastructure.
Note
The Status Page only displays content officially published by TrueWatch. SLO items, notes, and knowledge base content from regular workspaces are not shown here.
