- Functionbeat Reference:
- Overview
- Getting Started With Functionbeat
- Setting up and deploying Functionbeat
- Configuring Functionbeat
- Configure functions
- Specify general settings
- Configure the internal queue
- Configure the output
- Configure index lifecycle management
- Specify SSL settings
- Filter and enhance the exported data
- Define processors
- Add cloud metadata
- Add fields
- Add labels
- Add the local time zone
- Add tags
- Decode JSON fields
- Decode Base64 fields
- Decompress gzip fields
- Community ID Network Flow Hash
- Convert
- Drop events
- Drop fields from events
- Extract array
- Keep fields from events
- Registered Domain
- Rename fields from events
- Add Kubernetes metadata
- Add Docker metadata
- Add Host metadata
- Add Observer metadata
- Dissect strings
- DNS Reverse Lookup
- Add process metadata
- Parse data by using ingest node
- Enrich events with geoIP information
- Configure 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
- Get help
- Debug
- Common problems
- Deployment to AWS fails with "failed to create the stack"
- Deployment to AWS fails with "resource limit exceeded"
- Error loading config file
- Found unexpected or unknown characters
- Logstash connection doesn’t work
- @metadata is missing in Logstash
- Not sure whether to use Logstash or Beats
- SSL client fails to connect to Logstash
- Monitoring UI shows fewer Beats than expected
A newer version is available. For the latest information, see the
current release documentation.
Debug
editDebug
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.