Setting Up Log Aggregation
Overview
Deploy centralized log aggregation platforms (ELK Stack, Grafana Loki, Splunk) with ingestion pipelines, structured parsing, retention policies, visualization dashboards, and alerting. Configure log shippers (Filebeat, Promtail, Fluentd) to collect from applications, containers, and system logs with proper security and scalability.
Prerequisites
- Target infrastructure identified: Kubernetes, Docker Compose, or VMs
- Storage requirements calculated: estimate daily log volume and multiply by retention period
- Network connectivity between log sources and aggregation platform (typically ports 9200, 3100, 8088)
- Authentication mechanism defined (LDAP, OAuth, API tokens, or basic auth)
- Resource allocation planned: Elasticsearch needs significant heap memory (minimum 4GB per node)
Instructions
- Select the log aggregation platform: ELK for full-text search and complex queries, Loki for lightweight Kubernetes-native logging, Splunk for enterprise with advanced analytics
- Deploy the storage backend: Elasticsearch cluster, Loki with object storage (S3/GCS), or Splunk indexers
- Configure log shippers on sources: Filebeat for ELK, Promtail for Loki, Fluentd/Fluent Bit for multi-destination
- Define parsing rules: Logstash grok patterns for unstructured logs, JSON parsing for structured logs, multiline handling for stack traces
- Set retention policies: Index Lifecycle Management (ILM) for Elasticsearch, chunk retention for Loki, index rotation for Splunk
- Deploy visualization: Kibana dashboards for ELK, Grafana dashboards for Loki, Splunk Search for Splunk
- Configure alerting: define log-based alerts for error spikes, application exceptions, and security events
- Implement RBAC: restrict dashboard access and log visibility by team and environment
- Test the full pipeline: generate test logs, verify ingestion, confirm parsing, and validate dashboard display
Output
- Docker Compose or Kubernetes manifests for the log aggregation stack
- Log shipper configuration files (Filebeat YAML, Promtail config, Fluentd conf)
- Parsing and field extraction rules (Logstash pipeline, grok patterns)
- Retention policy configuration (ILM, lifecycle rules)
- Dashboard JSON exports for Kibana or Grafana
- Alert rule definitions for error rate monitoring
Error Handling
| Error |
Cause |
Solution |
Elasticsearch heap space exhausted |
JVM heap too small for index volume |
Increase ES_JAVA_OPTS heap size (set to 50% of available RAM, max 32GB) or add nodes |
Cannot connect to Elasticsearch |
Network issue or Elasticsearch not started |
Verify Elasticsearch is running and healthy; check firewall rules and bind address |
Failed to create index |
Disk space full or index template misconfigured |
Check disk usage with df -h; review index template settings and shard allocation |
Failed to parse log line |
Grok pattern mismatch or unexpected log format |
Test grok patterns with Kibana Grok Debugger; add fallback pattern for unmatched lines |
Promtail: too many open files |
System file descriptor limit too low for log tailing |
Increase ulimit -n to 65536; reduce the number of watched paths |
Examples
- "Deploy an ELK stack on Docker Compose with Filebeat collecting Nginx and application logs, Logstash parsing with grok, and a Kibana dashboard for 5xx error monitoring."
- "Set up Loki + Promtail on Kubernetes with 14-day retention, basic auth, and a Grafana dashboard showing logs per namespace."
- "Configure Fluentd to ship logs from 20 application servers to both Elasticsearch (hot storage, 7 days) and S3 (cold storage, 1 year)."
Resources
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: jeremylongshore-claude-code-plugins-plus-skills-setting-up-l3description: Setting Up Log Aggregation4---5# Setting Up Log Aggregation67## Overview89Deploy centralized log aggregation platforms (ELK Stack, Grafana Loki, Splunk) with ingestion pipelines, structured parsing, retention policies, visualization dashboards, and alerting. Configure log shippers (Filebeat, Promtail, Fluentd) to collect from applications, containers, and system logs with proper security and scalability.1011## Prerequisites1213- Target infrastructure identified: Kubernetes, Docker Compose, or VMs14- Storage requirements calculated: estimate daily log volume and multiply by retention period15- Network connectivity between log sources and aggregation platform (typically ports 9200, 3100, 8088)16- Authentication mechanism defined (LDAP, OAuth, API tokens, or basic auth)17- Resource allocation planned: Elasticsearch needs significant heap memory (minimum 4GB per node)1819## Instructions20211. Select the log aggregation platform: ELK for full-text search and complex queries, Loki for lightweight Kubernetes-native logging, Splunk for enterprise with advanced analytics222. Deploy the storage backend: Elasticsearch cluster, Loki with object storage (S3/GCS), or Splunk indexers233. Configure log shippers on sources: Filebeat for ELK, Promtail for Loki, Fluentd/Fluent Bit for multi-destination244. Define parsing rules: Logstash grok patterns for unstructured logs, JSON parsing for structured logs, multiline handling for stack traces255. Set retention policies: Index Lifecycle Management (ILM) for Elasticsearch, chunk retention for Loki, index rotation for Splunk266. Deploy visualization: Kibana dashboards for ELK, Grafana dashboards for Loki, Splunk Search for Splunk277. Configure alerting: define log-based alerts for error spikes, application exceptions, and security events288. Implement RBAC: restrict dashboard access and log visibility by team and environment299. Test the full pipeline: generate test logs, verify ingestion, confirm parsing, and validate dashboard display3031## Output3233- Docker Compose or Kubernetes manifests for the log aggregation stack34- Log shipper configuration files (Filebeat YAML, Promtail config, Fluentd conf)35- Parsing and field extraction rules (Logstash pipeline, grok patterns)36- Retention policy configuration (ILM, lifecycle rules)37- Dashboard JSON exports for Kibana or Grafana38- Alert rule definitions for error rate monitoring3940## Error Handling4142| Error | Cause | Solution |43|-------|-------|---------|44| `Elasticsearch heap space exhausted` | JVM heap too small for index volume | Increase `ES_JAVA_OPTS` heap size (set to 50% of available RAM, max 32GB) or add nodes |45| `Cannot connect to Elasticsearch` | Network issue or Elasticsearch not started | Verify Elasticsearch is running and healthy; check firewall rules and bind address |46| `Failed to create index` | Disk space full or index template misconfigured | Check disk usage with `df -h`; review index template settings and shard allocation |47| `Failed to parse log line` | Grok pattern mismatch or unexpected log format | Test grok patterns with Kibana Grok Debugger; add fallback pattern for unmatched lines |48| `Promtail: too many open files` | System file descriptor limit too low for log tailing | Increase `ulimit -n` to 65536; reduce the number of watched paths |4950## Examples5152- "Deploy an ELK stack on Docker Compose with Filebeat collecting Nginx and application logs, Logstash parsing with grok, and a Kibana dashboard for 5xx error monitoring."53- "Set up Loki + Promtail on Kubernetes with 14-day retention, basic auth, and a Grafana dashboard showing logs per namespace."54- "Configure Fluentd to ship logs from 20 application servers to both Elasticsearch (hot storage, 7 days) and S3 (cold storage, 1 year)."5556## Resources5758- Elastic Stack guide: https://www.elastic.co/guide/59- Grafana Loki: https://grafana.com/docs/loki/latest/60- Fluentd documentation: https://docs.fluentd.org/61- Promtail configuration: https://grafana.com/docs/loki/latest/send-data/promtail/6263---64> Converted and distributed by [TomeVault](https://tomevault.io/claim/jeremylongshore) — claim your Tome and manage your conversions.65<!-- tomevault:4.0:skill_md:2026-04-11 -->
