[
https://issues.apache.org/jira/browse/SLIDER-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14273510#comment-14273510
]
Steve Loughran commented on SLIDER-747:
---------------------------------------
+1
I'll add this to the new REST API plans. Integrating with the existing WS/
paths will enforce security in a secure cluster (clients will need to handle
SPNEGO and http redirects)
We'd need
# a way for deployed apps to publish data for the agent to pick up. Some
defined location in the FS, perhaps?
# published events to be stored somewhere (attach to the {{RoleInstance}}
structure would work well. Agent would publish with a timestamp; WS API would
support enum and GET
I've also been adding some Codahale support in the AM, for publishing to
ganglia, graphite, the console: SLIDER-319
We could think about publishing the container info this way too, perhaps,
though the dynamic nature of containers may complicate things
> Expose component specific information through Slider AM Web Service
> -------------------------------------------------------------------
>
> Key: SLIDER-747
> URL: https://issues.apache.org/jira/browse/SLIDER-747
> Project: Slider
> Issue Type: Improvement
> Components: appmaster
> Reporter: Thomas Weise
>
> It should be possible for the agent to pass on stats/counters to as part of
> the heartbeat and for those to be made available in through the Slider AM
> REST API. The information could be an opaque JSON object that is not
> interpreted by the AM but available to the client. This can be used in Slider
> apps to provide stats without reinventing heartbeat protocol and web service.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
