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.
An 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.
Intro to Kibana
ELK for Logs & Metrics