- Heartbeat Reference: other versions:
- Overview
- Getting Started With Heartbeat
- Setting up and running Heartbeat
- Configuring Heartbeat
- Set up monitors
- Specify general settings
- Configure the internal queue
- Configure the output
- Specify SSL settings
- Filter and Enhance the exported data
- Parse data by using ingest node
- Set up project paths
- Set up the Kibana endpoint
- Load the Kibana dashboards
- Load the Elasticsearch index template
- Configure logging
- Use environment variables in the configuration
- YAML tips and gotchas
- Regular expression support
- HTTP Endpoint
- heartbeat.reference.yml
- Exported fields
- Monitoring Heartbeat
- Securing Heartbeat
- Troubleshooting
- Contributing to Beats
This functionality is in beta and is subject to change. The design and
code is considered to be less mature than official GA features. Elastic will
take a best effort approach to fix any issues, but beta features are not
subject to the support SLA of official GA features.
Stopping Heartbeat
editStopping Heartbeat
editAn orderly shutdown of Heartbeat ensures that it has a chance to clean up and close outstanding resources. You can help ensure an orderly shutdown by stopping Heartbeat properly.
If you’re running Heartbeat as a service, you can stop it via the service management functionality provided by your installation.
If you’re running Heartbeat directly in the console, you can stop it by entering Ctrl-C. Alternatively, send SIGTERM to the Heartbeat process on a POSIX system.
Was this helpful?
Thank you for your feedback.