Logging

Logging Configuration

Group same common errors

This option causes harmless exceptions, such as accessing a server that no longer exists, not to be logged in the API log, and repeated errors within the last 10 minutes to be grouped in the activity log so that the number of log entries is much smaller.

The option is enabled by default and it is recommended to leave it enabled, otherwise the activity log can quickly become large.

API log: Don't log response if response is large

Removes the API response from the API log if the response is larger than 20 kb. If the response is too large, the logged response is replaced with an appropriate message. Other data, like the request body content, remains unaffected.

The option is enabled by default and it is recommended to leave it enabled

Don't log the following errors

This option allows you to exclude common, non-critical errors from the logs. This keeps your logs focused on essential issues and prevents cluttering from irrelevant entries.

Exclude 'Access to server denied' logs

Exclude logs generated when a user attempts to access a server that they don't have permissions for. These attempts might be unintentional, for example, if you have resellers, a reseller might forget to remove the server from their billing integration.

Exclude 'Access to user denied' logs

Exclude logs generated when a user attempts to access a user profile they do not own.

Exclude 'Object not found' errors

Exclude logs generated when a user attempts to access a non-existent object or item.

Impersonate: Don't log impersonate user login

Enable if logins that were performed using the impersonate functionality should not be recorded in the user login history.

The option is enabled by default and it is recommended to leave it enabled

Impersonate: Don't log API calls

Don't log API calls in the access log of the impersonated account (recommended).

The option is enabled by default and it is recommended to leave it enabled

Impersonate: Don't log executed actions

Log the performed actions in the activity log of the parent account instead of the log of the impersonated account.

The option is enabled by default and it is recommended to leave it enabled

Log Retention Settings

You can specify for each log type how long the entries should be kept in the database. By default, the logs are kept for 30 days.

In addition to this, a maximum number of log entries can be defined. The limit is set to 300000 entries by default and it is recommended not to deactivate the limit as it can lead to a large accumulation of logs if Tenantos is used by many users or many actions are performed.