Doubt related to the LoggingFramework Question

[radhika-singh-10]

There are a few questions related to the LogLevel that came to mind while brainstorming on the LoggingFramework System Design Question-

1. What is the default hierarchy of LogLevel that is to be followed?
2. Can there be any scenario where the logLevel is not mentioned? If yes, what is the default LogLevel?
3. Can one user in parallel log into the console and file different levels of log, like for console, the user is logging info, and for file, debug is being logged?

[Agent-Hellboy]

3. Can one user simultaneously log into the console and log different levels of messages — for example, logging INFO to the console while logging DEBUG to a file?

This is not implemented in the current version. You should explore and implement it.

What is the default hierarchy of LogLevel that should be followed?

You can set it to INFO, DEBUG, or any desired level. However, any proper logging framework should follow a hierarchical structure such as:

root logger -> child logger1, child logger2 -> grandchild1 grandchild2

If the root logger level is set to INFO, then all loggers within the hierarchy should inherit that level by default. You can also disable propagation and enforce a specific log level at a particular node (e.g., force child logger1 to use INFO only).

For example, refer to the Python logging framework implementation here:
https://github.com/python/cpython/blob/main/Lib/logging/__init__.py#L1483

Can there be any scenario where the LogLevel is not specified? If yes, what is the default LogLevel?

Yes, the framework can have a default log level. You can discuss this with your interviewer, or if you are implementing it, treat it as a design decision during the initial drafts.