Ambassador Edge Stack collects many statistics internally, and makes it easy to
direct this information to a statistics and monitoring tool of your
choice. As an example, for a given service
usersvc, here are some
interesting statistics to investigate:
envoy.cluster.usersvc_cluster.upstream_rq_totalis the total number of requests that
usersvchas received via Ambassador Edge Stack. The rate of change of this value is one basic measure of service utilization, i.e. requests per second.
envoy.cluster.usersvc_cluster.upstream_rq_2xxis the total number of requests to which
usersvcresponded with an HTTP response indicating success. This value divided by the prior one, taken on an rolling window basis, represents the recent success rate of the service. There are corresponding
5xxcounters that can help clarify the nature of unsuccessful requests.
envoy.cluster.usersvc_cluster.upstream_rq_timeis a StatsD timer that tracks the latency in milliseconds of
usersvcfrom Ambassador Edge Stack's perspective. StatsD timers include information about means, standard deviations, and decile values.
There are several ways to get different statistics out of Ambassador Edge Stack:
:8877/metricsendpoint can be polled for aggregated statistics (in a Prometheus-compatible format). This is our recommended method.
- Ambassador Edge Stack can push Envoy statistics over the StatsD or DogStatsD protocol.
- Ambassador Edge Stack can push RateLimiting statistics over the StatsD protocol.