Skip to content

feat: consolidate metrics stack into docker-compose.yaml using profiles#13

Open
Bierchermuesli wants to merge 2 commits into
developfrom
feat/metrics-profile
Open

feat: consolidate metrics stack into docker-compose.yaml using profiles#13
Bierchermuesli wants to merge 2 commits into
developfrom
feat/metrics-profile

Conversation

@Bierchermuesli

Copy link
Copy Markdown

Summary

  • Merges docker-compose.metrics.yml into docker-compose.yaml under a metrics profile — no more -f juggling or COMPOSE_FILE for dev
  • Moves metrics documentation to metrics/README.md
  • Commits the full metrics/ directory (Grafana provisioning, dashboards, scrape config, vmalert rules)
  • Adds neops/docker-compose.neops.prod.metrics.yml for prod
  • Adds docker-compose.override.yml to .gitignore for local customisations

Usage

# base services only
docker compose up

# base + full observability stack (VictoriaMetrics, Grafana, exporters, vmalert)
docker compose --profile metrics up

Prod deployments continue using COMPOSE_FILE to assemble the stack.

Test plan

  • docker compose up starts only redis, postgres, elasticsearch, frontend
  • docker compose --profile metrics up adds all metrics services
  • Fresh clone: bash metrics/fetch-dashboards.sh populates community dashboards, Grafana starts cleanly

obisimon and others added 2 commits March 17, 2026 00:28
Replace the separate docker-compose.metrics.yml overlay with a single
file using Docker Compose profiles. Run base services with
`docker compose up`, add the full observability stack with
`--profile metrics`. Move metrics documentation to metrics/README.md.
Also gitignore docker-compose.override.yml for local customisations.

@leandrolerena leandrolerena left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, just a admin point

Comment thread docker-compose.yaml
@@ -0,0 +1,135 @@
services:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this be on the root docker-compose.yml, or opt-in via COMPOSE?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants