- Journalbeat Reference for 6.5-7.15:
- Overview
- Getting started with Journalbeat
- Setting up and running Journalbeat
- Configuring Journalbeat
- Configure inputs
- Specify general settings
- Configure the internal queue
- Configure the output
- Set up index lifecycle management
- 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 Elasticsearch index template
- Configure logging
- Use environment variables in the configuration
- YAML tips and gotchas
- Regular expression support
- HTTP Endpoint
- journalbeat.reference.yml
- Exported fields
- Monitoring Journalbeat
- Securing Journalbeat
- Troubleshooting
This functionality is experimental and may be changed or removed completely in a
future release. Elastic will take a best effort approach to fix any issues, but
experimental features are not subject to the support SLA of official GA
features.
Stopping Journalbeat
editStopping Journalbeat
editAn orderly shutdown of Journalbeat ensures that it has a chance to clean up and close outstanding resources. You can help ensure an orderly shutdown by stopping Journalbeat properly.
If you’re running Journalbeat as a service, you can stop it via the service management functionality provided by your installation.
If you’re running Journalbeat directly in the console, you can stop it by entering Ctrl-C. Alternatively, send SIGTERM to the Journalbeat process on a POSIX system.
Was this helpful?
Thank you for your feedback.