STREAMS-210 | Began planning MXBean monitoring strategy
STREAMS-210 | First run at aggregating all data stored in relevant JMX beans
STREAMS-210 | Relevant POJOs to represent JMX data
STREAMS-210 | Initial commit with json schemas and skeleton for JMX bean message aggregation
STREAMS-210 | Now aggregate all data from necessary JMX beans on a regular cadence
STREAMS-210 | Removed unnecessary POJO classes
STREAMS-210 | Fixing commit issue
Merge branch 'master' into STREAMS-210
STREAMS-210 | Removed accidental changes to runtime files
STREAMS-210 | Added test to test memory object deserializer
STREAMS-211 | Added the BroadcastMessagePersister interface which allows us to persist serialized JMX messages (like the ones we aggregate in the BroadcastMonitorThread). There is an implementation of that interface which persists those messages via a HTTP POST to a URI that is defined in the Streams configuration
STREAMS-211 | Removed unnecessary include
STREAMS-210 | Removed circular dependency in streams-pojo module
STREAMS-216 | Updated the broadcast object to contain a streams ID which will make it easier to identify which Stream the beans belong to
refresh streams-config
support detection of StreamsConfiguration
support detection of any component configuration
test using base ComponentConfiguration
STREAMS-220 | Rewrote FacebookPostActivitySerializer to guarantee final Activity data shape
Merge
Merge branch 'master' into STREAMS-211
STREAMS-211 | Responded to code review feedback
Merge commit '6f1bbec7992dcc3ea92e313cd5c4d99291a931e0'