---
title: "Understanding CTERA Log Messages"
slug: "understanding-portal-log-messages"
tags: ["Portal", "Logs"]
updated: 2024-03-21T06:58:02Z
published: 2024-03-21T06:58:02Z
canonical: "kb.ctera.com/understanding-portal-log-messages"
---

> ## 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.

# Understanding Portal Log Messages

CTERA products generate log messages upon various events. The log messages are divided by severity levels.

| Severity | Required Response |
| --- | --- |
| **Emergency** | System is unusable. |
| **Alert** | Action must be taken immediately. |
| **Error** | Error condition. Action must be taken as soon as possible. |
| **Warning** | Warning messages. An indication that an error may occur if action is not taken. |
| **Notice** | Normal but significant condition. |
| **Info** | Informational message. |
| **Debug** | Debug-level messages, useful for debugging and troubleshooting. |
| **Trace** | Trace-level messages, used by CTERA support for debugging and troubleshooting. |

Within each severity level, the log messages are divided in to topics. These topics enable you to understand the source of the message. For example, messages dealing with signing-in are included in the access topic.

Log messages are divided in to the following topics:

- Access
- Accounting
- Antivirus
- Audit
- Backup
- Cloud sync
- Files
- Permanent deletion
- Sync
- System

#### Example 1

Assume the following CTERA Portal log message is received:

```
info,Login,Portal,,2023-10-11T01:32:05,,CTTP,Administration,Client logged in to portal,172.21.1.15,,topic: access
```

The first word indicates that this is an info message, and the next two words indicate that it is related to logging into the portal.

The message is `Client logged in to portal`

The additional attribute values are: **The protocol used** – `CTTP` **The client IP address** – `172.21.1.15` **The action** – `Login`

The message is also timestamped (`2023-10-11T01:32:05`) with the type of message (`topic: access`).

#### Example 2

Assume the following CTERA Portal log message is received:

```
error,Login,Portal,,2023-10-11T13:10:00,,,CTTP,Client login to portal failed,,,failedPortal: portal.myportal.com reason: Login failed: Portal portal.myportal.com does not exist failedDevice: IT topic: access
```

The first word indicates that this is an error message, and the next two words indicate that it is related to logging into the portal.

The message is `Client login to portal failed`

The additional attribute values are: **The client IP address** – `172.21.1.15` **The failed device** – IT **The portal that could not be logged in to** – `portal.myportal.com` **The reason** – `Login failed: Portal portal.myportal.com does not exist` **The protocol used** – `CTTP` **The action** – `Login`

The message is also timestamped (`2023-10-11T13:10:00`) with the type of message (`topic: access`).