client metrics

[sveinelo]

copied from Unleash/unleash#21

jarib:
There's currently no way of tracking what toggles are being used across applications. The simplest I can think of is to add easy statsd/graphite reporting in the client.

Perhaps look at Yammer Metrics. From reading the Kafka docs it sounds pretty nice:

Kafka uses Yammer Metrics for metrics reporting in both the server and the client. This can be configured to report stats using pluggable stats reporters to hook up to your monitoring system.

hennings:
Codahale Metrics (successor to Yammer metrics) is a nice library for timing
histograms, counters and gauges. There are several publishers you can plug
in to send the data to graphite, a servlet etc.

Henning
On 21 Oct 2014 15:33, "Jari Bakken" notifications@github.com wrote:

There's currently no way of tracking what toggles are being used across
applications. The simplest I can think of is to add easy statsd/graphite
reporting to the client.

Perhaps look at Yammer Metrics
https://dropwizard.github.io/metrics/3.1.0/. From reading the Kafka
docs it sounds pretty nice:

Kafka uses Yammer Metrics for metrics reporting in both the server and the
client. This can be configured to report stats using pluggable stats
reporters to hook up to your monitoring system.

—
Reply to this email directly or view it on GitHub
Unleash/unleash#21.

[sveinelo]

Should this be part of unleash-client-java, or should we add this to our internal unleash-client-java-finn wrapper?

[jarib]

If we do it in a pluggable way (e.g. with Codahale Metrics) I see no reason why it shouldn't be in the open source client.

[sveinelo]

+1

[ivarconr]

+1.

But i strongly advise that we look in to this at next milestone.

[ivarconr]

We should probably emit events to make it easy for people to integrate their custom metric system.

[ivarconr]

This is mostly done on the metrics branch. Only one thing left:

• add option to disable metrics (relevant for clients running agains older unleash server).

[ivarconr]

see #30