Aperture-py

Changelog

List of aperture PRs merged since 0.10.0-rc.1 release. For the full list of changes, see [list of changes][changes]

Learning period via EMA warm up window (921)

Description of change
* EMA emits invalids during warm up by default.
* Increase the EMA warm period in latency gradient policy to 1 minute.
* This would ensure no actuation for at least one minute of initial
traffic while Aperture learns the latency profile of a service.

[changes]: https://github.com/fluxninja/aperture/compare/releases/aperture-controller/v0.10.0-rc.1...releases/aperture-controller/v0.10.0-rc.2

Changelog

List of aperture PRs merged since 0.9.0 release. For the full list of changes, see [list of changes][changes]

Remove unused CheckResponse.Error (906)

This field described only authz-specific errors and was filled in
envoy.Handler.Check() response when also returning non-nil error, but in
such case the grpc framework was not using the response anyway.
This field was also used for metrics, but no codepath was actually
setting them, as flowcontrol never set these.

Also:
* Create errors using grpc/status package, so that we have control on
the grpc
status.
* Add missing sampled logs for error conditions.

Drive-by:
* Remove unused error from ClassifierEngine.Classify(), as it's
infallible (all errors are reported individually per-label).
* Remove unused code from authz.go.

Aperture SDK for Javascript (817)

Co-authored-by: Hasit Mistry <hasitfluxninja.com>

Add authzHandler to sdk-validator's grpc server (797)

Description of change
Add authzHandler to sdk-validator's grpc server

- Add CommonHandler
- Refactor FlowControlHandler with CommonHandler

Alerts pipelines (893)

Description of change

This introduces basic pipelines for Alerts including the following.

`alerts.Alerter` interface
This interface is being propagated as part of the platform. It can be
used by any party interested by calling `AddAlert(*alerts.Alert)`
method. In particular, it will be used by components like
https://github.com/fluxninja/aperture/issues/863.
There are helper functions and methods provided to `alerts.Alert` struct
for easy construction of such alerts.

Alerts receiver
This receiver calls `AlertsChan()` method of `alerts.Alerter`, converts
received `alert.Alert` structs into OpenTelemetry Logs format and pushes
into the next consumer.
There are convenient functions provided for easy conversions in both
ways, to be used in the Alertmanager exporter
https://github.com/fluxninja/aperture/issues/862.

Alerts processors
Alerts processor add proper labels to the alerts i.e. `agent_group`,
`instance` and `controller_id`.

Ref: GH-861

flowcontrol: restructure codebase II (898)

Description of change
Making room for adding more APIs (adapters, previews etc) under
flowcontrol.

Document Prometheus metrics and OLAP Flow events (878)

Description of change

Closes: 720

Speed up ser/deserialization of CheckResponse in envoy authz (881)

Now CheckResponse is binary-encoded in protobuf wire format and stored
in DynamicMetadata as base64 string. This speeds up serialization, but
also deserialization (in metrics processor).

No changes in envoyfilter defition were needed as envoy's access logger passes
StringValue from dynamic meatadata as-is (previously, it was JSON-encoding a
StructValue into string)

Note: metrics processor still accepts JSON-encoding, so other SDKs should
continue working without changes.


[changes]: https://github.com/fluxninja/aperture/compare/releases/aperture-controller/v0.9.0...releases/aperture-controller/v0.10.0-rc.1

Changelog

List of aperture PRs merged since 0.8.0 release. For the full list of changes, see [list of changes][changes]

flowcontrol: restructure codebase II (898)
Description of change
Making room for adding more APIs (adapters, previews etc) under
flowcontrol.

Document Prometheus metrics and OLAP Flow events (878)

Speed up ser/deserialization of CheckResponse in envoy authz (881)

Now CheckResponse is binary-encoded in protobuf wire format and stored
in DynamicMetadata as base64 string. This speeds up serialization, but
also deserialization (in metrics processor).

No changes in envoyfilter defition were needed as envoy's access logger passes
StringValue from dynamic meatadata as-is (previously, it was JSON-encoding a
StructValue into string)

Note: metrics processor still accepts JSON-encoding, so other SDKs should
continue working without changes.

Results

(Based on looking at pprof data)

