Stop Packetbeat
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
An orderly shutdown of Packetbeat ensures that it has a chance to clean up and close outstanding resources. You can help ensure an orderly shutdown by stopping Packetbeat properly.
If you’re running Packetbeat as a service, you can stop it via the service management functionality provided by your installation.
If you’re running Packetbeat directly in the console, you can stop it by entering Ctrl-C. Alternatively, send SIGTERM to the Packetbeat process on a POSIX system.