Understanding the Log Content
  • 1 Minute to read
  • Dark
    Light
  • PDF

Understanding the Log Content

  • Dark
    Light
  • PDF

Article Summary

Log Message Levels

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

LevelRequired Response
EmergencySystem is unusable.
AlertAction must be taken immediately.
CriticalCritical condition. A situation such as storage nearing full capacity has occurred. Action should be taken as soon as possible.
ErrorError condition. Action must be taken as soon as possible.
WarningWarning messages. An indication that an error may occur if action is not taken.
NoticeNormal but significant condition.
InfoInformational message.
DebugDebug-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,,2020-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 attributes values are:
MessageClient logged in to portal
protocolCTTP
*clientAddr172.21.1.15
actionLogin
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,,2020-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:
MessageClient login to portal failed
clientAddr172.21.1.15
failedDeviceIT
failedPortalportal.myportal.com
reasonLogin failed: Portal portal.myportal.com does not exist
protocolCTTP
actionLogin
The optional field, failedUser, does not have a value.
The message is also timestamped (202-05-06T13:10:00) with the type of message (topic: access).


Was this article helpful?