feat: system backups and alerts pages#101
Draft
andre8244 wants to merge 14 commits into
Draft
Conversation
edospadoni
deployed
to
alerts-and-backup-ui - my-backend-qa PR #101
Render
Active
edospadoni
deployed
to
alerts-and-backup-ui - my-collect-qa PR #101
Render
Active
edospadoni
deployed
to
alerts-and-backup-ui - my-frontend-qa PR #101
Render
Active
Contributor
|
🔗 Redirect URIs Added to Logto The following redirect URIs have been automatically added to the Logto application configuration: Redirect URIs:
Post-logout redirect URIs:
These will be automatically removed when the PR is closed or merged. |
andre8244
force-pushed
the
alerts-and-backup-ui
branch
from
80211a6 to
f7d17d2
Compare
edospadoni
deployed
to
alerts-and-backup-ui - my-frontend-qa PR #101
Render
Active
andre8244
force-pushed
the
alerts-and-backup-ui
branch
from
f7d17d2 to
a9c986f
Compare
edospadoni
deployed
to
alerts-and-backup-ui - my-frontend-qa PR #101
Render
Active
edospadoni
force-pushed
the
feat/alerts-config-refactor
branch
from
74168a3 to
08a07dd
Compare
andre8244
force-pushed
the
alerts-and-backup-ui
branch
from
a9c986f to
eff1f04
Compare
edospadoni
deployed
to
alerts-and-backup-ui - my-frontend-qa PR #101
Render
Active
andre8244
changed the title
edospadoni
force-pushed
the
feat/alerts-config-refactor
branch
from
feea17d to
c4c7f2b
Compare
edospadoni
force-pushed
the
alerts-and-backup-ui
branch
from
eff1f04 to
9d111a7
Compare
edospadoni
deployed
to
alerts-and-backup-ui - my-frontend-qa PR #101
Render
Active
Member
|
update deploy |
Auto-updated .render-build-trigger files to ensure all services are deployed in PR preview environments. 🤖 Generated by GitHub Actions
Contributor
|
🚀 Build triggers updated! All |
edospadoni
deployed
to
alerts-and-backup-ui - my-frontend-qa PR #101
Render
Active
edospadoni
deployed
to
alerts-and-backup-ui - my-backend-qa PR #101
Render
Active
edospadoni
deployed
to
alerts-and-backup-ui - my-collect-qa PR #101
Render
Active
edospadoni
deployed
to
alerts-and-backup-ui - my-mimir-qa PR #101
Render
Active
Builds the operational alerts surface on top of Mimir Alertmanager: a
single paginated list endpoint plus per-system silence management,
resolved-alert history, and aggregations the UI uses to render the
overview page.
Endpoints:
- GET /alerts (cross-hierarchy / single-tenant / sub-tree scoping,
multi-value label filters, sorting on starts_at/severity/alertname,
pagination with stable fingerprint tiebreaker)
- GET /alerts/history (paginated alert_history rows with date range)
- GET /alerts/totals / /trend / /stats (severity buckets, time-series
deltas, top-N alertname/system_key, MTTR/MTBF)
- GET /alerts/{fingerprint}/activity (silence/unsilence audit timeline,
populated transparently by the silence endpoints)
- GET /systems/{id}/alerts and friends scoped to a single system
Each alert in the list is enriched with a local-DB system object
(id/name/type) so the frontend doesn't need a per-row round-trip.
Per-tenant fan-out failures are surfaced as warnings rather than
failing the whole request.
Gated on the existing read:systems / manage:systems permissions:
read for the list endpoints, manage for silence create/update/delete.
…GET /alerts Stamp system_type at ingest (collect) alongside the other system_* labels and drop the per-request DB lookup that enriched each alert with a separate system object. Saves a SELECT on every GET /alerts and removes a redundant field the frontend never read.
edospadoni
deployed
to
alerts-and-backup-ui - my-backend-qa PR #101
Render
Active
…UNT shortcut, in-process cache
edospadoni
deployed
to
alerts-and-backup-ui - my-backend-qa PR #101
Render
Active
POST /alerts/config used to 500 on invalid emails (slices lacked binding `dive`). Now binding, semantic, and entity-layer failures all go through response.ValidationFailed with JSON-path keys (email_recipients.2.address) and stable codes. Same envelope on the four silence endpoints. Fix reflect.Value.String() leaking "<int Value>" in response.ParseValidationErrors. OpenAPI: reusable SilenceValidationFailed response + inline examples.
edospadoni
deployed
to
alerts-and-backup-ui - my-backend-qa PR #101
Render
Active
Contributor
ℹ️ My API content change detectedNo structural change, nothing to display. Powered by Bump.sh |
edospadoni
deployed
to
alerts-and-backup-ui - my-frontend-qa PR #101
Render
Active
edospadoni
deployed
to
alerts-and-backup-ui - my-frontend-qa PR #101
Render
Active
The status-gated loop in db-migrate/db-migrate-qa called run_migration.sh status, which only checks for a schema_migrations row and ignores the recorded checksum. Drift on an already-applied migration was silently skipped. Call apply directly so report_checksum_drift fires, and exit the loop on the first non-zero status.
edospadoni
deployed
to
alerts-and-backup-ui - my-backend-qa PR #101
Render
Active
edospadoni
deployed
to
alerts-and-backup-ui - my-frontend-qa PR #101
Render
Active
andre8244
force-pushed
the
alerts-and-backup-ui
branch
from
728ac1e to
b12bf76
Compare
edospadoni
deployed
to
alerts-and-backup-ui - my-frontend-qa PR #101
Render
Active
edospadoni
deployed
to
alerts-and-backup-ui - my-frontend-qa PR #101
Render
Active
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📋 Description
Related Issue: #83
🚀 Testing Environment
To trigger a fresh deployment of all services in the PR preview environment, comment:
Automatic PR environments:
✅ Merge Checklist
Code Quality:
Builds: