[
https://issues.apache.org/jira/browse/STREAMS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Blackmon resolved STREAMS-209.
------------------------------------
Resolution: Fixed
all sub-tasks merged
> Streams can broadcast JMX information
> -------------------------------------
>
> Key: STREAMS-209
> URL: https://issues.apache.org/jira/browse/STREAMS-209
> Project: Streams
> Issue Type: Bug
> Reporter: Robert Douglas
>
> As a developer, my Streams should be able to take all JMX information,
> package it up and periodically broadcast it to a centralized location. This
> way, when Streams are run on environments that we do not have full control
> over (ie. Iron.io) we can still monitor their performance.
> Acceptance Criteria:
> - Separate thread is instantiated for the LocalStreamBuilder which will be
> responsible for aggregating all JMX information and periodically sending
> broadcasts out at a predetermined interval
> - Thread/HTTP requests are not unduly taxing to the Stream
> - In the event of an exception/error/hang, the broadcasting thread can
> appropriately rely the information
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
