← Templates · Monitoring & Analytics
GR
Graylog
Community3 services
Centralized log management — collect, search, and alert on logs from your whole fleet in one place.
| Runs | 3 services |
|---|---|
| Stack | graylog-mongodbgraylog-opensearchgraylog |
| Provisioned for it | Nothing, it's self-contained |
| Verified | Not yet |
Why deploy on Railyard
Railyard provisions all 3 services in this stack together — graylog-mongodb, graylog-opensearch, graylog — wired to reach each other over the private network, on a server you already pay for.
Deploying Graylog is one piece of a bigger stack you can keep building — add a database, a worker, a cache, or another app, all on the same servers you already pay for.
Good for
- Centralized log aggregation and search across every app and server on your team
- A self-hosted alternative to a hosted log-management SaaS
- Alerting on log patterns (error rates, specific messages) across your whole fleet
Good to know
- MongoDB (config store) and OpenSearch (log storage) are dedicated to this stack, not shared Railyard addons — Graylog needs OpenSearch 2.x or Elasticsearch 7.x specifically, which is older than Railyard's general-purpose Elasticsearch addon
- OpenSearch needs real memory headroom — give this app's server at least 2GB free, or the OpenSearch container will get OOM-killed on startup
- Default login is admin / RailyardAdmin123! (Graylog stores this as a one-way SHA-256 hash, so it can't be generated as a random secret) — change it immediately after first login
- Ship logs to this stack from your other apps via GELF or syslog input, configured from the Graylog UI after deploy