Understanding the Log Content
- 1 Minute to read
- Print
- PDF
Understanding the Log Content
- 1 Minute to read
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Log Message Levels
CTERA products generate log messages upon various events. The log messages are divided into the severity levels.
| Level | Required Response |
|---|---|
| Emergency | System is unusable. |
| Alert | Action must be taken immediately. |
| Critical | Critical condition. A situation such as storage nearing full capacity has occurred. Action should be taken as soon as possible. |
| 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. |
Log Message Topics
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 and messages from a CTERA Agent are included in the agent topic.
Log messages are divided by one of the following topics:
- access
- accounting
- agent
- allTopics
- antivirus
- audit
- backup
- cloudsync
- files
- sync
- system
Log Message Examples
Example 1
Assume the following CTERA Portal log message is received:
info,Login,Portal,,2023-05-06T01:32:05,,CTTP,Administration,Client logged in to portal,192.168.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 attributes values are:
action – Login
protocol – CTTP
Message – Client logged in to portal
clientAddr – 192.168.1.15
topic – access
The message is also timestamped (2023-05-06T01:32:05).
Example 2
Assume the following CTERA Portal log message is received:
error,Login,Portal,,2023-05-06T13: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 attribute values are:
action – Login
protocol – CTTP
Message – Client login to portal failed
failedPortal – portal.myportal.com
reason – Login failed: Portal portal.myportal.com does not exist
failedDevice – IT
topic – access
The message is also timestamped (2023-05-06T13:10:00).
Was this article helpful?