Skip to content

Audit And History ​

Use Reporting → Audit to investigate activity across Ordyn. Use an endpoint's History to understand what happened on one device.

Audit View ​

Start with the affected resource, actor, or time range. Audit helps identify changes to jobs, policies, software, services, and administrative settings that could explain an issue.

Use the Security Auditor role for read-only investigation. Select role scopes appropriate to the investigator's responsibilities; see Access Control. Global Audit can include broader feature activity, so prefer endpoint History for a narrowly scoped device investigation.

Configuration Revisions ​

Use an item's Revisions tab to inspect saved configuration, compare versions or restore earlier settings. Configuration audit entries link to the exact revisions produced by the change when you have access to the item. See Configuration Revisions and Proposals.

Endpoint History ​

Review the timeline to find whether a job reached a device, where it stopped, and what happened before the failure. Follow the run link for task output and artifacts. Intel AMT operations and managed desktop sessions also appear in History.

Remote Access and Remote Desktop sessions ​

Open a session's History entry to review its details and outcome. For further investigation, correlate it with Audit and the session time.

Stored Context ​

Events retain the names recorded when the activity occurred. Renaming or deleting a resource does not erase that context, although links to deleted resources may be unavailable. Links to retained configuration revisions remain usable.

Retention ​

Audit and endpoint History are retained for 365 days by default. Operators can configure them independently:

Deployment settingControls
ORDYN_AUDIT_EVENT_RETENTION_DAYSGlobal Audit retention
ORDYN_ENDPOINT_HISTORY_RETENTION_DAYSEndpoint History retention

A value of zero or less disables automatic age-based removal. Retention is measured from the event time. Removing audit events does not remove configuration revisions.

Security Notes ​

Treat event history as sensitive administrative data. It can identify people, devices, and operational activity even when secret values are excluded.

Support Bundles ​

When the timeline is insufficient, create a Support Bundle for the affected scope and time range. It collects the available logs and diagnostic context for further investigation.