---
title: Viewing All Logs
slug: neurons-for-itsm/on-premises-help/enu/2022/viewing-all-logs
createdAt: 2026-07-30T04:08:22.532Z
---

If there are any problems with the ConfigDB, such as email issues or workflow errors, they are reported in the logs. Review the logs to determine the underlying issue and to help resolve it.

•[Setting the Log Level](https://docs.ivanti.com/neurons-for-itsm/on-premises-help/enu/2022/viewing-all-logs#Setting)

•[Viewing the Logs](https://docs.ivanti.com/neurons-for-itsm/on-premises-help/enu/2022/viewing-all-logs#Viewing)

### Setting the Log Level

You can set the amount and detail of information in the logs by adjusting the Log Level. You can do this by going to the **Logging Configuration** workspace. See the Service and Asset Manager Online Help.

### Viewing the Logs

Follow these steps to view all of the logs associated with the ConfigDB:

1.Log in to the ConfigDB.

2.From the workspace selector bar, select **All Logs**. The system displays the **LogsAll** workspace with the following information:

FieldDescriptionLog Entry IdA unique ID for this log entry.Log TimeThe time at which the log entry was originally created on the server.Log DB TimeThe time when the log was uploaded into the database.Client IP AddressThe IP address of the service that generated the log, such as the workflow server.SubSystem IdThe subsystem of the service that generated the log. (Each module has predefined subsystems. For example, for the email server, polling is a subsystem.)Login IdThe login ID for the user who experienced the log event.Tenant IdThe tenant instance that is experiencing the log event.Error CodeThe category of the error. An example is "trigger not found".Current RoleThe role assigned to the user if the error is generated by a user. If the error is generated by the system, this field is empty.Host NameThe machine that is reporting the error.Thread NameInternal thread ID. Not applicable.

3.Double-click any log entry to view the log details.

4.To refresh the data, click **Refresh**.
