Logging Levels

Syslog

Syslog is a standardized message logging protocol supported by numerous operating systems, applications, and hardware.

Log level

  • A log level is set up as an indicator within the log management system that captures the importance and urgency of all log entries.


  • They can alert you if certain events require your immediate attention or if you can continue with your day.

Types of Log Level


Critical

Description: Indicates a severe problem that has caused or will cause the system to fail or become unusable.

Usage: Signals that urgent intervention is needed to prevent total system failure or severe disruption.

Error

Description: Represents a significant problem that has caused a failure in a specific part of the system, but not necessarily the entire system.

Usage: Used to log failures or issues that affect the system’s operations and need to be resolved to ensure proper functionality.

Warning

Description: Indicates a potential problem. While not immediately harmful, warnings suggest that there could be a need for attention or future action to prevent problems.

Usage: Helps identify issues that are not critical but could potentially lead to problems if not addressed.

Information

Description: Provides general information about the system's operation. These messages indicate that things are working as expected

Usage: Useful for monitoring the system’s general health and understanding its behavior during normal operation.

DEBUG

Description: Provides detailed information primarily used for debugging.

Usage: Typically enabled during development or when troubleshooting specific issues.

Prioritizing

  1. Critical: Very High priority. Requires immediate attention to prevent complete system failure or severe disruption.

  2. Error: High priority. Needs to be addressed to fix significant issues affecting parts of the system, though the entire system may still be operational.

  3. Warning: Medium priority. Indicates potential issues that should be reviewed to prevent future problems, though not immediately disruptive.

  4. Information: Low priority. Provides general status updates and does not require immediate action but helps in monitoring and understanding system behavior.

  5. DEBUG: Low priority. Primarily used for development and troubleshooting, providing detailed technical information that is usually not needed during normal operations.





    By

Kaviraj P R