Skip to content

Activity Log

Purpose

The Activity Log is the Clarity Transform record of business workflow events, approval decisions and sign-ins. The on-screen subtitle reads: "Business workflow events and approval decisions. This is the auditor's record: it is append-only for the application and tamper-evident by hash chain, not tamper-proof."

The page help describes the record model:

"Every row since the chain was introduced carries a sequence and a SHA-256 hash linked to the previous row. Verify recomputes the whole chain and names the first row that does not match, including any row inserted without going through the application. It detects edits, deletions and insertions by anyone who does not also recompute every later hash; a database owner who does recompute is caught only by comparing against the chain-head anchors written to the event log and to the anchor file on the web server, and against exports you keep yourself. Field-level diffs of grid edits live in Change Log; this page records who did what."

Page views, imports and generic create, edit and delete operations are not event types on this screen. For example, creating, editing and deleting a RAID Log entry writes nothing here; those changes are only in the Change Log. Field-level changes are in the Change Log, and system and diagnostic messages are in the Event Log.

Where to find it

Logging → Activity Log

What you see

Actions

These are buttons on the page, above the grid:

  • Verify audit chain: recomputes the hash chain and names the first row that does not match (from the page help). The result is shown in a banner above the filters, for example "Intact through sequence N (N rows checked, M pre-chain rows not verified). Head hash ... Algorithm sha256-v1." Each check is itself recorded as an AuditChainVerified event.
  • Export range: downloads every event that matches the current filters (Event Type, Entity Type, Date and Quick Time Range), not only the page on screen, as a CSV file named activity_log_<date>_<time>.csv. The file starts with a comment line giving the range, the exporting user and the chain head (sequence and hash), and ends with a row count, so it can be checked against a later Verify audit chain. Cells that a spreadsheet could read as a formula are prefixed with a single quote. Each export is recorded as an AuditExported event.
  • Auto-refresh

The grid toolbar has only a back arrow and a refresh icon. The grid rows have no row actions.

Filters

  • Event Type: the event types present in the log. In the lab: All Event Types, AdminChange, ApprovalItemsDecided, ApprovalItemsDecidedByOperator, ApprovalRequestSent, AuditChainVerified, AuditExported, ConfirmationFailed, ConfirmationOpened, ConfirmationPassed, EventLocked, EventMigrationConfirmationSent, EventUnlocked, InterviewFieldCommitted, InterviewInviteFailed, InterviewInviteOpened, InterviewInviteSent, MigrationPlanCreated, MigrationPlanStarted, MoveGroupApplied, RunbookPromotedToLive, RunbookTaskAssigned, SignIn, SmokeTestSignoffFailed, SmokeTestSignoffOpened, SmokeTestSignoffPassed
  • Entity Type: the entity types present in the log. In the lab: All Entity Types, activity_log, Application, ApprovalRequest, credentials, Device, integration_endpoints, InterviewSession, MigrationEvent, MoveGroup, NutanixMovePlan, Runbook, Session

A value appears in these lists once the log holds an event of that type. This build also records these event types, which appear in the list once they have occurred:

  • Runbook execution: RunbookTaskStatusChanged, RunbookTaskAssigned, RunbookTaskNoteChanged, RunbookTaskTimingEdited, RunbookTasksReset, RunbookStatusChanged, RunbookScriptRunStarted, RunbookScriptRunCompleted, RunbookActionStarted, RunbookTimelineExported, RollbackDeclared and RollbackActivationCompleted
  • T-Minus tasks: TMinusTaskStatusChanged, TMinusTaskAssigned, TMinusTaskNoteChanged and TMinusTaskTimingEdited
  • Notification emails, each with a Queued, Sent, NotSent and Failed event: TMinusEmailAction..., InterviewOutcomeEmail..., GoNoGoEmail... and EventComms...

  • GoNoGoDecisionRecorded and InterviewCompleted

  • Date: a date picker

  • Quick Time Range: All Time, Last 1 Hour, Last 6 Hours, Last 24 Hours, Last 7 Days, Last 30 Days

The grid remembers its Search: text, column filters, sort order and page size between visits. If the grid shows fewer rows than you expect, clear the Search: box and the filter row.

Columns

  • Timestamp: shown in UTC. The Change Log shows local time, so in summer the two logs show times one hour apart for the same change.
  • Event
  • Entity Type
  • Entity
  • Actor
  • Details

How to

See sign-ins

  1. Go to Logging → Activity Log.
  2. In Event Type, select SignIn.
  3. The grid shows sign-in rows, with Session in the Entity Type column.

Check whether a notification email was sent

  1. Go to Logging → Activity Log.
  2. In Event Type, select the email event for the notification, for example TMinusEmailActionSent for a T-Minus Send Email task, or GoNoGoEmailSent for a Go/No-Go decision.
  3. Look for a row for the event or task. If there is none, select the matching Queued, NotSent or Failed event type instead, for example TMinusEmailActionNotSent.

Export the events on screen

  1. Go to Logging → Activity Log.
  2. Set Event Type, Entity Type, Date and Quick Time Range to the events you want.
  3. Select Export range. The CSV file holds every matching event.

  • Automation Script Log: results of the automation scripts run by runbook tasks.

  • Change Log: field-level diffs of grid edits.

  • Event Log: system events, errors and diagnostic information.
  • Communications: the email templates behind the notification emails.
  • Go/No-Go: the decisions recorded as GoNoGoDecisionRecorded events.