What's changed
A performance and maintenance release: the Resolved page and the poll loop put much less load on the database, and the open dependency advisories are closed.
Breaking Changes
- Jarvis: No breaking changes. On the first start of 2.1.1 the database migration creates two indexes on
alert_events. The migration holds a write lock on that table while it builds them, which took about 1.4 s with 660k events on a laptop. Plan the rollout of a large instance accordingly. - Helm chart 2.2.1: No breaking changes. Only
appVersionmoves to2.1.1.
Fixed
- Resolved page without full scans. Every poll of an open Resolved tab aggregated and sorted the whole
alert_eventstable, which spilled to temp files on PostgreSQL with the defaultwork_mem. A page now reads through two new indexes and stops after its limit: 96 ms with temp files became 0.4 ms at 240k events. The result and its ordering are unchanged, and the page total costs a little more CPU in exchange for no disk I/O. - Far fewer database writes per poll. The recorder rewrote the fingerprint row of every active alert on every poll just to advance
last_seen_at. On PostgreSQL that is a new row version, an index entry and a WAL record each time, and one instance with about 60k fingerprints had reached 159 million row updates on that table. A fingerprint row is now rewritten at most once per hour, and a row that went missing is written again on the next poll. The retention sweep, which works in whole days, is not affected.
Security
- Closed the open Go standard library, vitest, minimatch and vite advisories, and updated
go-jose,golang.org/x/cryptoandgolang.org/x/oauth2. - The
govulncheckgate in CI now fails on reachable findings only, with each exception justified in the repository.
Changed
- Go dependencies updated, including echo 4.16.3, pgx 5.12 and SQLite 1.62.
- New documentation page on setting up Alertmanager receivers next to Jarvis, since Jarvis itself sends no notifications: Notifications.
- A short teaser video on the docs homepage (documentation site only, nothing changes in the app).
Full diff: v2.1.0...v2.1.1
Container image
docker pull ghcr.io/kj187/jarvis:2.1.1Digest: sha256:29a48e2b182687ee231b39fa60c34be71936fd52feec1bdc69d5be00fd31fe2e
Verify image signature (cosign)
cosign verify ghcr.io/kj187/jarvis@sha256:29a48e2b182687ee231b39fa60c34be71936fd52feec1bdc69d5be00fd31fe2e \
--certificate-identity="https://github.com/kj187/jarvis/.github/workflows/release.yml@refs/tags/v2.1.1" \
--certificate-oidc-issuer="https://token.actions.githubusercontent.com"Verify build provenance (GitHub attestation)
gh attestation verify oci://ghcr.io/kj187/jarvis:2.1.1 --repo kj187/jarvisHelm chart
helm install jarvis oci://ghcr.io/kj187/charts/jarvis --version 2.2.1Chart changes and breaking changes: charts/jarvis/CHANGELOG.md
Verify chart signature (cosign)
cosign verify ghcr.io/kj187/charts/jarvis:2.2.1 \
--certificate-identity-regexp='^https://github\.com/kj187/jarvis/\.github/workflows/chart-release\.yml@refs/(heads/main|tags/v[0-9].*)$' \
--certificate-oidc-issuer="https://token.actions.githubusercontent.com"SBOM
The SPDX SBOM covers the image (OS packages and the Go binary's modules) and the frontend production dependencies. It is attached to this release (sbom.spdx.json) together with its keyless signature bundle (sbom.spdx.json.sigstore.json) and attested to the image digest. The image manifest additionally embeds BuildKit's own SBOM (docker buildx imagetools inspect).
cosign verify-blob sbom.spdx.json \
--bundle sbom.spdx.json.sigstore.json \
--certificate-identity="https://github.com/kj187/jarvis/.github/workflows/release.yml@refs/tags/v2.1.1" \
--certificate-oidc-issuer="https://token.actions.githubusercontent.com"
gh attestation verify oci://ghcr.io/kj187/jarvis@sha256:29a48e2b182687ee231b39fa60c34be71936fd52feec1bdc69d5be00fd31fe2e \
--repo kj187/jarvis \
--signer-workflow kj187/jarvis/.github/workflows/release.yml \
--predicate-type https://spdx.dev/Document/v2.3