WIP: monitoring #15

Draft
Brooke wants to merge 12 commits from monitoring into main
Owner

#8

https://git.coopcloud.tech/coop-cloud/garage/issues/8
Brooke added 4 commits 2026-05-08 19:59:53 +00:00
Brooke added 1 commit 2026-05-08 20:10:23 +00:00
use compose_file env instead of a conditional in the .env file.
Some checks failed
continuous-integration/drone/pr Build is failing
46ba380e45
fauno requested changes 2026-05-08 20:34:25 +00:00
fauno left a comment
Owner

thanks!

thanks!
README.md Outdated
@ -56,0 +64,4 @@
>SECRET_METRICS_TOKEN_SECRET_VERSION=v1 # length=64 charset=hex
>
> MONITORING="true"
> ```
Owner

also add instructions on which address and port to add to prometheus/alloy

also add instructions on which address and port to add to prometheus/alloy
Author
Owner

Good point, instructions are definitely not finished, let me add the wip flag to the pr

Good point, instructions are definitely not finished, let me add the wip flag to the pr
Author
Owner

The pr is a wip so I'll wait on review until the instructions are finalized.

The pr is a wip so I'll wait on review until the instructions are finalized.
Brooke marked this conversation as resolved
@ -0,0 +4,4 @@
services:
app:
environment:
- MONITORING_ENABLED=true
Owner

i recently discovered the env var is not needed here because the template is rendered locally

i recently discovered the env var is not needed here because the template is rendered locally
Author
Owner

Where should this be placed to trigger the conditional in the config? I wasn't sure if it should go in the .env or in the compose file and chose the compose with the idea that it'd be simpler to manage in the config.

Where should this be placed to trigger the conditional in the config? I wasn't sure if it should go in the .env or in the compose file and chose the compose with the idea that it'd be simpler to manage in the config.
Owner

as i understand, if it's user-customizable it has to go on .env and only defined on compose files if it's needed during container runtime. if it's for templates it's ok for it to only be on .env.

as i understand, if it's user-customizable it has to go on `.env` and only defined on compose files if it's needed during container runtime. if it's for templates it's ok for it to only be on `.env`.
Owner

everything else looks ok, thanks!

everything else looks ok, thanks!
Brooke marked this conversation as resolved
@ -0,0 +9,4 @@
labels:
- "traefik.tcp.routers.garage-monitoring.rule=HostSNI(`*`)"
- "traefik.tcp.routers.garage-monitoring.entrypoints=garage-monitoring"
- "traefik.tcp.services.garage-monitoring.loadbalancer.server.port=3903"
Owner

this means the port is proxied but not protected by https, right? wouldn't it be better to proxy it through the domain name? i'm not sure if you can do this on coopcloud, maybe the paths need to be listed

this means the port is proxied but not protected by https, right? wouldn't it be better to proxy it through the domain name? i'm not sure if you can do this on coopcloud, maybe the paths need to be listed
Author
Owner

True, I didn't think of this. Going through a domain name would be easiest, because If I understand the monitoring endpoint correctly it's just served as a plaintext result.

True, I didn't think of this. Going through a domain name would be easiest, because If I understand the monitoring endpoint correctly it's just served as a plaintext result.
Brooke marked this conversation as resolved
compose.yml Outdated
@ -52,0 +58,4 @@
external: true
metrics_token:
name: ${STACK_NAME}_metrics_token_${SECRET_METRICS_TOKEN_SECRET_VERSION}
external: true
Owner

i think you can move these secrets to compose.monitoring.yml so they're only needed when monitoring is enabled

i think you can move these secrets to compose.monitoring.yml so they're only needed when monitoring is enabled
Author
Owner

Ah, thanks for catching this

Ah, thanks for catching this
Brooke marked this conversation as resolved
Brooke added 1 commit 2026-05-08 20:54:37 +00:00
move secrets to compose.monitoring.yml
Some checks failed
continuous-integration/drone/pr Build is failing
3741560b13
Brooke changed title from monitoring to WIP: monitoring 2026-05-08 20:56:24 +00:00
Brooke added 1 commit 2026-05-08 20:58:45 +00:00
no idea if this actually works, pushing so that I can test later
Some checks failed
continuous-integration/drone/pr Build is failing
baa4167a89
Brooke added 1 commit 2026-05-09 00:54:18 +00:00
set unique stack name
Some checks failed
continuous-integration/drone/pr Build is failing
88d46b767e
Brooke added 3 commits 2026-05-15 20:11:55 +00:00
Brooke requested review from fauno 2026-05-15 20:11:57 +00:00
Brooke added 1 commit 2026-05-15 20:32:13 +00:00
Merge branch 'main' into monitoring
Some checks failed
continuous-integration/drone/pr Build is failing
dfb679b1c0
Some checks failed
continuous-integration/drone/pr Build is failing
This pull request is marked as a work in progress.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin monitoring:monitoring
git checkout monitoring
Sign in to join this conversation.
No Reviewers
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/garage#15
No description provided.