it's codahale metrics:
https://dropwizard.github.io/metrics/3.1.0/
This has
1. metrics support for many standard things that hadoop & slider uses
2. standard outputters for ganglia, graphite and one that can just
output to log4j on a schedule
3. some servlets you can hook up to publish metrics
4. liveness probes to hit to ask for system health.
I've instrumented the REST API for applications, noting whenever a URL is
hit and the verb used, creating counters (monotonically increasing) and
meters (average rate tracking). This is the result of a GET on the metrics:
{
"version":"3.0.0",
"gauges":{
},
"counters":{
"DELETE-/application/action/ping.counter":{
"count":2
},
"GET-/application/action/ping.counter":{
"count":2
},
"GET-/application/live.counter":{
"count":1
},
"GET-/application/live/resources.counter":{
"count":1
},
"GET-/application/model.counter":{
"count":1
},
"GET-/application/model/desired.counter":{
"count":1
},
"GET-/application/model/desired/appconf.counter":{
"count":1
},
"GET-/application/model/desired/resources.counter":{
"count":1
},
"GET-/application/model/resolved.counter":{
"count":1
},
"GET-/application/model/resolved/appconf.counter":{
"count":1
},
"GET-/application/model/resolved/resources.counter":{
"count":1
},
"HEAD-/application/action/ping.counter":{
"count":2
},
"POST-/application/action/ping.counter":{
"count":2
},
"PUT-/application/action/ping.counter":{
"count":2
}
},
"histograms":{
},
"meters":{
"DELETE-/application/action/ping.meter":{
"count":2,
"m15_rate":0.0,
"m1_rate":0.0,
"m5_rate":0.0,
"mean_rate":59.9610253335332,
"units":"events/second"
},
"GET-/application/action/ping.meter":{
"count":2,
"m15_rate":0.0,
"m1_rate":0.0,
"m5_rate":0.0,
"mean_rate":32.828863136469586,
"units":"events/second"
},
"GET-/application/live.meter":{
"count":1,
"m15_rate":0.0,
"m1_rate":0.0,
"m5_rate":0.0,
"mean_rate":4.147536156146441,
"units":"events/second"
},
"GET-/application/live/resources.meter":{
"count":1,
"m15_rate":0.0,
"m1_rate":0.0,
"m5_rate":0.0,
"mean_rate":4.47205191157859,
"units":"events/second"
},
"GET-/application/model.meter":{
"count":1,
"m15_rate":0.0,
"m1_rate":0.0,
"m5_rate":0.0,
"mean_rate":4.957047186132165,
"units":"events/second"
},
"GET-/application/model/desired.meter":{
"count":1,
"m15_rate":0.0,
"m1_rate":0.0,
"m5_rate":0.0,
"mean_rate":5.13289053597643,
"units":"events/second"
},
"GET-/application/model/desired/appconf.meter":{
"count":1,
"m15_rate":0.0,
"m1_rate":0.0,
"m5_rate":0.0,
"mean_rate":6.3293142188043925,
"units":"events/second"
},
"GET-/application/model/desired/resources.meter":{
"count":1,
"m15_rate":0.0,
"m1_rate":0.0,
"m5_rate":0.0,
"mean_rate":7.4732271636860945,
"units":"events/second"
},
"GET-/application/model/resolved.meter":{
"count":1,
"m15_rate":0.0,
"m1_rate":0.0,
"m5_rate":0.0,
"mean_rate":5.703530485370444,
"units":"events/second"
},
"GET-/application/model/resolved/appconf.meter":{
"count":1,
"m15_rate":0.0,
"m1_rate":0.0,
"m5_rate":0.0,
"mean_rate":9.198701143398553,
"units":"events/second"
},
"GET-/application/model/resolved/resources.meter":{
"count":1,
"m15_rate":0.0,
"m1_rate":0.0,
"m5_rate":0.0,
"mean_rate":12.015764683264443,
"units":"events/second"
},
"HEAD-/application/action/ping.meter":{
"count":2,
"m15_rate":0.0,
"m1_rate":0.0,
"m5_rate":0.0,
"mean_rate":45.93688272313841,
"units":"events/second"
},
"POST-/application/action/ping.meter":{
"count":2,
"m15_rate":0.0,
"m1_rate":0.0,
"m5_rate":0.0,
"mean_rate":48.90812608514905,
"units":"events/second"
},
"PUT-/application/action/ping.meter":{
"count":2,
"m15_rate":0.0,
"m1_rate":0.0,
"m5_rate":0.0,
"mean_rate":53.50741077639253,
"units":"events/second"
}
},
"timers":{
}
}
As it feeds to ganglia, and as ambari picks up ganglia, these will be wired
up
On 14 January 2015 at 21:16, Rakesh Saha <[email protected]> wrote:
> Is this need to be integrated with ambari metrics service ?
>
> On Wed, Jan 14, 2015 at 8:29 AM, Steve Loughran (JIRA) <[email protected]>
> wrote:
>
> >
> > [
> >
> https://issues.apache.org/jira/browse/SLIDER-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> > ]
> >
> > Steve Loughran resolved SLIDER-754.
> > -----------------------------------
> > Resolution: Fixed
> >
> > > add metering/counter of REST operations
> > > ---------------------------------------
> > >
> > > Key: SLIDER-754
> > > URL: https://issues.apache.org/jira/browse/SLIDER-754
> > > Project: Slider
> > > Issue Type: Sub-task
> > > Components: Web & REST
> > > Affects Versions: Slider 0.70
> > > Reporter: Steve Loughran
> > > Assignee: Steve Loughran
> > > Priority: Minor
> > > Fix For: Slider 0.70
> > >
> > >
> > > add a class to support joint metering and counting, so that every REST
> > resource/endpoint can mark their use.
> > > Then ... support on-demand creation for trivial metering, and hook up
> > the Application URLs.
> > > Test: get the metrics after operations
> >
> >
> >
> > --
> > This message was sent by Atlassian JIRA
> > (v6.3.4#6332)
> >
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
