Status Page¶
TrueWatch provides a Status Page where you can view the operational status of each site, SLO reliability results, and historical incidents and maintenance records.
We continuously monitor the service status of all sites. If a service issue occurs, our team responds and resolves it as a priority. If you encounter anomalies during use, we recommend checking the TrueWatch service status first to determine whether the issue is caused by temporary platform fluctuations. For example, if log uploads fail, check whether the TrueWatch log service is operating normally.
Service Sites¶
Navigate to Help > Status Page in the sidebar:
Click the Subscribe button to start monitoring the service status of this site. After subscribing, you will receive email notifications when service anomalies occur.
Warning
TrueWatch continuously monitors all feature modules of the workspace under each site: checks are performed at 1-minute intervals, and results are aggregated every 5 minutes. If a single anomaly occurs within any 5-minute window, that period is marked as anomalous. If a module remains anomalous for 30 consecutive minutes (i.e., six consecutive aggregated results), an alert email is triggered. After the first alert, if the next 5-minute aggregation returns to normal, the anomaly event is considered resolved.
You can directly click the links below 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/ | AWS (UAE) |
Service Status¶
Each site’s service can have the following statuses:
| Service Status | Description |
|---|---|
| Operational | The site’s service is running normally. |
| Critical | The site’s service is experiencing anomalies that may affect data upload, processing, or querying. |
| Degraded | The site’s service is still usable, but data processing or querying may be delayed. |
| Maintenance | TrueWatch technical staff is performing maintenance on the relevant service. |
Critical/Degraded Determination Logic¶
The Status Page displays service status by primary feature modules and does not break down into sub-items such as data upload, data processing, or data querying. The following modules are currently covered:
| Primary Feature Module | Primary Feature Module |
|---|---|
| Events | Infrastructure |
| RUM | APM |
| Metrics | Logs |
| Synthetic Monitoring | CI Visibility |
| Security | Monitors |
| Incident Center | Error Tracking |
| Unified Catalog | Agent Monitoring |
| Platform Access | Scenarios & Dashboards |
| OpenAPI | Notification Services |
The system determines the service status based on monitoring results for each module. Different modules may use different monitoring metrics. The table below provides some examples:
Check Item |
Check Condition | Service Status | Example Description |
|---|---|---|---|
| Data Push Failure Rate | Greater than 90% | Critical | Log data collection: failure rate of pushing data from Kodo to the message queue exceeds 90%, resulting in a Critical status for the Logs service. |
| Data Ingestion Failure Rate | Greater than 90% | Critical | Log data collection: failure rate of writing data from Kodo-x to the database exceeds 90%, resulting in a Critical status for the Logs service. |
| Message Subscription Delay P99 | Greater than 5 minutes | Degraded | APM data collection: P99 delay of data sent from the message queue to Kodo-x exceeds 5 minutes, resulting in a Degraded status for the APM service. |
Managing Service Status¶
On the service status page, you can:
-
Click on each service site link 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 each primary feature module.
-
View the service status and SLO reliability results for each site over the last 90 days.
-
Switch to view Historical Incidents.
Service Reliability¶
The Status Page displays the service status for each site over the last 90 days and shows the service reliability results based on SLOs. An SLO (Service Level Objective) measures whether the service meets the expected availability target within a specified period. By checking the SLO results, you can quickly determine 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 primary feature modules associated with an incident and their SLO reliability results.
-
Switch to view the service status.
Historical incidents are displayed by site and business date. If an incident record contains the following information, it will be displayed on the page:
-
Incident status: Critical, Degraded, or Maintenance.
-
Affected modules: one or more primary feature modules.
Incident records that include affected modules are linked to the corresponding primary feature modules and the day’s SLO results. If no affected modules are specified, the record is displayed as a site-level historical record.
Note
The Status Page only displays content officially published by TrueWatch. Drafts, archived content, and SLOs, notes, or knowledge content from regular workspaces are not shown here.