Draft
Conversation
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. |
Contributor
🤖 My API structural change detectedStructural change detailsAdded (10)
Powered by Bump.sh |
8b5324c to
9ec5be6
Compare
b10c682 to
08c4b4c
Compare
Member
Author
|
update deploy |
Contributor
|
🚀 Build triggers updated! All |
gsanchietti
commented
Feb 25, 2026
gsanchietti
commented
Feb 25, 2026
Member
Author
|
update deploy |
2 similar comments
Member
Author
|
update deploy |
Member
|
update deploy |
Contributor
|
🚀 Build triggers updated! All |
- Add authenticated metrics proxy endpoint (ANY /api/mimir/*)
- HTTP Basic Auth: system_key + system_secret (no JWT)
- Adds X-Scope-OrgID = organization_id for multi-tenancy
- Add MIMIR_URL config field (default: http://localhost:9009)
- Update nginx to route /mimir/ -> backend
- Add mimir/docker-compose.yml for dedicated metrics VM (Server B)
- Add OpenAPI documentation for /api/mimir/{path} endpoint
- Add user documentation (EN+IT) and operator README
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- alert.py: push/resolve/silence/list alerts via collect Mimir proxy (HTTP Basic auth) - alerting_config.py: manage alerting config via backend API (Logto OIDC auth) - scripts/README.md: usage documentation for both scripts Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
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
This pull request introduces backend support for alerting configuration and monitoring via integration with the Mimir Alertmanager. It adds new API endpoints for managing alert routing (email/webhook receivers, severity levels, exceptions), retrieving alerting configuration, and fetching current alerts.
Backend alerting API and configuration:
/api/alertingfor configuring alert routing, disabling alerts, retrieving alerting configuration, and listing current alerts. These endpoints enforce organization hierarchy and RBAC, and interact with the Mimir Alertmanager backend. (backend/main.go,backend/methods/alerting.go) [1] [2]backend/models/alerting.go) TO BE TESTEDOther changes
MimirURLparameterRelated Issue: #[ISSUE_NUMBER]
🚀 Testing Environment
To trigger a fresh deployment of all services in the PR preview environment, comment:
Automatic PR environments:
✅ Merge Checklist
Code Quality:
Builds: