Viewing the Audit Log

The audit log records the activities of users. It records events that occur when users create and modify objects on your system, as well as events that occur when users execute jobs or access services through the API or web services. Some examples of events recorded in the audit log include creating a dataflow, modifying a database connection, or running a job.

  1. Open Management Console.
  2. Go to System > Logs.
  3. Click Audit Log.

    The audit log lists the following information.

    Column Description
    Severity
    Error
    Errors indicate an isolated problem that causes part of the system to become unusable. For example, a problem that causes a single service to not work would generate an error.
    Warning
    Warnings indicate problems that do not stop the system from working. For example, when loading a service where a parameter has an invalid value, a warning is issued and the default parameter is used. During the use of a service, if results are returned but there is a problem, a warning will be logged.
    Info
    Info events are typically seen during startup and initialization, providing information such as version information and which services were loaded.
    Date/Time The date and time of the event in the time zone of the Spectrumâ„¢ Technology Platform server.
    User The user account that performed the action.
    Source The software component that generated the event. This could be the name of a module or "Platform".
    Event

    The action that occurred. The platform events are listed below. In addition to these events, other events may appear in your audit log depending on the modules you have installed.

    Create
    The object was created and saved to the server.
    Create Version
    A new version of the dataflow was created in Enterprise Designer.
    Delete
    The object was removed from the server.
    Delete Version
    The dataflow version was removed. Other versions may still exist.
    Expose
    The dataflow was exposed, making it available for execution.
    Item added
    The object was added to a folder on the server.
    Item moved
    The object was moved to a different folder on the server.
    Rename
    The object's name was modified and the object was saved.
    Unexpose
    The dataflow was made unavailable for execution. It can still be edited in Enterprise Designer.
    Update
    The object was modified and saved.
    Type

    The part of the system that was modified by the event. Examples of types include the dataflow type (job, service, subflow, process flow) file servers, and access control settings.

    In some situations an object of the same name may appear multiple times with different values in the Type column. This is because one user action may generate multiple events in the system. For example, when you create a job in Enterprise Designer, you will see a "Create" event for the job in the audit log, plus an "Item added" event for a FolderItem type that has the same name as the job. This indicates that the job was saved and placed in a folder on the system. The saving of the job and placement of the job into a folder are treated as two separate system events.

    Object Name The name of the item that generated the log entry. For example, the name of a dataflow. Object names may be user-defined, such as the name of a dataflow, or they may be defined by the system.