chukwa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Graham (JIRA)" <>
Subject [jira] Commented: (CHUKWA-515) Statistics REST API for Agent
Date Sun, 29 Aug 2010 03:04:52 GMT


Bill Graham commented on CHUKWA-515:

Thanks for the feedback Ari.

I was also concerned about holding onto to many data points, but was thinking I'd use the
write of a checkpoint as my timer, which I thought occurred at a {{reportCommit}} invocation.
(Maybe that's not the case?) The thought was to not hold more than 5 minutes worth, which
would be 60 data points per adaptor if checkpoints happened every 5 seconds. Do the checkpoints
happen at a constant interval? If not, or if it's too frequent, I could set up a timer as
you suggest. This would allow me to go back longer in time and save less frequently perhaps.

> 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