Puppet is a software configuration management tool which includes its own declarative language to describe system configuration. Deploy this integration to send logs from your Puppet applications to your Logz,io account.
Before you begin, you’ll need:
Download the Logz.io public certificate to your credentials 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/AAACertificateServices.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.
<<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)-
- Log location (JSON format)-
- Default log type -
Defaults for Puppet server access logs:
- Log location (plain text format) -
- Log location (JSON format) -
- Default log type -
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.
<<LISTENER-HOST>> with the host for your region. For example,
listener.logz.io if your account is hosted on AWS US East, or
listener-nl.logz.io if hosted on Azure West Europe.
# ... output.logstash: hosts: ["<<LISTENER-HOST>>:5015"] ssl: certificate_authorities: ['/etc/pki/tls/certs/COMODORSADomainValidationSecureServerCA.crt']
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.