Got it

This topic describes levels of VCN logs

Latest reply: Jan 10, 2019 13:03:57 279 1 0 0 0

Log Level

This topic describes levels of VCN logs.

Operation Log Levels
Operation log levels are Error, Information, and Debug in descending order.
Run Log Levels
Run log levels are Emergency, Critical, Error, Warning, Information, and Debug in descending order.
Security Log Levels
Security log levels are Error, Information, and Debug in descending order.

Operation Log Levels

Operation log levels are Error, Information, and Debug in descending order.

Table 1 lists log levels in ascending order.

Table 1 Log level description

Log Level

Log File Name

Description

Error

Error log

  • Error logs record errors that cause invocation failures.
  • Error logs record the error information and possible causes when the path or service logic is incorrect.

Information

Information log

Information logs record the program execution process, including the result of an operation performed during the process.

Testing personnel and personnel maintaining the live network can change logs to this level to view the detailed service process to help locate faults.

Debug

Debug log

  • Debug logs record debug information and traces or operations, for example, trace entry and exit of functions.
  • Debug logs provide detailed information to help development personnel to locate complex problems.
  • Debug logs also record code information used by software developers, for example, invoked functions, parameters, internal variables, and return values in function invocation.
  • Debug logs also record information about system exceptions or errors.
Debug logs are not stored in the database, and are stored only in debug log files.


Run Log Levels

Run log levels are Emergency, Critical, Error, Warning, Information, and Debug in descending order.

Table 1 lists log levels in ascending order.

Table 1 Log level description

Log Level

Log File Name

Description

Emergency

Emergency log

Emergency logs record system unavailability, for example, database connection failure and service startup failure.

Critical

Critical log

Critical logs record critical faults that greatly affect the system running, for example, NE creation failures.

Error

Error log

  • Error logs record unexpected faults that have major impact and can be rectified in the faulty module without affecting other modules, or have minor impact on other modules.
  • Logs at this level also record the fault information and possible causes when the path or service logic is incorrect, for example, logs about data length check failures, parameter errors, and data validity errors.

Warning

Warning log

Warning logs record system resource exceptions that occur when performance statistics are collected, for example, many database connections, and slow response of the system are recorded as warning logs.

Information

Information log

Information logs record the program execution process, including the result of an operation performed during the process.

Testing personnel and personnel maintaining the live network can change logs to this level to view the detailed service process to help locate faults.

Debug

Debug log

  • Debug logs record debug information and traces or operations, for example, trace entry and exit of functions.
  • Debug logs provide detailed information to help development personnel to locate complex problems.
  • Debug logs also record code information used by software developers, for example, invoked functions, parameters, internal variables, and return values in function invocation.
  • Debug logs also record information about system exceptions or errors.
Debug logs are not stored in the database, and are stored only in debug log files.



Security Log Levels

Security log levels are Error, Information, and Debug in descending order.

Table 1 lists log levels in ascending order.

Table 1 Log level description

Log Level

Log File Name

Description

Error

Error log

  • Error logs record information about login, logout, and authentication failures.
  • Error logs record the error information and possible causes when the path or service logic is incorrect.

Information

Information log

  • Information logs record information about login, logout, and authentication successes.
  • Security logs also record authentication information.

Debug

Debug log

  • Debug logs record debug information and trace login, logout, and authentication, for example, trace entry and exit of functions.
  • Debug logs provide detailed information to help development personnel to locate complex problems.
  • Debug logs also record code information used by software developers, for example, invoked functions, parameters, internal variables, and return values in function invocation.
  • Debug logs also record information about system exceptions or errors.


thanks for the information but need more explanation when get the logs how to trace it
View more
  • x
  • convention:

Comment

You need to log in to comment to the post Login | Register
Comment

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.