All pages
Powered by GitBook
1 of 1

Loading...

Activity Log

Understanding the Lifecycle Management Activity Log for tracking provisioning operations

The Lifecycle Management Activity Log provides visibility into all provisioning operations performed by Veza's Lifecycle Management system. It serves as a record of all activities, including successful actions, errors, and failures.

Overview

A Lifecycle Management policy defines automated workflows that execute when changes occur in a source of identity. The Activity Log tracks all aspects of these operations through a hierarchical structure:

  1. Policies define the overall automation framework for managing identities

  2. Workflows determine which actions should be executed for specific identities

  3. Actions represent specific operations to be performed on target systems

  4. Jobs are individual tasks executed as part of actions

  5. Events record atomic changes resulting from successful jobs

The Activity Log provides four views of this activity across different tabs: Events, Jobs, Actions, and Workflow Tasks.

Activity Log Tabs

Each tab can help track recent actions, verify that expected changes have occurred, identify patterns or issues in lifecycle events, and monitor the overall health of your Lifecycle Management implementation.

Events Tab

The Events tab shows individual changes made to entities and relationships within the system. Each event represents an atomic change resulting from a successful action.

Column
Description

Event Type

The type of event that occurred (e.g., REMOVE_RELATIONSHIP, ADD_RELATIONSHIP, SYNC_IDENTITY)

Timestamp

When the event occurred

Success

Whether the event completed successfully (True/False)

Identity

The identity associated with the event

Entity Name

The name of the entity affected by the event

Entitlement Entity

The entitlement entity involved in the event, if applicable

Message

Additional details or error messages related to the event

Jobs Tab

The Jobs tab displays individual jobs executed as part of actions. Jobs represent specific tasks performed on target systems, such as creating a user account or updating attributes. Use this tab to review whether individual jobs executed successfully or encountered an error and could not be completed.

Column
Description

Started At

When the job started

Completed At

When the job completed

Action Name

The name of the action that initiated the job

Action Type

The type of action (e.g., SYNC_IDENTITIES, MANAGE_RELATIONSHIPS)

Identity

The identity associated with the job

State

The current state of the job (Completed, Errored)

Any Changes

Whether the job resulted in changes to the system

Error Message

Detailed error information if the job failed

Actions Tab

The Actions tab shows high-level operations triggered by workflows. Actions typically involve one or more jobs that work together to accomplish a specific goal.

Column
Description

Started At

When the action started

Completed At

When the action completed

Action Name

The name of the action

Action Type

The type of action (e.g., SYNC_IDENTITIES, MANAGE_RELATIONSHIPS)

State

The current state of the action (Completed, Errored)

Jobs Started

Number of jobs initiated by this action

Any Changes

Whether the action resulted in changes to the system

Workflow Tasks Tab

Column
Description

Workflow

The name of the workflow

Identity

The identity for which the workflow was executed

Scheduled For

When the workflow was scheduled to run, if applicable

Started At

When the workflow started

Completed At

When the workflow completed

Entity Type

The type of entity processed by the workflow

State

The current state of the workflow (Completed, Errored)

Messages

Additional details or error messages related to the workflow

Workflow Execution Process

For each identity, Lifecycle Management follows this process:

  1. Validation: The system validates the identity against workflow trigger conditions

  2. Execution Determination: The system determines whether execution is needed based on:

    • Identity state (e.g., CREATED, CHANGED, UNCHANGED)

    • Continuous sync settings

    • Last execution time (for unchanged identities)

  3. Task Creation: If execution is needed, a workflow task is created

  4. Action Execution: The system executes conditions and actions via the task runner

  5. Result Storage: The result is stored as an event in the Activity Log

Using the Activity Log

The Activity Log provides filtering and search options to help locate particular events:

  • Filter by time period: Use the date range filters to focus on date ranges

  • Search by identity or entity: Use the search fields to find activities related to unique identities or entities

  • Filter by event type or state: Use the dropdown filters to focus on event type or state

  • View error messages: Review issues by checking for error messages in the Message column

Log Retention and Security

Veza maintains all Lifecycle Management activity logs for audit purposes. These logs are retained even if the associated integration is removed, maintaining a full historical record of all provisioning operations.

Note: Events shown in the Activity Log are distinct from the system-wide Event Logs found in the Veza Administration section.

See for more details on supported actions and configuration options.

The Workflow Tasks tab displays workflows executed for specific identities. Workflows represent a sequence of actions executed as part of a Lifecycle Management .

Actions
Policy