switch to alloy for logging #154
Conversation
There was a problem hiding this comment.
Pull Request Overview
This PR switches the logging system from Promtail to Alloy for collecting and processing logs from the Bridger application. The change modernizes the logging pipeline while maintaining compatibility with Loki for log storage.
- Replaces Promtail with Grafana Alloy for log collection and processing
- Adds new Alloy configuration files for both Docker and systemd journal-based deployments
- Updates Grafana dashboard and datasource configurations to support the new logging setup
Reviewed Changes
Copilot reviewed 11 out of 12 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| config/quadlet/alloy.container | New container configuration for running Alloy in systemd |
| config/alloy/config-journal.alloy | Alloy configuration for collecting logs from systemd journal |
| config/alloy/config-docker.alloy | Alloy configuration for collecting logs from Docker containers |
| config/deploy.sh | Updated deployment script to copy Alloy configuration files |
| compose.yaml | Replaced Promtail service with Alloy service and updated volume mounts |
| config/grafana/provisioning/datasources/grafana-datasources.yaml | Made Loki datasource editable |
| config/grafana/provisioning/dashboards/file-dashboards.yaml | New dashboard provisioning configuration |
| config/grafana/dashboards/updated/Bridger-1757731649448.json | New Grafana dashboard for Bridger logs |
| bridger/gateway.py | Added command-line interface for MQTT gateway user management |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
| loki.relabel "journal_labels" { | ||
| forward_to = [] |
There was a problem hiding this comment.
The forward_to parameter is set to an empty array but should reference the next component in the pipeline. This will cause the relabel component to drop all data instead of forwarding it to the processing stage.
| loki.relabel "docker_labels" { | ||
| forward_to = [] |
There was a problem hiding this comment.
The forward_to parameter is set to an empty array but should reference the next component in the pipeline. This will cause the relabel component to drop all data instead of forwarding it to the processing stage.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
No description provided.