[jira] [Commented] (SAMZA-105) Write a JMX scraper

["Steven Yates (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SAMZA-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119823#comment-14119823 ] 

Steven Yates commented on SAMZA-105:
------------------------------------

Hi [~criccomini], this should be pretty straight forward to do. 

Do you have an idea of how we would expose the metrics to potential clients, a rest interface perhaps? I will review the existing Metrics service and go from there .

Many Thanks
Steven Yates

> Write a JMX scraper
> -------------------
>
>                 Key: SAMZA-105
>                 URL: https://issues.apache.org/jira/browse/SAMZA-105
>             Project: Samza
>          Issue Type: Bug
>          Components: metrics
>    Affects Versions: 0.6.0
>            Reporter: Chris Riccomini
>
> Samza currently has a JmxReporter, which exposes Samza's metrics via JMX, so they can be viewed in things like VisualVM, JConsole, etc. It would be nice to have the inverse of this, as well: the ability to scrape metrics from JMX beans, and inject them into Samza's metrics framework.
> The main motivation for adding this support is to allow us to collect metrics for third party libraries that don't use Samza's metrics framework. Since most libraries expose information via JMX, it's can be used as a common bridge that we can pull metrics out of.
> One way to implement this would be to write a JmxMetricsScraper that implements TaskLifecycleListener. In the beforeInit method, it could grab the metrics registry and config objects, connect to the local process' JMX beans, and start scraping the relevant metrics.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)