Elastic Heartbeat Configuration

Monitor the status of hosts at set intervals using ICMP, TCP, and HTTP.

Follow the steps below to send your observability data to Logit.io

Logs

Heartbeat is a lightweight shipping agent used to monitor the health of services running on the host. The results can then be shipped to one or more destinations, including Logstash.

Install Integration

Please click on the Install Integration button to configure your stack for this source.

Install Heartbeat

To get started first follow the steps below:

Install heartbeat (opens in a new tab)
Root access
Verify the required port @logstash.sslPort is open

Older versions can be found here: heartbeat 7 (opens in a new tab), heartbeat 6 (opens in a new tab), heartbeat 5 (opens in a new tab)

Locate the configuration file

/etc/heartbeat/heartbeat.yml

Configure the monitors

The following example shows a basic configuration for each of the three different types of monitors, ICMP, TCP, and HTTP.

Copy the contents below and paste this into the heartbeat.yml file at line 39

# Configure monitors inline
heartbeat.monitors:
  - type: http
    # Set enabled to true (or delete the following line) to enable this monitor
    enabled: true
    # ID used to uniquely identify this monitor in Elasticsearch even if the config changes
    id: my-monitor
    # Human readable display name for this service in Uptime UI and elsewhere
    name: My Monitor
    # List of URLs to query
    urls: ["https://logit.io"]
    # Configure task schedule
    schedule: '@every 10s'
 
# Other examples for icmp, tcp and http
# heartbeat.monitors:
#   - type: icmp
#     schedule: '@every 5s'
#     hosts: ["myhost"]
#   - type: tcp
#     schedule: '@every 5s'
#     hosts: ["myhost:7"]  # default TCP Echo Protocol
#     check.send: "Check"
#     check.receive: "Check"
#   - type: http
#     schedule: '@every 5s'
#     urls: ["http://localhost:80/service/status"]
#     check.response.status: 200
# heartbeat.scheduler:
#   limit: 10

There's also a full example configuration file called heartbeat.reference.yml that shows all the possible options.

Configure Output

We'll be shipping to Logstash so that we have the option to run filters before the data is indexed.
Comment out the elasticsearch output block.

## Comment out elasticsearch output
#output.elasticsearch:
#  hosts: ["localhost:9200"]

Uncomment and change the logstash output to match below:

output.logstash:
  hosts: ["@logstash.host:@logstash.sslPort"]
  loadbalance: true
  ssl.enabled: true

Validate Configuration

In the directory where Filebeat is installed, run the following command to validate the installation:

.\@beatname.exe test config -c @beatname.yml

If the yml file is invalid, @beatname will print a description of the error. For example, if the output.logstash section was missing, @beatname would print no outputs are defined, please define one under the output section

Start Heartbeat

 sudo systemctl enable heartbeat
 sudo systemctl start heartbeat

Check Logit.io for your logs

Data should now have been sent to your Stack.

View My Data

If you don't see take a look at How to diagnose no data in Stack below for how to diagnose common issues.

How to diagnose no data in Stack

If you don't see data appearing in your stack after following this integration, take a look at the troubleshooting guide for steps to diagnose and resolve the problem or contact our support team and we'll be happy to assist.

Heartbeat Logging Overview

Heartbeat is a lightweight shipping agent created by Elastic as part of their Beats group of log shippers. Compared to other tools in the Beats family, such as Metricbeat & Winlogbeat, Heartbeat is a relatively new addition to the Elastic Stack.

Heartbeat is the only member of the Beats family that Elastic recommends you to install on a separate network/machine to the one you are currently wishing to monitor.

Heartbeat was created to allow observability of the health of services running on the host (this includes uptime monitoring functionality as standard). These results can then be shipped to one or more destinations, including Logstash.

Heartbeat supports HTTP, ICMP and TCP protocols for monitoring service availability.

If you need to keep a close eye on uptime for the purposes of complying with your company's service level agreement (SLA) then you'll find that Heartbeat is integral for monitoring these instances based on the URLs & metrics you supply to the application, prior to indexing. This feedback can be triggered based on the custom schedule you select during configuration.

If you need any further assistance with migrating your Heartbeat data to Logstash we're here to help you get started. Feel free to reach out by contacting our support team by visiting our dedicated Help Centre or via live chat & we'll be happy to assist.

Hashicorp Vault Heroku