Changelog

List of aperture PRs merged since 0.8.0-rc.2 release. For the full list of changes, see list of changes

Revamp workload and flux meter metrics and labels (#843)

New label attribute_found in FluxMeter to denote if the attribute on
which the flux meter is based was found in the access log/span
Removed label decision_type on summary workload_latency_ms since
it is now emitted only if response was received.
New counter workload_requests_total to measure the workload
decisions count since the summary does not take into account the
scenarios where response is not received e.g. rejects or connection
resets.
A new column response_received on OLAP Flow events to denote the
case when response is not received.

workload_latency = response_latency - aperture_latency

Workload Latency can become negative in case of connection reset
If the connection is aborted by Client or Server Envoy immediately
terminates the connection for the other endpoint.
In the Access Log, status code is set as 0 and response_latency is
set as zero.
If Authz call to Aperture Agent had succeeded for this request, then
aperture_latency is greater than zero.
- This would lead the workload_latency to be computed as negative.

Ignore negative workload latency I.E. don't populate the workload
latency column
Publish Prometheus metrics for flux-meter or workload latency only if
the metric column is found

This fixes regression introduced in
#828.

Dynamic Telemetry Flow Labels were added before labels filtering, which
led them to be incorrectly filtered out.