What are the Logs?

What are Logs? And why is it important for Basic Programming?

Have you ever had a problem with a program and don't know what's going on? 🤔 Have to guess where it is, wasting hours!

Logs are "evidence" that helps us to stop guessing when a program has a problem. It's like a notebook that records everything a program does. When a problem occurs, just open it and know where to solve it!

Logs severity level:

- DEBUG: Details for programming people

- INFO: The usual thing to tell.

- WARNING: There's a problem, but it's still fine.

- ERROR: There's a real problem. Partially unavailable.

- CRITICAL: The system's broken.

How are prints and Logs different?

- Print: It's like writing on a note, pasting a screen. Turn off the program, the text is gone.

- Logs: It's like writing down a notebook with a date. Keep it looking backwards.

Good Logs Must Answer These 4 Questions:

1. When: Happened? (Timestamp)

2. What: How violent is the level? (Level)

3. Where: What part of the code is born? (Function, Module)

4. Why: Why is it born? Does it contain information? (UserID, OrderID)

Popular Logging Libraries:

- Python: logging, loguru.

- JavaScript: winston, pino

- Java: log4j, slf4j

- C #: Serilog, NLog

- PHP: Monolog

- Go: logrus, zap.

Interesting Logs Viewing Tool:

- Command line: grep, tail, less.

- Log management: ELK Stack, Splunk

- IDE integration: VS Code extensions

- Cloud services: AWS CloudWatch, Google Cloud Logging

Good Logs need to read and know about immediately. Don't need to sit down to code! Try Improving Writing Logs ensure that the programmer's life will definitely improve.

# Programming # logs # debugging # softwaredevelopment # Basicprogramming