Debug
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
By default, Packetbeat sends all its output to syslog. When you run Packetbeat in the foreground, you can use the -e command line flag to redirect the output to standard error instead. For example:
packetbeat -e
The default configuration file is packetbeat.yml (the location of the file varies by platform). You can use a different configuration file by specifying the -c flag. For example:
packetbeat -e -c mypacketbeatconfig.yml
You can increase the verbosity of debug messages by enabling one or more debug selectors. For example, to view publisher-related messages, start Packetbeat with the publisher selector:
packetbeat -e -d "publisher"
If you want all the debugging output (fair warning, it’s quite a lot), you can use *, like this:
packetbeat -e -d "*"