chukwa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Graham (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CHUKWA-515) Statistics REST API for Agent
Date Fri, 27 Aug 2010 19:06:55 GMT

    [ https://issues.apache.org/jira/browse/CHUKWA-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903537#action_12903537
] 

Bill Graham commented on CHUKWA-515:
------------------------------------

I'd like to return the 1 minute and 5 minute average data rates for each adaptor.

To do this I was planning on saving off the last 5 minutes worth of timestamp/offset pairs
for each adaptor, so stats could be generated. This would be done in the {{ChukwaAgent}} in
the {{reportCommit}} method. Let me know if you see problems with this approach, or if there's
a better way to go about this.

> Statistics REST API for Agent
> -----------------------------
>
>                 Key: CHUKWA-515
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-515
>             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.


Mime
View raw message