How sadsfae/ansible-elk works
Main Components
a) Server-side Components:
• Elasticsearch (Core Database)
• Logstash/Fluentd (Log Processing)
• Kibana (Visualization Interface)
• Nginx/Apache (Reverse Proxy)
• X-Pack (Optional Security Layer)
• Curator (Optional Index Management)
b) Client-side Components:
• Filebeat (Log Shipping)
• Metricbeat (System Metrics)
• Packetbeat (Network Data)
• Heartbeat (Uptime Monitoring)
[Client Layer]
• ↑
[Transport Layer]
• ↑
[Processing Layer]
• ↑
[Storage Layer]
• ↑
[Visualization Layer]
Key Elements
a) Data Flow:
• Log data flow from clients to server
• SSL/TLS encryption paths
• Ports for different services (configurable in group_vars/all.yml)
b) Component Relationships:
• Client-Server communication
• Internal component dependencies
• Authentication flows
Specific Implementation Details
• Nginx/Apache reverse proxy (port 80/8080) → Kibana
• Filebeat → Logstash/Fluentd (SSL-encrypted)
• Elasticsearch cluster configuration
• X-Pack security wrapper (if enabled)
• Curator maintenance workflows
• Alternative paths for Fluentd vs Logstash
Component Grouping
Related components:
[ELK Server Group]
• Elasticsearch (Storage)
• Logstash/Fluentd (Processing)
• Kibana (UI)
• Nginx/Apache (Proxy)
• X-Pack (Security)
• Curator (Maintenance)
[Client Group]
• Filebeat
• Metricbeat
• Packetbeat
• Heartbeat
• RSyslog (if using Fluentd)