Skip to content

Add monitoring stack - #159

Open
blueraft wants to merge 8 commits into
developfrom
add-monitoring-stack
Open

Add monitoring stack#159
blueraft wants to merge 8 commits into
developfrom
add-monitoring-stack

Conversation

@blueraft

@blueraft blueraft commented Nov 4, 2025

Copy link
Copy Markdown
Collaborator
  • Adds an optional monitoring stack (Prometheus, Grafana, Alertmanager, cAdvisor, and Temporal UI)
  • Can be started by running: docker compose --profile monitoring up -d

@blueraft
blueraft force-pushed the add-monitoring-stack branch from 31424db to cfdb350 Compare January 22, 2026 12:10
@lauri-codes
lauri-codes changed the base branch from main to develop February 23, 2026 11:40
@blueraft
blueraft force-pushed the add-monitoring-stack branch 2 times, most recently from 040304b to 3e7ed7a Compare June 26, 2026 08:22
Comment thread README.md Outdated
> **External URL Configuration**: It is critical to change `MONITORING_EXTERNAL_URL` in production (e.g. to `https://my-oasis.org`). Leaving it as `http://localhost` will cause SSO login callbacks and CORS headers to fail for remote users.

> [!WARNING]
> **Access Control & Security**: By default, the monitoring stack connects to the public Keycloak realm (`fairdi_nomad_prod`). This means **any user with a NOMAD account** will be able to authenticate and access your Grafana and Temporal UI pages. For private production deployments, you **must** set up a dedicated Keycloak realm and configure client overrides in your `.env` file.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

I talked to Sascha about this. It's possible to create a custom realm in keycloak and give admin role to only that realm, so they would not be able to access other realms like nomad-prod.

There's also role based access, so the custom realm admin's roles could be further restricted to just manage-users for instance. https://www.keycloak.org/docs/latest/server_admin/index.html#_per_realm_admin_permissions

But this depends on whether we want to offer this as an option for oases that registers with us. @lauri-codes @hampusnasstrom

@blueraft
blueraft force-pushed the add-monitoring-stack branch from 4ace987 to 320edbb Compare August 12, 2026 10:42
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.

1 participant