Portal Logs
  • 2 Minutes to read
  • Dark
    Light
  • PDF

Portal Logs

  • Dark
    Light
  • PDF

Article Summary

The portal Log Viewer includes the following logs:

LogContent
SystemLog of all system events.
Local BackupLog of synchronization operations.
Cloud BackupLog of backup and restore operations.
Cloud SyncLog of cloud drive synchronization operations.
AccessLog of user access.
AuditLog of changes to the CTERA Portal.
AgentsLog of CTERA Agent events.
AntivirusLog of virus files detected by the portal antivirus function. This log is only displayed if the portal has an antivirus license.
Permanent DeletionLog of folders and files permanently deleted.

Understanding the Log Files

CTERA products generate log messages upon various events. The log messages are divided by 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.

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:

  • access
  • accounting
  • allTopics
  • antivirus
  • audit
  • backup
  • cloudsync
  • files
  • sync
  • system

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,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 usedCTTP
The client IP address172.21.1.15
The actionLogin

The message is also timestamped (2023-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,,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 class is UserLoggedInToPortalFailed
The message is Client login to portal failed

The additional attribute values are:
The client IP address172.21.1.15
The failed device – IT
The portal that could not be logged in toportal.myportal.com
The reasonLogin failed: Portal portal.myportal.com does not exist
The protocol usedCTTP
The actionLogin

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


Was this article helpful?

What's Next