* `createExtAuthzResponse` went from total 18% to total 2.6% (from about 50% of
authz.Check to about 10%).
* `GetStruct` went from total 6% to total 3% (from about 75% of
metricsprocessor.ConsumeLogs to about 40%)
* total ~20% improvement
* now agent's overhead is either comparable or slightly higher than istio
proxy's (before, it was noticably higher). (Note: istio proxy might also had
sped up as a result of this change due to not needing to serialize
protobuf.Struct in access logs, although I haven't measured this precisely)

Use envoy authz in java sdk (816)

buf dependencies were updated resulting in changes in many generated files.

Restructure flowcontrol directories (884)

Description of change
Restructure directories

Invalid signals telemetry (876)

Description of change
* `valid` label on `signal_reading` metric for indicating whether the
reading was valid.
* Rename label `attribute_found` on FluxMeter metric to `valid` to be
consistent with Signal metrics.
* A new panel in Signals dashboard: "Signal Validity (Frequency)"

panichandler: process panic handlers in the same go routine (875)

[changes]: https://github.com/fluxninja/aperture/compare/releases/aperture-controller/v0.8.0...releases/aperture-controller/v0.9.0

Changelog

List of aperture PRs merged since 0.8.0 release. For the full list of changes, see [list of changes][changes]

flowcontrol: restructure codebase II (898)
Description of change
Making room for adding more APIs (adapters, previews etc) under
flowcontrol.

Document Prometheus metrics and OLAP Flow events (878)

Speed up ser/deserialization of CheckResponse in envoy authz (881)

Now CheckResponse is binary-encoded in protobuf wire format and stored
in DynamicMetadata as base64 string. This speeds up serialization, but
also deserialization (in metrics processor).

No changes in envoyfilter defition were needed as envoy's access logger passes
StringValue from dynamic meatadata as-is (previously, it was JSON-encoding a
StructValue into string)

Note: metrics processor still accepts JSON-encoding, so other SDKs should
continue working without changes.

Results

(Based on looking at pprof data)

* `createExtAuthzResponse` went from total 18% to total 2.6% (from about 50% of
authz.Check to about 10%).
* `GetStruct` went from total 6% to total 3% (from about 75% of
metricsprocessor.ConsumeLogs to about 40%)
* total ~20% improvement
* now agent's overhead is either comparable or slightly higher than istio
proxy's (before, it was noticably higher). (Note: istio proxy might also had
sped up as a result of this change due to not needing to serialize
protobuf.Struct in access logs, although I haven't measured this precisely)

Use envoy authz in java sdk (816)

buf dependencies were updated resulting in changes in many generated files.

Restructure flowcontrol directories (884)

Description of change
Restructure directories

Invalid signals telemetry (876)

Description of change
* `valid` label on `signal_reading` metric for indicating whether the
reading was valid.
* Rename label `attribute_found` on FluxMeter metric to `valid` to be
consistent with Signal metrics.
* A new panel in Signals dashboard: "Signal Validity (Frequency)"

panichandler: process panic handlers in the same go routine (875)

[changes]: https://github.com/fluxninja/aperture/compare/releases/aperture-controller/v0.8.0...releases/aperture-controller/v0.9.0-rc.3

Changelog

List of aperture PRs merged since 0.9.0-rc.1 release. For the full list of changes, see [list of changes][changes]

[changes]: https://github.com/fluxninja/aperture/compare/releases/aperture-controller/v0.9.0-rc.1...releases/aperture-controller/v0.9.0-rc.2

Changelog

List of aperture PRs merged since 0.8.0 release. For the full list of changes, see [list of changes][changes]

Use envoy authz in java sdk (816)

buf dependencies were updated resulting in changes in many generated files.

Restructure flowcontrol directories (884)

Description of change
Restructure directories

Invalid signals telemetry (876)

Description of change
* `valid` label on `signal_reading` metric for indicating whether the
reading was valid.
* Rename label `attribute_found` on FluxMeter metric to `valid` to be
consistent with Signal metrics.
* A new panel in Signals dashboard: "Signal Validity (Frequency)"

panichandler: process panic handlers in the same go routine (875)


remove unused panic handler


[changes]: https://github.com/fluxninja/aperture/compare/releases/aperture-controller/v0.8.0...releases/aperture-controller/v0.9.0-rc.1