search

mushorg / buttinsky

Botnet monitoring is a crucial part in threat analysis and often neglected due to the lack of proper open source tools. Our tool will provide an open source framework for automated botnet monitoring. The modular design will allow full customization of the used protocols, the monitoring clients behavior, how we log the collected information, processing of the data to analyze the botnets purpose, size and threat and how the monitoring task are distributed between dedicated nodes.
http://buttinsky.org
GNU General Public License v3.0
79 stars 27 forks source link

Filelogging #27

Closed ihpd closed 11 years ago

ihpd commented 11 years ago

Debugging will improve a lot if we can enable file logging to a static text file.

In spawner.py

Under import --> import modules.reporting.file_logger as file_logger

Under load --> log.info("Task ID:" + identifier + " is loaded successfully into queue from source file <" + filename + ">")

Under main--> log = file_logger.FileLogger(name="buttinsky").log() log.info('Starting Buttinsky spawner')

Pls suggest if this viable

glaslos commented 11 years ago

I'm still not sure how to do this properly, I'll think about it.

ihpd commented 11 years ago

Just thinking out loud. Right now cli and spawner is live (usable condition. So lets get the raw logs(debug/info)

We will need to add two more TODO in each file to remove these file loggers when we get report_logger operational.

glaslos commented 11 years ago

Well the "report_logger" is only for the data collected by the monitors. For general system logging we are going to need something new. Preferably used by all layers.

ihpd commented 11 years ago

Let me know your thoughts on this.This can be used as a starting point.

https://github.com/glastopf/glastopf/blob/master/modules/reporting/file_logger.py

glaslos commented 11 years ago

I'll think about it.

ihpd commented 11 years ago

Looks like this is finally over with the basic logger implemented now. This can be moved to closure.