chukwa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ari Rabkin (JIRA)" <>
Subject [jira] Commented: (CHUKWA-515) Statistics REST API for Agent
Date Sat, 28 Aug 2010 03:57:53 GMT


Ari Rabkin commented on CHUKWA-515:

Bill -- I see one problem with your approach. If an adaptor puts out a large number of chunks,
your approach requires storing a potentially significant amount of data.

It's a pretty easy fix. Instead of caching a timestamp+offset on every commit or every send,
you could a timer go off every N seconds, and cache a timestamp-offset pair for each adaptor
only on the timer tick. This way, the memory required is constant per adaptor. The tradeoff
is that the average will be very slightly stale, but you can put a bound on how stale, by
picking a suitably low value for N.

> Statistics REST API for Agent
> -----------------------------
>                 Key: CHUKWA-515
>                 URL:
>             Project: Chukwa
>          Issue Type: Sub-task
>            Reporter: Bill Graham
>            Assignee: Bill Graham
> Develop a REST interface to expose Agent statistics. 
> * Request URI:
> {noformat}
> GET /rest/v1/adaptorStats HTTP/1.0
> {noformat}
> * For now I'm shooting for the XML response, but ultimately we can support optional params:
> {noformat}
> viewType=[json|xml|text] (default is XML?)
> {noformat}
> * Response XML
> TBD. My thought is to integrate with the {{AgentMetrics}} and {{ChunkQueueMetrics}} and
show their information, along with a list of adaptors. It appears that the same {{MemQueue}}
is shared amongst all adaptors, so we won't be able to expose per-adaptor stats as is. Let
me know if I'm missing something there, or if you have comments in general about the approach.
> I was planning on using Jetty similar to how the collector does. We could have some common
code that delegates requests to different handlers based on the URI. The current telnet interface
will remain as-is.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message