Skip to content

perf-sentinel chart v0.2.44

Choose a tag to compare

View all tags
@github-actions github-actions released this 28 May 15:07
chart-v0.2.44
1a1712b

What's new in chart-v0.2.44

This is a metadata-only chart bump: appVersion advances from 0.7.7 to 0.7.8, the default image.tag now resolves to ghcr.io/robintra/perf-sentinel:0.7.8, and the artifacthub.io/images annotation is updated to keep the Artifact Hub display card in lockstep. No chart-level template diff, no values.yaml schema change, no new RBAC, no new optional ConfigMap or Secret, no .perf-sentinel.toml review required to upgrade. The chart-v0.2.43 surface is preserved byte-for-byte.

The 0.7.8 daemon image closes the suggested_fix coverage gaps surfaced by the v0.7.7 simulation lab and extends N+1 detection to HTTP. Vendor-specific OTel scope recognition (.NET EF Core, Quarkus), a service-name fallback for framework detection, and HTTP sanitizer-aware classification. Full release notes for the daemon at v0.7.8. None of this touches a chart-level template, a daemon HTTP route, a Prometheus metric label set the chart already exposes, or the OTLP listener wire format.

Changed

  • appVersion bumped from 0.7.7 to 0.7.8, default image.tag now resolves to ghcr.io/robintra/perf-sentinel:0.7.8.
  • artifacthub.io/images annotation updated to ghcr.io/robintra/perf-sentinel:0.7.8. Runtime image selection is unaffected (templates already resolve to .Chart.AppVersion when values.yaml image.tag is empty).
  • No chart-level config change. values.yaml, every template, the ServiceMonitor rendering, the NetworkPolicy rendering, the optional [daemon.ack] and [daemon.cors] plumbing, and the ack-toml-baseline mount are byte-for-byte identical to chart-v0.2.43.

Behavior

  • Daemon binary side: vendor-specific OTel scope recognition. Framework detection now resolves scopes outside the io.opentelemetry.* convention: OpenTelemetry.Instrumentation.EntityFrameworkCore / Microsoft.EntityFrameworkCore to csharp_ef_core, io.quarkus.* (reactive sub-packages before the catch-all) to java_quarkus_reactive / java_quarkus. Segment-boundary matching so io.quarkusbridge.acme does not match io.quarkus.
  • Daemon binary side: service-name fallback. When scopes, code_location, and filepath are all absent, a distinctive framework substring in the service name (e.g. helidon in helidon-se-svc) infers the framework as a last resort.
  • Daemon binary side: HTTP N+1 sanitizer-aware classification. Same-URL high-occurrence HTTP groups with timing variance reclassify from redundant_http to n_plus_one_http. High occurrence alone is not sufficient for HTTP (no looks_sanitized gate), so uniform-timing polls stay redundant_http.
  • No HTTP-shape change on the daemon side. Every /api/* route, every /metrics line, the OTLP HTTP and gRPC routes, and every JSON shape are byte-for-byte identical to chart-v0.2.43 for already-clean inputs.
  • No upgrade hook required, no on-disk migration. The runtime ack store JSONL schema is unchanged, existing acks survive the upgrade.

Install

helm install perf-sentinel oci://ghcr.io/robintra/charts/perf-sentinel --version 0.2.44

Upgrade an existing release:

helm upgrade perf-sentinel oci://ghcr.io/robintra/charts/perf-sentinel --version 0.2.44

Operator action required only if you use sanitizer_aware_classification

HTTP workloads may see some groups previously reported as redundant_http (Warning) now reported as n_plus_one_http (Critical at >= 10 occurrences) when they show timing variance. If your quality_gate rules are wired on critical-only counts, re-baseline n_plus_one_http_critical_max (or fix the patterns) before tightening the gate. Query-parameter HTTP N+1 on .NET stays redundant_http unless OTEL_DOTNET_EXPERIMENTAL_HTTPCLIENT_DISABLE_URL_QUERY_REDACTION=true is set, see the v0.7.8 release notes and docs/LIMITATIONS.md.

Full Changelog: chart-v0.2.43...chart-v0.2.44

Assets 4
Loading