Re: Nimrod Config Reload Capability

12 views
Skip to first unread message

Sergio Bossa

unread,
Jan 28, 2013, 6:52:12 AM1/28/13
to nimro...@googlegroups.com
Hi Adam,

That's definitely a great idea :)
Could you open an issue about it?

Plans are to get back working on Nimrod in the coming weeks: this one and backups will probably be the next features to be implemented, so stay tuned :)

Cheers,

Sergio Bossa
Sent by iPhone

Il giorno 28/gen/2013, alle ore 10:57, ad...@metabroadcast.com ha scritto:

Hi,

We're looking at monitoring metrics of individual servers on a load balanced, elastic API. Presently we aggregate logs together and pass them to Nimrod in a single file, but we'd really like to understand individual app server performance. To support this we'd ideally like to have a config reload/refresh functionality in Nimrod that allows for a changing number of configured log sources (servers) currently driving an API. Is such a feature currently in place? If not, it would be a great addition I think :)

Regards,

Adam Horwich

--
 
 

ad...@metabroadcast.com

unread,
Jan 29, 2013, 5:17:52 AM1/29/13
to nimro...@googlegroups.com
Shall do, Sergio. Thanks! 

On the same subject/mechanism, can you clarify me what Nimord currently uses to determine where to start from in a source log file when it is restarted? Does it scan for the last record it knows was successfully recorded, or does it just tail from the end?

Adam

Sergio Bossa

unread,
Jan 31, 2013, 4:03:42 PM1/31/13
to nimro...@googlegroups.com
On Tue, Jan 29, 2013 at 10:17 AM, <ad...@metabroadcast.com> wrote:

> Shall do, Sergio. Thanks!

Great, thanks much, and sorry for this late response :)

> On the same subject/mechanism, can you clarify me what Nimord currently uses
> to determine where to start from in a source log file when it is restarted?
> Does it scan for the last record it knows was successfully recorded, or does
> it just tail from the end?

It either tails from the end (the default), or scans from the
beginning if provided with the option "end : false" (I know, not
really a great option name) in the specific log section.
Keeping/Restoring log line numbers may be a quite expensive
operations: there may be some improvement in the area in the future,
but nothing really planned as of now, but I'm open to suggestions and
contributions :)

Cheers,

Sergio B.

--
Sergio Bossa
http://www.linkedin.com/in/sergiob
Reply all
Reply to author
Forward
0 new messages