Skip to content
Tapsilog asynchronous logging service
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
bin Added file adapter. Now works like analogger Sep 2, 2010
lib/palmade Added support for tags Sep 3, 2010
CHANGELOG initial commit Aug 24, 2010 Added more info to readme Sep 3, 2010
Rakefile Bumped version to 0.1.0 Sep 3, 2010

Tapsilog, an asynchronous logging service

Tapsilog is a super customized fork of Analogger. Tapsilog allows you to attach tags to log messages so that it can be searched easily. Currently, Tapsilog supports files and mongodb as storage backend.

Supported adapters

  • file - Logs to files, STDOUT or STDERR
  • mongo - Logs to mongoDB

Gems required for mongoDB support

  • mongo
  • bson
  • bson_ext


Tapsilog Server

The best way to run tapsilog is to write a config file and call:

tapsilog -c /path/to/config_file.yml

Sample Config

port: 19080
  - /tmp/tapsilog.sock
daemonize: false
key: some_serious_key

syncinterval: 1

  #Currently supports file or mongo
  adapter: mongo

  #These options are used for mongo backend.
  #You can leave the host, port, user and password blank and tapsilog connects to your local mongo installation by default
  #port: 1234
  #user: root
  #password: somepassword
  database: tapsilog
    - service: default
      target: default # This is the mongodb namespace. For file backend, use the path of log file

    - service: dev.access
      target: dev.access

    - service: dev.bizsupport
      target: dev.bizsupport

Tapsilog Client

The tapsilog Logger class quacks like the ruby standard Logger.


logger ='default', '/tmp/tapsilog.sock', 'some_serious_key')
logger.level = Palmade::Tapsilog::Logger::DEBUG # defaults to INFO"I am logging a message.", {:my_name => "tapsilog", :my_number => 2})
You can’t perform that action at this time.