Repository navigation
Graylog SIEM Deployment Guide
Historical lab configuration โ not a current production deployment recipe (reviewed November 11, 2026). The Docker example below uses Graylog 5.2 and OpenSearch 2.12.0. Compatibility, vendor support status, images, credentials, and plugin configuration have not been revalidated for current releases. Consult the official Graylog documentation and vendor release/support matrix before adopting or upgrading. The example exposes port 9000 over plaintext HTTP; only use this on an isolated, trusted test network. For a real deployment, terminate HTTPS with a trusted reverse proxy (or supported native TLS), tightly restrict management access, and never forward port 9000 to the public internet. Internal HTTP service-to-service URLs in the isolated Docker network are not public external links.
Graylog SIEM deployment guide - covering installation, input configuration, stream processing, alerting, dashboards, and log management for a self-hosted open-source SIEM alternative.
Covers: Graylog server and MongoDB/OpenSearch setup, GELF/Syslog/Beats input configuration, stream routing and processing pipelines, alert conditions and notifications, Graylog dashboards, index rotation/retention, and content pack installation.
Deploy Graylog as a centralized log management and alerting platform for security operations, with stream-based routing that separates security-relevant logs from operational noise.
- Building a self-hosted SIEM that's lighter-weight than the full ELK stack
- Centralizing syslog from network devices, Linux servers, and Windows Beats
- Setting up alert-based detection for specific log patterns
- Log management and retention for compliance requirements
Graylog is an open-source log management platform designed for collecting, indexing, and analyzing log data. It combines the power of Elasticsearch (or OpenSearch) for storage with an intuitive web interface for search and visualization. Graylog is lighter weight than ELK and offers a more streamlined experience for log aggregation and SIEM use cases.
This guide covers deploying Graylog using Docker and configuring it to receive logs from various sources.
| Feature | Graylog | ELK Stack |
|---|---|---|
| Setup Complexity | Lower | Higher |
| Resource Usage | Lighter | Heavier |
| Web Interface | Purpose-built | Kibana (general purpose) |
| Alerting | Built-in (even in free) | Requires configuration |
| Stream Processing | Native | Via Logstash |
| Learning Curve | Gentler | Steeper |
| Feature | Open (Free) | Operations | Security |
|---|---|---|---|
| Log Collection | โ | โ | โ |
| Alerting | โ | โ | โ |
| Dashboards | โ | โ | โ |
| LDAP/AD Auth | โ | โ | โ |
| Archiving | โ | โ | โ |
| Anomaly Detection | โ | โ | โ |
| SIEM Features | โ | โ | โ |
| Audit Logging | โ | โ | โ |
For homelab/learning: Graylog Open is excellent and free.
| Component | Minimum | Recommended |
|---|---|---|
| OS | Ubuntu 20.04/22.04 LTS | Ubuntu 22.04 LTS |
| RAM | 4 GB | 8 GB+ |
| CPU | 2 vCPUs | 4 vCPUs |
| Storage | 50 GB | 200 GB+ SSD |
Graylog requires three components:
| Component | Purpose |
|---|---|
| MongoDB | Stores configuration and metadata |
| OpenSearch/Elasticsearch | Stores and indexes log messages |
| Graylog Server | Processing, web interface, API |
| Port | Service | Purpose |
|---|---|---|
| 9000 | Graylog Web | Web interface & API |
| 1514 | Graylog | Syslog TCP input |
| 1514/udp | Graylog | Syslog UDP input |
| 5044 | Graylog | Beats input |
| 12201 | Graylog | GELF TCP input |
| 12201/udp | Graylog | GELF UDP input |
| 9200 | OpenSearch | Search engine (internal) |
| 27017 | MongoDB | Database (internal) |
sudo apt update && sudo apt upgrade -y# Install dependencies
sudo apt install -y apt-transport-https ca-certificates curl gnupg lsb-release
# Add Docker GPG key
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg
# Add Docker repository
echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
# Install Docker
sudo apt update
sudo apt install -y docker-ce docker-ce-cli containerd.io docker-compose-plugin
# Add user to docker group
sudo usermod -aG docker $USER
newgrp docker# Increase virtual memory for OpenSearch
sudo sysctl -w vm.max_map_count=262144
echo "vm.max_map_count=262144" | sudo tee -a /etc/sysctl.conf
sudo sysctl -pmkdir -p ~/graylog/{data,config}
mkdir -p ~/graylog/data/{mongodb,opensearch,graylog}
cd ~/graylogGraylog requires a password_secret (for encryption) and a root_password_sha2 (admin password hash).
# Generate password secret (minimum 16 characters)
pwgen -N 1 -s 96
# Hash your admin password. The prompt does not echo and nothing is written to
# shell history. Choose a long, unique password; never reuse a sample value.
read -rsp "Graylog admin password: " GL_ADMIN_PW; echo
printf '%s' "$GL_ADMIN_PW" | sha256sum | cut -d" " -f1
unset GL_ADMIN_PWSave both values for the next step.
Note: This guide pins
graylog/graylog:5.2andopensearchproject/opensearch:2.12.0for a known-good config. Graylog does not support OpenSearch 3.0+ (it will break your instance) - check the Graylog compatibility matrix before bumping either version.
Create docker-compose.yml:
version: '3.8'
services:
# MongoDB for Graylog configuration storage
mongodb:
image: mongo:6.0
container_name: graylog-mongodb
volumes:
- mongodb_data:/data/db
networks:
- graylog-network
restart: unless-stopped
# OpenSearch for log storage and indexing
opensearch:
image: opensearchproject/opensearch:2.12.0
container_name: graylog-opensearch
environment:
- cluster.name=graylog-cluster
- node.name=opensearch-node1
- discovery.type=single-node
- bootstrap.memory_lock=true
- "OPENSEARCH_JAVA_OPTS=-Xms2g -Xmx2g"
- DISABLE_SECURITY_PLUGIN=true
- DISABLE_INSTALL_DEMO_CONFIG=true
ulimits:
memlock:
soft: -1
hard: -1
nofile:
soft: 65535
hard: 65535
volumes:
- opensearch_data:/usr/share/opensearch/data
networks:
- graylog-network
restart: unless-stopped
# Graylog Server
graylog:
image: graylog/graylog:5.2
container_name: graylog
environment:
# CHANGE THESE VALUES
- GRAYLOG_PASSWORD_SECRET=<YOUR_PASSWORD_SECRET_HERE>
- GRAYLOG_ROOT_PASSWORD_SHA2=<YOUR_SHA256_HASH_HERE>
- GRAYLOG_HTTP_EXTERNAL_URI=http://<YOUR_SERVER_IP>:9000/
# MongoDB connection
- GRAYLOG_MONGODB_URI=mongodb://mongodb:27017/graylog
# OpenSearch connection
- GRAYLOG_ELASTICSEARCH_HOSTS=http://opensearch:9200
# Timezone
- GRAYLOG_ROOT_TIMEZONE=America/Los_Angeles
# Email (optional)
# - GRAYLOG_TRANSPORT_EMAIL_ENABLED=true
# - GRAYLOG_TRANSPORT_EMAIL_HOSTNAME=smtp.example.com
# - GRAYLOG_TRANSPORT_EMAIL_PORT=587
# - GRAYLOG_TRANSPORT_EMAIL_USE_AUTH=true
# - GRAYLOG_TRANSPORT_EMAIL_AUTH_USERNAME=user@example.com
# - GRAYLOG_TRANSPORT_EMAIL_AUTH_PASSWORD=<smtp-app-password>
entrypoint: /usr/bin/tini -- wait-for-it opensearch:9200 -- /docker-entrypoint.sh
volumes:
- graylog_data:/usr/share/graylog/data
networks:
- graylog-network
depends_on:
- mongodb
- opensearch
ports:
# Graylog web interface and REST API
- "9000:9000"
# Syslog TCP
- "1514:1514"
# Syslog UDP
- "1514:1514/udp"
# GELF TCP
- "12201:12201"
# GELF UDP
- "12201:12201/udp"
# Beats
- "5044:5044"
restart: unless-stopped
volumes:
mongodb_data:
opensearch_data:
graylog_data:
networks:
graylog-network:
driver: bridgeInstead of inline environment variables, create .env:
# Graylog Configuration - use the values you generated in Step 2.1.
# Do not copy sample values: a published password hash is a published password.
GRAYLOG_PASSWORD_SECRET=<output of: pwgen -N 1 -s 96>
GRAYLOG_ROOT_PASSWORD_SHA2=<sha256 hash of YOUR admin password>
GRAYLOG_HTTP_EXTERNAL_URI=http://192.168.1.50:9000/
GRAYLOG_ROOT_TIMEZONE=America/Los_AngelesUpdate docker-compose.yml to use the env file:
graylog:
env_file:
- .env# Start all services
docker compose up -d
# Monitor startup (wait for "Graylog server up and running")
docker compose logs -f graylogStartup typically takes 1-2 minutes.
Open your browser:
http://<SERVER-IP>:9000
Default Credentials:
- Username:
admin - Password: The password you hashed in Step 2.1
sudo ufw allow 9000/tcp comment "Graylog Web UI"
sudo ufw allow 1514/tcp comment "Graylog Syslog TCP"
sudo ufw allow 1514/udp comment "Graylog Syslog UDP"
sudo ufw allow 5044/tcp comment "Graylog Beats"
sudo ufw allow 12201/tcp comment "Graylog GELF TCP"
sudo ufw allow 12201/udp comment "Graylog GELF UDP"
sudo ufw reloadsudo firewall-cmd --permanent --add-port=9000/tcp
sudo firewall-cmd --permanent --add-port=1514/tcp
sudo firewall-cmd --permanent --add-port=1514/udp
sudo firewall-cmd --permanent --add-port=5044/tcp
sudo firewall-cmd --permanent --add-port=12201/tcp
sudo firewall-cmd --permanent --add-port=12201/udp
sudo firewall-cmd --reloadGraylog uses "Inputs" to receive log data. Configure these via the web interface.
- Navigate to System โ Inputs
- Select Syslog UDP from the dropdown
- Click Launch new input
- Configure:
- Node: Select your Graylog node
- Title:
Syslog UDP - Bind address:
0.0.0.0 - Port:
1514
- Click Save
- Select Syslog TCP from dropdown
- Click Launch new input
- Configure:
- Title:
Syslog TCP - Bind address:
0.0.0.0 - Port:
1514
- Title:
- Click Save
For Winlogbeat/Filebeat:
- Select Beats from dropdown
- Click Launch new input
- Configure:
- Title:
Beats Input - Bind address:
0.0.0.0 - Port:
5044
- Title:
- Click Save
GELF (Graylog Extended Log Format) supports structured logging:
- Select GELF UDP from dropdown
- Click Launch new input
- Configure:
- Title:
GELF UDP - Bind address:
0.0.0.0 - Port:
12201
- Title:
- Click Save
After creating inputs, they should show as "RUNNING" with a green indicator.
Streams route messages based on rules. Think of them as filters that categorize incoming logs.
- Navigate to Streams
- Click Create Stream
- Configure:
- Title:
Windows Events - Description:
All Windows Event Log messages - Index Set: Default
- Title:
- Click Save
- Click Manage Rules for the new stream
- Add Rule:
- Field:
source - Type:
match regular expression - Value:
.*(or specific hostname pattern) - Inverted: No
- Field:
- Click Save
- Click Start Stream (on the Streams page)
| Stream Name | Rule Field | Rule Type | Rule Value |
|---|---|---|---|
| Linux Syslog | facility |
match exactly |
local0 through local7
|
| Network Devices | source |
match regular expression |
^(switch|router|fw).* |
| Sysmon Events | winlog_channel |
match exactly |
Microsoft-Windows-Sysmon/Operational |
| Authentication | EventID |
match exactly |
4624 or 4625
|
Pipelines process and enrich messages.
- Navigate to System โ Pipelines
- Click Manage rules โ Create Rule
- Create a rule to extract fields:
rule "Extract Windows EventID"
when
has_field("EventID")
then
let event_id = to_string($message.EventID);
set_field("event_id_string", event_id);
end
- Create a Pipeline:
- Click Manage pipelines โ Add new pipeline
- Name:
Windows Processing - Connect to stream:
Windows Events
- Add the rule to a stage in the pipeline
rule "GeoIP Lookup"
when
has_field("src_ip") AND NOT cidr_match("10.0.0.0/8", to_ip($message.src_ip))
then
let geo = geoip_lookup(to_string($message.src_ip));
set_field("src_geo_country", geo["country"]["iso_code"]);
set_field("src_geo_city", geo["city"]["name"]);
end
# Download Winlogbeat
$version = "8.12.0"
Invoke-WebRequest -Uri "https://artifacts.elastic.co/downloads/beats/winlogbeat/winlogbeat-$version-windows-x86_64.zip" -OutFile "$env:TEMP\winlogbeat.zip"
# Extract
Expand-Archive -Path "$env:TEMP\winlogbeat.zip" -DestinationPath "C:\Program Files"
Rename-Item "C:\Program Files\winlogbeat-$version-windows-x86_64" "C:\Program Files\Winlogbeat"Edit C:\Program Files\Winlogbeat\winlogbeat.yml:
winlogbeat.event_logs:
- name: Security
event_id: 4624, 4625, 4634, 4648, 4672, 4688, 4697, 4698, 4720, 4726, 4728, 4732, 4756, 4768, 4769, 4776
ignore_older: 72h
- name: System
event_id: 7045, 7040, 1074, 6005, 6006
ignore_older: 72h
- name: Microsoft-Windows-Sysmon/Operational
ignore_older: 72h
- name: Microsoft-Windows-PowerShell/Operational
event_id: 4103, 4104
ignore_older: 72h
processors:
- add_host_metadata: ~
# Output to Graylog Beats input
output.logstash:
hosts: ["<GRAYLOG-SERVER-IP>:5044"]
logging.level: info
logging.to_files: true
logging.files:
path: C:\ProgramData\winlogbeat\logs
name: winlogbeat
keepfiles: 7cd "C:\Program Files\Winlogbeat"
# Test configuration
.\winlogbeat.exe test config -e
# Install service
.\install-service-winlogbeat.ps1
# Start service
Start-Service winlogbeatEdit /etc/rsyslog.d/60-graylog.conf:
# Forward all logs to Graylog via UDP
*.* @<GRAYLOG-SERVER-IP>:1514;RSYSLOG_SyslogProtocol23Format
# Or via TCP (more reliable)
*.* @@<GRAYLOG-SERVER-IP>:1514;RSYSLOG_SyslogProtocol23FormatRestart rsyslog:
sudo systemctl restart rsyslog# Install Filebeat
curl -L -O https://artifacts.elastic.co/downloads/beats/filebeat/filebeat-8.12.0-amd64.deb
sudo dpkg -i filebeat-8.12.0-amd64.debConfigure /etc/filebeat/filebeat.yml:
filebeat.inputs:
- type: log
enabled: true
paths:
- /var/log/syslog
- /var/log/auth.log
- /var/log/secure
fields:
log_type: syslog
- type: log
enabled: true
paths:
- /var/log/audit/audit.log
fields:
log_type: audit
output.logstash:
hosts: ["<GRAYLOG-SERVER-IP>:5044"]Start Filebeat:
sudo systemctl enable filebeat
sudo systemctl start filebeatConfigure Docker to send logs directly to Graylog:
# Run container with GELF logging
docker run --log-driver=gelf \
--log-opt gelf-address=udp://<GRAYLOG-SERVER-IP>:12201 \
--log-opt tag="{{.Name}}" \
nginxOr in docker-compose.yml:
services:
webapp:
image: nginx
logging:
driver: gelf
options:
gelf-address: "udp://<GRAYLOG-SERVER-IP>:12201"
tag: "webapp"# Simple keyword search
error
# Field-specific search
source:webserver
# Wildcards
source:web*
# Boolean operators
error AND source:webserver
error OR warning
NOT debug
# Phrases
"authentication failed"
# Ranges
http_response_code:[400 TO 599]
timestamp:["2024-01-01 00:00:00" TO "2024-01-31 23:59:59"]
# Exists check
_exists_:user_id
EventID:4625
EventID:4624
EventID:1 AND winlog_channel:"Microsoft-Windows-Sysmon/Operational"
EventID:4104 OR (EventID:1 AND Image:*powershell*)
EventID:3 AND NOT DestinationIp:10.* AND NOT DestinationIp:192.168.*
EventID:1 AND (Image:*cmd.exe OR Image:*powershell.exe) AND ParentImage:*WINWORD.EXE
- Run your search
- Click Save (bookmark icon)
- Name your search
- Access from Search โ Saved Searches
- Navigate to Dashboards
- Click Create new dashboard
- Name:
Security Overview - Click Create
- Click Edit on dashboard
- Click Create
- Select Aggregation
- Configure:
- Visualization: Line Chart or Area Chart
- Rows: timestamp (Date Histogram)
- Metrics: count()
- Click Create
- Click Create
- Select Aggregation
- Configure:
- Visualization: Data Table
- Rows: source (Terms)
- Metrics: count()
- Sort: By metric, Descending
- Click Create
- Click Create
- Configure:
- Search Query:
EventID:(4624 OR 4625) - Visualization: Pie Chart
- Rows: EventID (Terms)
- Metrics: count()
- Search Query:
- Click Create
- Configure:
- Search Query:
EventID:4625 AND _exists_:src_geo_country - Visualization: World Map
- Rows: src_geo_country
- Metrics: count()
- Search Query:
Graylog Content Packs can provide pre-built dashboards. Check System โ Content Packs for available options.
- Navigate to Alerts โ Event Definitions
- Click Create Event Definition
Step 1: Event Details
- Title:
Multiple Failed Logins - Description:
Alerts when multiple login failures from same source - Priority:
High
Step 2: Condition
- Condition Type: Aggregation
- Search Query:
EventID:4625 - Streams: (Select your Windows stream)
- Group by:
sourceORIpAddress - Search within:
5 minutes - Execute every:
1 minute - Create alert when: count() >= 5
Step 3: Fields (optional) Add fields to include in the alert.
Step 4: Notifications
- Add notification (email, HTTP, Slack, etc.)
Condition:
- Search Query:
EventID:1 AND Image:*powershell* AND (CommandLine:*-enc* OR CommandLine:*downloadstring* OR CommandLine:*bypass*) - Create alert when: count() > 0
- Navigate to System โ Configurations โ Notification Settings
- Or set via environment variables:
# In docker-compose.yml
- GRAYLOG_TRANSPORT_EMAIL_ENABLED=true
- GRAYLOG_TRANSPORT_EMAIL_HOSTNAME=smtp.gmail.com
- GRAYLOG_TRANSPORT_EMAIL_PORT=587
- GRAYLOG_TRANSPORT_EMAIL_USE_AUTH=true
- GRAYLOG_TRANSPORT_EMAIL_USE_TLS=true
- GRAYLOG_TRANSPORT_EMAIL_AUTH_USERNAME=your@gmail.com
- GRAYLOG_TRANSPORT_EMAIL_AUTH_PASSWORD=<smtp-app-password>
- GRAYLOG_TRANSPORT_EMAIL_FROM_EMAIL=graylog@yourdomain.com- Navigate to Alerts โ Notifications
- Click Create Notification
- Select Slack Notification
- Configure webhook URL and channel
- Navigate to System โ Indices
- Click Create Index Set
- Configure:
- Title:
Security Logs - Index prefix:
security - Index rotation: Time-based (e.g., Daily)
- Retention: Delete after X indices
- Title:
| Strategy | Description | Use Case |
|---|---|---|
| Delete | Remove old indices | Limited storage |
| Close | Close but keep on disk | Occasional access needed |
| Archive | Move to cold storage | Compliance requirements |
- Click on an Index Set
- Click Edit
- Set rotation strategy:
- Time-based: Rotate daily/weekly
- Size-based: Rotate at X GB
- Set retention:
- Index count: Keep last N indices
- Time: Keep indices for X days
- Navigate to System โ Indices
- View index status (green/yellow/red)
- Check index size and document count
# Create certificate directory
mkdir -p ~/graylog/certs
# Generate self-signed certificate
openssl req -x509 -nodes -days 365 -newkey rsa:2048 \
-keyout ~/graylog/certs/graylog.key \
-out ~/graylog/certs/graylog.crt \
-subj "/CN=graylog.local"
# Create PKCS12 keystore (the export password is read from the environment so
# it does not appear in the process list or shell history)
read -rsp "Keystore export password: " P12_PASSWORD; echo; export P12_PASSWORD
openssl pkcs12 -export -in ~/graylog/certs/graylog.crt \
-inkey ~/graylog/certs/graylog.key \
-out ~/graylog/certs/graylog.p12 \
-name graylog -passout env:P12_PASSWORD
unset P12_PASSWORDgraylog:
volumes:
- ~/graylog/certs:/usr/share/graylog/data/certs:ro
environment:
- GRAYLOG_HTTP_ENABLE_TLS=true
- GRAYLOG_HTTP_TLS_CERT_FILE=/usr/share/graylog/data/certs/graylog.crt
- GRAYLOG_HTTP_TLS_KEY_FILE=/usr/share/graylog/data/certs/graylog.key
- GRAYLOG_HTTP_EXTERNAL_URI=https://<YOUR_SERVER_IP>:9000/- Navigate to System โ Authentication โ Authenticators
- Click Create Authenticator
- Select LDAP
- Configure:
- Server URL:
ldap://dc.example.com:389 - System Username:
CN=svc_graylog,OU=Service Accounts,DC=example,DC=com - System Password: (password)
- Search Base DN:
OU=Users,DC=example,DC=com - User Search Pattern:
(&(objectClass=user)(sAMAccountName={0}))
- Server URL:
- Map LDAP groups to Graylog roles
- Navigate to System โ Authentication โ Roles
- Create custom roles:
- Security Analyst: Read access to security streams
- Admin: Full access
- Auditor: Read-only to all
Check logs:
docker compose logs graylogCommon issues:
| Error | Solution |
|---|---|
waiting for opensearch |
Wait longer or check OpenSearch logs |
Password secret too short |
Ensure 16+ character secret |
Invalid MongoDB URI |
Check MongoDB is running |
No master |
OpenSearch cluster issue |
-
Check inputs are running:
- Navigate to System โ Inputs
- Verify status shows "RUNNING"
-
Test syslog connectivity:
# Send test message
echo "<14>Test message from $(hostname)" | nc -u -w1 <GRAYLOG-IP> 1514
logger -n <GRAYLOG-IP> -P 1514 "Test message"- Check Graylog logs:
docker compose logs -f graylog | grep -i "received"- Check time range: Default is 5 minutes
- Check stream selection: Messages may be in different stream
- Verify index: System โ Indices - check document count
- Check for processing errors: System โ Processing Status
# Reduce OpenSearch heap
# In docker-compose.yml, change:
- "OPENSEARCH_JAVA_OPTS=-Xms1g -Xmx1g"- Add field indexes to frequently searched fields
- Reduce time range of searches
- Use more specific queries
- Consider upgrading hardware
Content Packs bundle inputs, extractors, streams, and dashboards:
| Command | Purpose |
|---|---|
docker compose up -d |
Start stack |
docker compose down |
Stop stack |
docker compose logs -f graylog |
Follow Graylog logs |
docker compose restart graylog |
Restart Graylog only |
docker compose exec graylog bash |
Shell into container |
| Endpoint | Purpose |
|---|---|
GET /api/system |
System overview |
GET /api/system/inputs |
List inputs |
GET /api/streams |
List streams |
GET /api/search/universal/relative |
Execute search |
Example API call:
curl --user admin "http://localhost:9000/api/system/overview" # prompts for the password| Port | Protocol | Input Type |
|---|---|---|
| 1514 | TCP/UDP | Syslog |
| 5044 | TCP | Beats |
| 12201 | TCP/UDP | GELF |
| 5555 | TCP | Raw plaintext |
| Operator | Example | Description |
|---|---|---|
AND |
error AND nginx |
Both terms |
OR |
error OR warning |
Either term |
NOT |
NOT debug |
Exclude term |
"" |
"exact phrase" |
Exact match |
* |
fail* |
Wildcard |
: |
source:server1 |
Field match |
[] |
level:[1 TO 5] |
Range |
_exists_: |
_exists_:user |
Field exists |
| Variable | Purpose | Example |
|---|---|---|
GRAYLOG_PASSWORD_SECRET |
Encryption key | 96 character string |
GRAYLOG_ROOT_PASSWORD_SHA2 |
Admin password hash | SHA256 hash |
GRAYLOG_HTTP_EXTERNAL_URI |
External URL | http://ip:9000/ |
GRAYLOG_MONGODB_URI |
MongoDB connection | mongodb://host:27017/graylog |
GRAYLOG_ELASTICSEARCH_HOSTS |
OpenSearch URL | http://opensearch:9200 |
GRAYLOG_ROOT_TIMEZONE |
Server timezone | America/New_York |
Part of the Incident Response & Log Aggregation Branch
- ../README.md - IncidentResponse section index
- elk_stack.md - ELK Stack SIEM alternative
- wazuh.md - Wazuh for endpoint detection that feeds Graylog
- splunk.md - Commercial SIEM comparison
- ../../Homelab/HomeLab_Setup.md - Homelab context
๐ Source: IncidentResponse/SIEM/graylog.md | โ๏ธ Suggest an edit | โฌ
๏ธ Back to Incident Response
- ๐บ๏ธ Browse by Topic
- ๐ All Repository Files
- ๐งญ Learning Paths
- ๐ Master Guide
- ๐ค Glossary
- โ๏ธ Legal & Disclaimer
๐ Foundations & Learning
๐ก๏ธ Defense & Investigations
- Incident Response
- Open Source Intelligence (OSINT)
- Reverse Engineering
- Operations Security (OPSEC)
- Compliance
โ๏ธ Platforms & Infrastructure
๐ก Hardware, Wireless & Field Projects
- PNWC Cyberdeck
- Hardware Testing
- Hardware Hacking
- Software-Defined Radio
- Wardriving
- uConsole
- Space Security
๐งฐ Assessment & Field Reference
๐ฆ Downloads & Project Resources
๐๏ธ Additional Topics