I'm a lumberjack and I'm ok! I sleep when idle, then I ship logs all day!
I parse your logs, I eat the JVM agent for lunch!
(This project was recently renamed from 'lumberjack' to 'logstash-forwarder' to
make its intended use clear. The 'lumberjack' name now remains as the network
protocol, and 'logstash-forwarder' is the name of the program. It's still the
same lovely log forwarding program you love.)
If you want to run logstash-forwarder, add to /etc/rc.conf
logstash_forwarder_enable="YES"
Do not forget to edit your configuration file:
Default: ${PREFIX}/etc/logstash-forwarder.conf
Key points
You'll need an SSL CA to verify the server (host) with.
You can specify custom fields for each set of paths in the config file.
Any number of these may be specified. I use them to set fields like type
and other custom attributes relevant to each log.
Generating an ssl certificate
Logstash supports all certificates, including self-signed certificates.
To generate a certificate, you can run the following command:
$ openssl req -x509 -batch -nodes -newkey rsa:2048 -keyout \
logstash-forwarder.key -out logstash-forwarder.crt -days 365
This will generate a key at logstash-forwarder.key and the 1-year valid
certificate at logstash-forwarder.crt. Both the server that is running
logstash-forwarder as well as the logstash instances receiving logs will
require these files on disk to verify the authenticity of messages.
PROTECT YOUR KEYS!
all: Bump PORTREVISION after lang/go119 update
Direct commit to quarterly to bump Go ports revisions after 61a665d2d8d2
Approved by: ports-secteam (blanket)
all: Bump PORTREVISION after lang/go119 update
Direct commit to quarterly to bump Go ports revisions after f30271912e48
Approved by: riggs (ports-secteam)
