Using Elastic 7.9 version with 7.9 beats (EFK self managed). Monitoring AWS-EC2 instances
Question:
- Can I just use System Module using Metric beats or
- AWS EC2 module is required
Can you please suggest/comment what module is best pros/cons
Metricbeat.yml for reference below
metricbeat.config.modules:
# Glob pattern for configuration loading
path: /etc/metricbeat/modules.d/*.yml
# Set to true to enable config reloading
reload.enabled: false
# Period on which files under path should be checked for changes
#reload.period: 10s
metricbeat.modules:
- module: aws
period: 300s
metricsets:
- ec2
access_key_id: '***************'
secret_access_key: '*******************'
enabled: true
#- module: system
# metricsets:
# - cpu # CPU usage
# - load # CPU load averages
# - memory # Memory usage
# - network # Network IO
# - process # Per process metrics
# - process_summary # Process summary
# - uptime # System Uptime
# - socket_summary # Socket summary
# - core # Per CPU core usage
# - diskio # Disk IO
# - filesystem # File system usage for each mountpoint
# - fsstat # File system summary metrics
# - raid # Raid
# - socket # Sockets and connection info (linux only)
# - service # systemd service information
# enabled: true
# period: 10s
# processes: ['.*']
# Configure the metric types that are included by these metricsets.
cpu.metrics: ["percentages","normalized_percentages"] # The other available option is ticks.
# core.metrics: ["percentages"] # The other available option is ticks.
output.logstash:
# The FluentD hosts
hosts: ["dev-hr-fd.mycompany.in:5044"]