--- title: "Portal Logs" slug: "portal-logs-8-1-1" tags: ["Portal"] status: "update" updated: 2026-05-18T12:14:41Z published: 2026-05-18T12:14:51Z canonical: "kb.ctera.com/portal-logs-8-1-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://kb.ctera.com/llms.txt > Use this file to discover all available pages before exploring further. # Portal Logs Events are generated by the portal and written to different logs, depending on where the entry originated. The logs can be viewed in the **Event Log** page: | Log | Content | | --- | --- | | **System** | Events that do not belong in other log categories. | | **Access** | User access to the CTERA Portal events. | | **Audit** | Changes to the CTERA Portal configuration. | Viewing logs for the CTERA Portal system is available in the *global administration view*. Logs for team portals can be viewed in each team portal's view. For more details about the format of portal log messages, see [Understanding CTERA Portal Log Messages](/v1/docs/understanding-portal-log-messages). **To configure log settings:** 1. In the global administration view, select **Settings > Control Panel** in the navigation pane. The **Control Panel** page is displayed. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-M2413650.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A51Z&se=2026-11-11T05%3A28%3A51Z&sr=c&sp=r&sig=NoxIRvfPmL%2F4X%2Bb8O2QMioMHbw4HSC3rHVZlYjhtDn4%3D) 2. Select **Logs**, under **Notifications and Log Settings**. The **Log Settings** page is displayed. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-QDL6036Q.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A51Z&se=2026-11-11T05%3A28%3A51Z&sr=c&sp=r&sig=NoxIRvfPmL%2F4X%2Bb8O2QMioMHbw4HSC3rHVZlYjhtDn4%3D) 3. Complete the fields. **Keep logs for** – The number of days that the CTERA Portal should store logs. The default value is 30 days. **Log Level** – The minimum log level to display in the CTERA Portal. For example, if you select `Critical`, then only *Emergency*, *Alert*, and *Critical* logs entries are displayed in the CTERA Portal log pages. The default value is `Info` **Device Log Collector Level** – The minimum log level to collect from each device. For example, if you select `Critical`, then only *Emergency*, *Alert*, and *Critical* log events are collected from devices. The default value is `Info` 4. If you want to configure the CTERA Portal to send logs to a Syslog server located on your network or in the cloud, see [Setting Up Access to a Syslog Server](/v1/docs/portal-logs-8-1-1#setting-up-access-to-a-syslog-server). 5. Click **Save**. ## Setting Up Access to a Syslog Server 1. In the global administration view, select **Settings > Control Panel** in the navigation pane. The **Control Panel** page is displayed. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-BH4QOB73.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A51Z&se=2026-11-11T05%3A28%3A51Z&sr=c&sp=r&sig=NoxIRvfPmL%2F4X%2Bb8O2QMioMHbw4HSC3rHVZlYjhtDn4%3D) 2. Select **Logs**, under **Notifications and Log Settings**. The **Log Settings** page is displayed. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-OWTD68ZF.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A51Z&se=2026-11-11T05%3A28%3A51Z&sr=c&sp=r&sig=NoxIRvfPmL%2F4X%2Bb8O2QMioMHbw4HSC3rHVZlYjhtDn4%3D) 3. Slide **Use Syslog** on. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-IJ6EXBF8.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A51Z&se=2026-11-11T05%3A28%3A51Z&sr=c&sp=r&sig=NoxIRvfPmL%2F4X%2Bb8O2QMioMHbw4HSC3rHVZlYjhtDn4%3D) **Note** You can obtain free Syslog servers online, such as Kiwi Syslog Daemon ([http://www.kiwisyslog.com/](http://www.kiwisyslog.com/)). The following logs are sent to the Syslog server: **Minimum Event Severity** – The minimum log level to send to the Syslog server. For example, if you select `Critical`, then only *Emergency*, *Alert*, and *Critical* log events are sent to the Syslog server. The default value is `Info`. **Server Address** – The Syslog server IP address. **Syslog Port** – The Syslog server's port number. The default value is 514. **Syslog Protocol** – The protocol to use to send logs. The default is **UDP**. **To send logs securely using TLS:** - Server (Tomcat) logs – catalina.out.* - Portal logs – portal.* - Database logs - Audit logs - Journal logs 1. Change the **Syslog Protocol** to **TCP/TLS**. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-FXVQMZAZ.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A51Z&se=2026-11-11T05%3A28%3A51Z&sr=c&sp=r&sig=NoxIRvfPmL%2F4X%2Bb8O2QMioMHbw4HSC3rHVZlYjhtDn4%3D) 2. Click ![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-ODUY0XOK.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A51Z&se=2026-11-11T05%3A28%3A51Z&sr=c&sp=r&sig=NoxIRvfPmL%2F4X%2Bb8O2QMioMHbw4HSC3rHVZlYjhtDn4%3D) to upload and browse to a valid CA certificate, select it and click **Open**. The certificate must be in PEM format. If the certificate is valid, the certificate distinguished name is displayed. 3. Optionally, slide **Use Client Certificate** on if you want authentication on both the client and server sides. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-G336ML46.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A51Z&se=2026-11-11T05%3A28%3A51Z&sr=c&sp=r&sig=NoxIRvfPmL%2F4X%2Bb8O2QMioMHbw4HSC3rHVZlYjhtDn4%3D) If client side authentication is enabled: If the private key is valid, `Valid` is displayed for **Private Key (*.pem)**. If the certificate is valid, the certificate distinguished name is displayed in **Certificate (*.pem)**. 1. Click ![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-ODUY0XOK.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A51Z&se=2026-11-11T05%3A28%3A51Z&sr=c&sp=r&sig=NoxIRvfPmL%2F4X%2Bb8O2QMioMHbw4HSC3rHVZlYjhtDn4%3D) to browse to the private key to upload. 2. Select it and click **Open**. The private key must be in PEM format. 3. Click ![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-ODUY0XOK.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A51Z&se=2026-11-11T05%3A28%3A51Z&sr=c&sp=r&sig=NoxIRvfPmL%2F4X%2Bb8O2QMioMHbw4HSC3rHVZlYjhtDn4%3D) to browse to a valid certificate. 4. Select it and click **Open**. The certificate must be in PEM format. 4. Click **Save**. ## Clearing Logs You can clear the logs of all team portals. **To clear all logs:** 1. In the global administration view, select **Settings > Control Panel** in the navigation pane. The **Control Panel** page is displayed. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-WMY0TGO9.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A51Z&se=2026-11-11T05%3A28%3A51Z&sr=c&sp=r&sig=NoxIRvfPmL%2F4X%2Bb8O2QMioMHbw4HSC3rHVZlYjhtDn4%3D) 2. Select **Logs**, under **Notifications and Log Settings**. The **Log Settings** page is displayed. ![Image](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-4BHPLEON.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A28%3A51Z&se=2026-11-11T05%3A28%3A51Z&sr=c&sp=r&sig=NoxIRvfPmL%2F4X%2Bb8O2QMioMHbw4HSC3rHVZlYjhtDn4%3D) 3. Click **Clean Now**. Logs are cleared in all virtual portals.