Logbook

Learn how to make the most of the logbook functionality to help you keep a pulse of actions taken, and easily identify issues within CIPP.

The Logbook is a feature within CIPP that records and displays all actions performed by the system on a given day. This page is essential for monitoring and troubleshooting as it helps users track the execution of various tasks, identify issues, and confirm successful operations.

Using the Logbook for troubleshooting

Users can verify if specific actions have occurred by checking the log entries. For example, if a user wants to verify if a specific scheduled task, such as the "Hudu Extension Sync," was executed successfully. They select the appropriate date, use the filter to search for "Hudu Extension Sync," and review the log entries to confirm successful execution.

Logbook Filters

Expanding the Logbook Filters section at the top of the page will present you with the following options for how you would like to retrieve data from the logbook:

  • Start Date

  • End Date

  • Filter by Username

  • Filter by Severity

Logbook Results Table

Column
Description

Date Time

The exact time the action was logged

Tenant

The primary domain of the tenant

Tenant ID

The tenant ID associated with the log entry

User

Indicates the user associated with the action

Message

Provides a brief description of the action performed

API

Identifies the API endpoint involved in the action

Severity

Indicates the severity level of the log entry. Options include: debug, info, warn, error, and critical

App Id

Log Data

Opens a second table to display information relevant to the logbook entry


Feature Requests / Ideas

We value your feedback and ideas. Please raise any feature requests on GitHub.

Last updated

Was this helpful?