Mimir integration

[gsanchietti]

📋 Description

This pull request introduces a complete proxy integration for Grafana Mimir, enabling secure, multi-tenant metrics and alerting management for each organization. It adds backend support for proxying all Mimir API calls (including Alertmanager), updates the API documentation, and provides user and developer documentation in both English and Italian. Additionally, it updates the CI workflow and NGINX configuration to support the new proxy endpoints.

Backend: Mimir Proxy Integration

• Implements a generic reverse proxy handler (ProxyMimir in collect/methods/mimir.go) that authenticates systems, resolves their organization_id, injects the X-Scope-OrgID header, and forwards any HTTP method to the configured Mimir backend. This supports all Prometheus and Alertmanager APIs, ensuring requests are properly scoped per organization. [1] [2] [3] [4] [5]

API & Documentation Updates

• Extends the OpenAPI specification to document the new /api/services/mimir/{path} endpoints, supporting GET, POST, PUT, and DELETE, with full details on authentication, multi-tenancy, and request/response formats. [1] [2]
• Adds comprehensive user documentation for alerting and Alertmanager usage, including authentication, troubleshooting, and usage examples in both English and Italian (docs/en/08-alerting.md, docs/it/08-alerting.md). [1] [2]
• Updates the documentation navigation and translation files to include the new Alerting documentation section. [1] [2]

Configuration & CI Enhancements

• Adds Mimir backend configuration to collect/.env.example and loads it in the service configuration, defaulting to http://localhost:9009. [1] [2]
• Updates the CI workflow to add an image description for the Mimir backend and injects this as a label in the container build process. [1] [2]

Infrastructure: NGINX Proxy

• Adds an NGINX location block to forward /services/mimir/ requests to the collect service's Mimir proxy endpoint, ensuring proper routing and header forwarding for the new API.

Compression Handling

• Adjusts the backend's gzip middleware to exclude Mimir proxy endpoints, preventing double-compression issues when proxying binary or already compressed data.

Related Issue: #[ISSUE_NUMBER]

🚀 Testing Environment

To trigger a fresh deployment of all services in the PR preview environment, comment:

update deploy

Automatic PR environments:

• Backend: https://my-backend-qa-pr-42.onrender.com
• Collect: https://my-collect-qa-pr-42.onrender.com
• Frontend: https://my-frontend-qa-pr-42.onrender.com
• Proxy: https://my-proxy-qa-pr-42.onrender.com

✅ Merge Checklist

Code Quality:

• 
• 
• 
• 

Builds:

• 
• 
• 
• 

[github-actions]

🔗 Redirect URIs Added to Logto

The following redirect URIs have been automatically added to the Logto application configuration:

Redirect URIs:

• https://my-frontend-qa-pr-42.onrender.com/login-redirect
• https://my-proxy-qa-pr-42.onrender.com/login-redirect

Post-logout redirect URIs:

• https://my-frontend-qa-pr-42.onrender.com/login
• https://my-proxy-qa-pr-42.onrender.com/login

These will be automatically removed when the PR is closed or merged.

[github-actions]

🤖 My API structural change detected

Preview documentation

Structural change details

Added (10)

• DELETE /api/alerting/config
• DELETE /api/services/mimir/alertmanager/api/v2/silences/{silence_id}
• GET /api/alerting/alerts
• GET /api/alerting/config
• GET /api/services/mimir/alertmanager/api/v2/alerts
• GET /api/services/mimir/alertmanager/api/v2/silences
• GET /api/services/mimir/alertmanager/api/v2/silences/{silence_id}
• POST /api/alerting/config
• POST /api/services/mimir/alertmanager/api/v2/alerts
• POST /api/services/mimir/alertmanager/api/v2/silences

Powered by Bump.sh

[gsanchietti]

update deploy

[github-actions]

🚀 Build triggers updated!

All .render-build-trigger files have been automatically updated to ensure fresh deployments of all services in the PR preview environment.

[gsanchietti]

update deploy

[edospadoni]

update deploy

[github-actions]

🚀 Build triggers updated!

All .render-build-trigger files have been automatically updated to ensure fresh deployments of all services in the PR preview environment.