Operations History Report
The Operations History Report in Site24x7's Network Configuration Manager (NCM) provides a detailed log of every operation executed on your monitored network devices. Whether an operation was triggered automatically by Site24x7 or manually by an administrator, this report captures the full context, including the operation type, the action performed, the time of execution, who invoked it, and whether it succeeded or failed. Use this report to audit operational activity, investigate failures, and maintain accountability across your network management workflows.
Use cases
- Audit all backup, restore, and configuration push operations performed across NCM devices.
- Investigate failed operations to identify devices with credential issues or connectivity problems.
- Verify that scheduled or automated operations are executed at the expected times.
- Track which operations were initiated by Site24x7 automatically versus those triggered by an administrator.
- Maintain a complete operational audit trail for compliance and change management requirements.
Generating the report
- Log in to your Site24x7 account.
- Navigate to Reports > NCM Device > Operations History Report. The report loads with all operation records listed under the Ungrouped section by default. The count shown in parentheses indicates the total number of records in the current view.
- Use the Group by drop-down menu to organize the results by a specific attribute, such as the operation type or execution status.
- Click Add Filters to narrow down the results based on the device name, the operation type, the action, who invoked it, or the execution status.
- Click any sortable column header to sort the records in ascending or descending order.
- Click Share This to export the report as a CSV or PDF file, email it, or schedule it to be generated at regular intervals.
Report columns
The report displays the following columns for each operation record.
| Column | Description |
|---|---|
| Display Name | The name of the NCM device on which the operation was performed. |
| Operation Type | The category of the executed operation (for example, Backup). |
| Action | The description of the outcome or the action taken during the operation (for example, Backup operation executed successfully or Authentication failure due to incorrect credentials). |
| Execution Time | The date and time when the operation was executed, including the time zone. |
| Invoked By | The source that triggered the operation. Displays Site24x7 for automatically scheduled operations or the administrator's name for manually triggered ones. |
| Execution Status | The outcome of the operation, indicated by a status icon (see the Execution Status indicators below). |
Execution Status indicators
| Icon color | Status | Description |
|---|---|---|
| Green | Success | The operation completed without errors. |
| Red | Failed | The operation did not complete. Review the Action column for the failure reason (for example, an authentication failure or connectivity issue). |
Best practices
- Filter by the failed status to prioritize remediation: Use the Add Filters option to isolate failed operations and address the root cause, such as incorrect credentials or unreachable devices, before scheduling the next operation.
- Review authentication failures promptly: An Authentication failure due to incorrect credentials failure indicates that the device credentials stored in Site24x7 need to be updated. Resolve these to ensure backup continuity.
- Group by the operation type for focused audits: If you need to audit only backup operations or only restoration events, use the Group by drop-down menu to narrow the view to the relevant operation type.
- Schedule regular report exports: Use the Share This option to deliver automated report exports to your team, ensuring operational activity is always documented, even when no one is actively monitoring the console.
- Correlate failures with configuration changes: If an operation fails after a recent configuration change, cross-reference it with the Configuration Changes Report to determine whether the change introduced a connectivity or credential issue.
