Heartbeat Configuration

Configuration

This is a example configuration for the Heartbeat. You can use it as a starting point to further define which data you want to gather.

Please be aware of the fact that more data needs more storage space and that you might need to order additional space or bigger instances.

heartbeat.monitors:
- type: icmp
  id: Ping-GoogleDNS
  name: Google DNS
  hosts: ["8.8.8.8"]
  schedule: '@every 60s'

- type: icmp
  id: Ping-InternalDNS
  name: InternalDNS
  hosts: ["1.1.1.1"]
  schedule: '@every 60s'

- type: http
  id: insights.XO
  name: ElasticLogin
  enabled: true
  schedule: '@every 60s'
  hosts: ["ElasticLoginPage"]
  ipv4: true
  ipv6: true
  mode: any
  method: "GET"
  check.response:
    status: [200,301,302]

- type: http
  id: HttpSecondHost
  name: SecondHost
  enabled: true
  schedule: '@every 60s'
  hosts: ["https://YOURWEBSITEHERE"]
  ipv4: true
  ipv6: true
  mode: any
  method: "GET"
  check.response:
    status: [200]

- type: http
  name: "Check xoss API"
  enabled: true
  schedule: '@every 60s'
  hosts: ["xossAPIURL"]
  ipv4: true
  ipv6: true
  mode: any
  method: "GET"
  check.response:
    status: [200]

output.elasticsearch:
  hosts: ["Insights URL"]
  protocol: "HTTP"
  username: "Authentication Name"
  password: "Authentication PW"
  index: "heartbeat"
  xpack.enabled: false
  bulk_max_size: 800
  worker: 2
  compression_level: 9

setup.ilm.enabled: false
setup.ilm.check_exists: false
setup.dashboards.enabled: false
setup.template.enabled: false
setup.template.overwrite: false

processors:
  - add_host_metadata: ~
  - add_cloud_metadata: ~
  - add_docker_metadata: ~
  - add_kubernetes_metadata: ~