The purpose of this project is to have a simple framework for different logging adapters.
Originally developed as Hackathon_Logger but moved forewards and will now actively supported by firegento community.
See the Usage Chapter below to see how to use it.
Please be aware of the following restrictions:
- The ProxiBlue NewRelic extension use the same logic to log to NewRelic and will block FireGento Logger extension.
- Install modman
- Use the command from your Magento installation folder:
modman clone https://github.com/firegento/firegento-logger
- Install composer
- Install Magento Composer
- Create a composer.json into your project like the following sample:
{
...
"require": {
"firegento/logger":"*"
},
"repositories": [
{
"type": "composer",
"url": "http://packages.firegento.com"
}
],
"extra":{
"magento-root-dir": "./"
}
}
- Then from your
composer.json
folder:php composer.phar install
orcomposer install
- You can copy the files from the folders of this repository to the same folders of your installation
- Clear the cache, logout from the admin panel and then login again.
- Remove all extension files from your Magento installation
Configure the different loggers in System > Configuration > Advanced > Firegento Logger
- Karl Spies
- Christoph
- Christian
- Claas
- Damian Luszczymak
- Colin
- Marco Becker
- Nicolai Essig
- Daniel Kröger
- Michael Ryvlin
- Tobias Zander
Complete, working logger interfaces:
- File (Magento default)
- File (Advanced Format)
- Database
- XMPP (Jabber, Google Talk)
- Graylog2
- RSyslog (UDP)
- Loggly (UDP/HTTPS)
- Chromelogger
- Logstash
It is possible to use Multiple-Targets!
- Log Live View (Like a tail in terminal)
- Report View (Shows content of a report in backend)
For XMPP we use https://github.com/cweiske/xmpphp. For ChromeLogger we use https://github.com/ccampbell/chromephp
Make a fork, commit to develop branch and make a pull request
- There are combinations there doesn't work together ** You can't use Chromelogger with the embeded queueing model, because the queueing takes place after the response is send to the client