linkerd2/controller/destination
Andrew Seigner 28d5007cdf
Harmonize Prometheus label usage (#690)
The Destination service used slightly different labels than the
telemetry pipeline expected, specifically, prefixed with `k8s_*`.

Make all Prometheus labels consistent by dropping `k8s_*`. Also rename
`pod_name` to `pod` for consistency with `deployement`, etc. Also update
and reorganize `proxy-metrics.md` to reflect new labelling.

Fixes #655

Signed-off-by: Andrew Seigner <siggy@buoyant.io>
2018-04-05 15:09:06 -07:00
..
client.go Introducing Conduit, the ultralight service mesh 2017-12-05 00:24:55 +00:00
dns.go Refactor destination service and add tests in preparation to add information about labels (#645) 2018-03-30 11:36:48 -07:00
dns_test.go Fix flakey dns_test (#516) 2018-03-05 16:50:33 -08:00
k8s_resolver.go Add pod-based metric_labels to destinations response (#429) (#654) 2018-04-02 18:36:57 -07:00
k8s_resolver_test.go Refactor destination service and add tests in preparation to add information about labels (#645) 2018-03-30 11:36:48 -07:00
listener.go Harmonize Prometheus label usage (#690) 2018-04-05 15:09:06 -07:00
listener_test.go Harmonize Prometheus label usage (#690) 2018-04-05 15:09:06 -07:00
resolver.go Add pod-based metric_labels to destinations response (#429) (#654) 2018-04-02 18:36:57 -07:00
resolver_test.go Add pod-based metric_labels to destinations response (#429) (#654) 2018-04-02 18:36:57 -07:00
server.go Add pod-based metric_labels to destinations response (#429) (#654) 2018-04-02 18:36:57 -07:00
server_test.go Add pod-based metric_labels to destinations response (#429) (#654) 2018-04-02 18:36:57 -07:00
test_helper.go Add pod-based metric_labels to destinations response (#429) (#654) 2018-04-02 18:36:57 -07:00