Skip to content

Standardize Logging#1045

Draft
fernandohds564 wants to merge 36 commits intomasterfrom
add-logger-dev
Draft

Standardize Logging#1045
fernandohds564 wants to merge 36 commits intomasterfrom
add-logger-dev

Conversation

@fernandohds564
Copy link
Copy Markdown
Contributor

@fernandohds564 fernandohds564 commented Nov 23, 2023

This PR attempts to make use of the functionalities of the logging library to log messages. This will help standardize logging across all libraries to provide information to IOCs and HLA windows without the need of using callbacks or any other in-house developed strategy.

In order to review this PR, I recommend reading the basic and advanced tutorials of the logging library [1], to understand the basics of how it works. The main feature of this library that is not intuitive at first, but makes a lot of sense when you get used to it, is the hierarchy of loggers and how records are passed up in this hierarchy.

Another good reference is [2], where the best practices of the use of the library are explained. I tried to follow those, but I'm not sure if I succeded, since I'm still a newby in this subject.

Currently I have a doubt on how to define loggers. By the name of the module of the class or by the name of the module+the name of the class. It would be helpful to get an input from you guys on this matter.

Finally, feel free to add more reviewers for the PR. And help in implementation and testing is always welcome 😄.

[1] https://docs.python.org/3/howto/logging.html#logging-basic-tutorial
[2] https://coralogix.com/blog/python-logging-best-practices-tips/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant