Feature request: requests per-request timing metric customisation about talisker HOT 3 CLOSED

Hmm, this is an interesting one. Agreed that IP address makes no sense as part of the metric name. An application specified name for the upstream does make sense, but I'm not sure the best way to set that.

from talisker.

We've worked around this in our services themselves. However, talisker still emits it's per-request metrics. Perhaps as a half-way solution we could have a way to turn those off, since at this point they're just noise...

Cheers 😄

from talisker.

Fixed in #171, released in 0.9.7.

You can now do:

session.post(..., metric_api_name='api', metric_host_name='myservice')

And the metric name will take these into account, e.g.

requests.count.myservice.api:...
requests.latency.myservice.api.GET.200:...
requests.errors.myservice.http.api.200:...

from talisker.