Configuration
Before you begin, you’ll need:
- Filebeat 7 or Filebeat 6
- Root access
- Port 5015 open
Download the Logz.io public certificate to your Filebeat server
For HTTPS shipping, download the Logz.io public certificate to your certificate authority folder.
sudo curl https://raw.githubusercontent.com/logzio/public-certificates/master/AAACertificateServices.crt --create-dirs -o /etc/pki/tls/certs/COMODORSADomainValidationSecureServerCA.crt
Add Puppet as an input
In the Filebeat configuration file (/etc/filebeat/filebeat.yml), add Puppet to the filebeat.inputs section.
We recommend configuring Puppet to output JSON logs. See Advanced Logging Configuration from Puppet for more information.
Replace <<LOG-SHIPPING-TOKEN>>
with the token of the account you want to ship to.
# ...
filebeat.inputs:
- type: log
paths:
# If you configured Puppet to output JSON logs, replace the filename with
# `puppetserver.log.json`
- /var/log/puppetlabs/puppetserver/puppetserver.log
fields:
# If you configured Puppet to output JSON logs, set logzio_codec to
# `json`
logzio_codec: plain
# You can manage your tokens at
# https://app.logz.io/#/dashboard/settings/manage-tokens/log-shipping
token: <<LOG-SHIPPING-TOKEN>>
type: puppetserver
fields_under_root: true
encoding: utf-8
ignore_older: 3h
- type: log
paths:
# If you configured Puppet to output JSON logs, replace the filename with
# `puppetserver-access.log.json`
- /var/log/puppetlabs/puppetserver/puppetserver-access.log
fields:
# If you configured Puppet to output JSON logs, set logzio_codec to
# `json`
logzio_codec: plain
# You can manage your tokens at
# https://app.logz.io/#/dashboard/settings/manage-tokens/log-shipping
token: <<LOG-SHIPPING-TOKEN>>
type: puppetserver-access
fields_under_root: true
encoding: utf-8
ignore_older: 3h
If you’re running Filebeat 7, paste this code block. Otherwise, you can leave it out.
# ... For Filebeat 7 only ...
filebeat.registry.path: /var/lib/filebeat
processors:
- rename:
fields:
- from: "agent"
to: "filebeat_agent"
ignore_missing: true
- rename:
fields:
- from: "log.file.path"
to: "source"
ignore_missing: true
If you’re running Filebeat 6, paste this code block.
# ... For Filebeat 6 only ...
registry_file: /var/lib/filebeat/registry
The above assumes the following defaults for Puppet server logs:
- Log location (plain text format)-
/var/log/puppetlabs/puppetserver/puppetserver.log
- Log location (JSON format)-
/var/log/puppetlabs/puppetserver/puppetserver.log.json
- Default log type -
puppetserver
Defaults for Puppet server access logs:
- Log location (plain text format) -
/var/log/puppetlabs/puppetserver/puppetserver-access.log
- Log location (JSON format) -
/var/log/puppetlabs/puppetserver/puppetserver-access.log.json
- Default log type -
puppetserver-access
Puppet produces lots of different logs. Learn more from Puppet Labs Docs 🔗.
Set Logz.io as the output
If Logz.io is not an output, add it now. Remove all other outputs.
Replace <<LISTENER-HOST>>
with your region’s listener host (for example, listener.logz.io
). For more information on finding your account’s region, see Account region.
# ...
output.logstash:
hosts: ["<<LISTENER-HOST>>:5015"]
ssl:
certificate_authorities: ['/etc/pki/tls/certs/COMODORSADomainValidationSecureServerCA.crt']
Start Filebeat
Start or restart Filebeat for the changes to take effect.
Check Logz.io for your logs
Give your logs some time to get from your system to ours, and then open Kibana. You can search for type:puppetserver-access OR puppetserver
to filter for your logs. Your logs should be already parsed thanks to the Logz.io preconfigured parsing pipeline.
If you still don’t see your logs, see log shipping troubleshooting.