- Functionbeat Reference:
- Overview
- Getting Started With Functionbeat
- Setting up and running Functionbeat
- Configuring Functionbeat
- Configure functions
- 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 the Kibana endpoint
- Load the Elasticsearch index template
- Configure logging
- Use environment variables in the configuration
- YAML tips and gotchas
- Regular expression support
- functionbeat.reference.yml
- Exported fields
- Monitoring Functionbeat
- Securing Functionbeat
- Troubleshooting
This functionality is in beta and is subject to change. The design and code is
less mature than official GA features and is being provided as-is with no
warranties. Beta features are not subject to the support SLA of official GA
features.
Debug
edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.
Debug
editBy default, Functionbeat sends all its output to syslog. When you run Functionbeat in
the foreground, you can use the -e command line flag to redirect the output to
standard error instead. For example:
functionbeat -e
The default configuration file is functionbeat.yml (the location of the file varies by
platform). You can use a different configuration file by specifying the -c flag. For example:
functionbeat -e -c myfunctionbeatconfig.yml
You can increase the verbosity of debug messages by enabling one or more debug
selectors. For example, to view the published transactions, you can start Functionbeat
with the publish selector like this:
functionbeat -e -d "publish"
If you want all the debugging output (fair warning, it’s quite a lot), you can
use *, like this:
functionbeat -e -d "*"
Was this helpful?
Thank you for your feedback.