# Drop in Analogger support for \_\_\_\_\_

**URL:** <https://www.ruby-forum.com/t/drop-in-analogger-support-for/90744>\
**Category:** Ruby\
**Created:** [March 31, 2007, 8:06pm UTC](https://www.ruby-forum.com/t/drop-in-analogger-support-for/90744 "2007-03-31T20:06:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![unknown](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/u/4bbf92/32.png) [@unknown](https://www.ruby-forum.com/u/unknown)\
**Post date:** [March 31, 2007, 8:06pm UTC](https://www.ruby-forum.com/t/drop-in-analogger-support-for/90744/1 "2007-03-31T20:06:08Z")

</div>

In the next release of Analogger, I want to provide drop in support for  
using it in other pieces of software or frameworks that provide/use a  
logging facility.

Does anyone have any requests?

Nitro looks easy.

It looks pretty simple to provide something that conforms to the  
SimpleLogger api in Rails.

What else might people like drop in support for?

Kirk H.

---

<div class="post-metadata">

**Author:** ![unknown](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/u/4bbf92/32.png) [@unknown](https://www.ruby-forum.com/u/unknown)\
**Post date:** [March 31, 2007, 8:17pm UTC](https://www.ruby-forum.com/t/drop-in-analogger-support-for/90744/2 "2007-03-31T20:17:09Z")

</div>

If you are going to support Rails make sure to look at the trunk. The  
trunk now just uses the Ruby logger API and defines a SimpleFormatter  
as the default formatter. Not sure what the API for Analogger is but  
the bottom line is that you just need to be able to support calls  
through the normal Ruby logger API.

V/r  
Anthony E.

---

<div class="post-metadata">

**Author:** ![unknown](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/u/4bbf92/32.png) [@unknown](https://www.ruby-forum.com/u/unknown)\
**Post date:** [March 31, 2007, 9:15pm UTC](https://www.ruby-forum.com/t/drop-in-analogger-support-for/90744/3 "2007-03-31T21:15:13Z")

</div>

On Sun, 1 Apr 2007, Anthony E. wrote:

> If you are going to support Rails make sure to look at the trunk. The  
> trunk now just uses the Ruby logger API and defines a SimpleFormatter  
> as the default formatter. Not sure what the API for Analogger is but  
> the bottom line is that you just need to be able to support calls  
> through the normal Ruby logger API.

That’s more or less all that Nitro needs, too, and I already have code  
running that is doing that, so that should work just fine.

Thanks,

Kirk H.