---
title: System Events Report
description: Monitor and analyse critical system-level activities within your Perspio Tenant.
---
[Skip to content](https://help.perspio.io/help/system-events-report#main-content)
English
Show submenu for translations
Open main navigation
Close main navigation
- English
Show submenu for translations
- [Contact us](mailto:servicedesk@perspio.io)
[Contact us](mailto:servicedesk@perspio.io)
How can we help you?
- There are no suggestions because the search field is empty.
1. [Perspio Help Centre](https://help.perspio.io/help?hsLang=en)
2. [Reports](https://help.perspio.io/help/reports?hsLang=en)
3. [Available Reports](https://help.perspio.io/help/reports?hsLang=en#available-reports)
# System Events Report
## Monitor and analyse critical system-level activities within your Perspio Tenant.
#### **Overview**
The **System Events** report provides detailed visibility into operational incidents occurring at the platform level, such as action connector failures or other critical system-generated events. Each entry represents a system-level occurrence—such as failed automations or integration errors—that could impact data flow or trigger-based workflows.
This report is essential for administrators and support teams looking to identify root causes of service interruptions, integration issues, or automation failures. It helps ensure platform reliability by allowing early detection and resolution of system-critical incidents.
---
#### **Report Structure**
The generated System Events report contains the following data columns:
| **Column Name** | **Description** |
| --- | --- |
| **Timestamp** | The exact date and time when the system event occurred. Useful for correlating errors with asset activity or user actions. |
| **Criticality** | Severity classification of the event (e.g., **MAJOR**). Indicates the potential impact level and urgency for resolution. |
| **Event** | Describes the nature of the event. In the example provided, this is `Action Connector Failure`, identifying failed outbound system actions. |
| **Object Id** | The unique identifier of the object where the event occurred. Enables reference to specific automation components (e.g., `ac-000018`). |
| **Object Name** | The user-friendly name of the object involved in the event (e.g., `Send SMS`, `Update Asset Location`). Useful for locating and troubleshooting failed integrations or actions. |
Each row in the report represents an individual event logged by the system during the selected timeframe.
At the bottom of the report, a generation timestamp is included, confirming the moment the report was compiled along with the relevant time zone (e.g., AEST).
---
#### **How to Generate the Report**
To run the System Events report:
1. Navigate to **Reports → System Events → Snapshot**.
2. Choose your **Scope**:
- **Relative** (e.g., This Month, Last Week)
- **Range** (custom date range)
3. Select the **System Events** categories to include (e.g., Action Connector Failures, API Limitations).
4. Define **Criticality** filters as needed (e.g., **MAJOR**, **CRITICAL**, **WARNING**).
5. Click **Run Report**.
The results will display in a tabular format and can be exported to **PDF, PDF/A, XLSX** or **CSV** for audit logs, incident reviews, or escalation.
---
#### **Applicability and Use Cases**
The System Events report is most applicable to IT teams, integration engineers, and operations staff monitoring platform health. Common use cases include:
1. **Integration Error Tracking**
Identify failures in workflows such as sending SMS, pushing updates, or writing back to third-party systems.
2. **Automation Reliability Checks**
Review failed actions triggered by Perspio workflows and automation rules to ensure reliability of operational automations.
3. **Incident Correlation**
Match system-level errors against field activity or customer-reported issues to identify root causes.
4. **Audit and Compliance Reporting**
Maintain logs of platform-level issues for internal audits or external compliance requirements.
5. **Connector and Object Troubleshooting**
Pinpoint underperforming or incorrectly configured action connectors by analysing repeated failures tied to specific Object IDs.
---
#### **Interpreting the Data**
- A **repeating event pattern** with the same Object ID may indicate a configuration or authentication issue with an external integration.
- **MAJOR** and **CRITICAL** criticality levels should be reviewed and triaged as a matter of urgency.
- A **high volume of failures** within a short window may suggest a systemic outage or misconfigured connector.
- Absence of data may indicate either a stable environment or a misconfigured filter (ensure all required event types are selected).
---
#### **Summary**
The **System Events** report is a core diagnostic tool for monitoring the operational integrity of Perspio. By surfacing critical system-level events such as action connector failures, it empowers platform administrators to quickly investigate and resolve issues before they impact business operations. Use this report to stay on top of errors, maintain platform health, and ensure that automation and integrations run reliably across the tenant.
- [Introduction](https://help.perspio.io/help/introduction?hsLang=en#main-content)
- [How to's](https://help.perspio.io/help/introduction?hsLang=en#how-tos)
- [Assets](https://help.perspio.io/help/assets?hsLang=en#main-content)
- [Asset Inspector](https://help.perspio.io/help/assets?hsLang=en#asset-inspector)
- [Utilisation Module](https://help.perspio.io/help/assets?hsLang=en#utilisation-module)
- [Configuration](https://help.perspio.io/help/assets?hsLang=en#configuration)
- [Events](https://help.perspio.io/help/assets?hsLang=en#events)
- [Servicing](https://help.perspio.io/help/assets?hsLang=en#servicing)
- [Asset Configuration](https://help.perspio.io/help/assets?hsLang=en#asset-configuration)
- [Device Configuration](https://help.perspio.io/help/assets?hsLang=en#device-configuration)
- [Explorer](https://help.perspio.io/help/explorer?hsLang=en)
- [Dashboards](https://help.perspio.io/help/dashboards?hsLang=en#main-content)
- [Configuration](https://help.perspio.io/help/dashboards?hsLang=en#configuration)
- [Reports](https://help.perspio.io/help/reports?hsLang=en#main-content)
- [Available Reports](https://help.perspio.io/help/reports?hsLang=en#available-reports)
- [Groups](https://help.perspio.io/help/groups?hsLang=en#main-content)
- [Security Groups](https://help.perspio.io/help/groups?hsLang=en#security-groups)
- [Asset Groups](https://help.perspio.io/help/groups?hsLang=en#asset-groups)
- [Geofences](https://help.perspio.io/help/geofences?hsLang=en)
- [Workflows](https://help.perspio.io/help/workflows?hsLang=en)
- [Administration](https://help.perspio.io/help/administration?hsLang=en#main-content)
- [Settings Module](https://help.perspio.io/help/administration?hsLang=en#settings-module)
- [Admin Panel](https://help.perspio.io/help/administration?hsLang=en#admin-panel)
- [Devices](https://help.perspio.io/help/devices?hsLang=en#main-content)
- [Troubleshooting](https://help.perspio.io/help/devices?hsLang=en#troubleshooting)
- [Installation Guides](https://help.perspio.io/help/devices?hsLang=en#installation-guides)
[](https://perspio.io)
2/50 Yeo St, Neutral Bay NSW 2089
[mailto:servicedesk@perspio.io](mailto:servicedesk@perspio.io)
Copyright © 2026 Inauro