Understanding CTERA Log Files
- 21 Jun 2022
- 1 Minute to read
- Print
- DarkLight
- PDF
Understanding CTERA Log Files
- Updated on 21 Jun 2022
- 1 Minute to read
- Print
- DarkLight
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
CTERA products generate log messages upon various events. The log messages are divided by 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. |
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 one of the following topics, added to the end of each log entry:
- access
- accounting
- allTopics
- antivirus
- audit
- backup
- cloudsync
- files
- sync
- system
Example 1
Assume the following CTERA Portal log message is received:
info,Login,Portal,,2022-05-06T01: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 class is UserLoggedInToPortal
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 (2022-05-06T01:32:05) with the type of message (topic: access).
Example 2
Assume the following CTERA Portal log message is received:
error,Login,Portal,,2022-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 class is UserLoggedInToPortalFailed
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 (2022-05-06T13:10:00) with the type of message (topic: access).
Was this article helpful?