Log-shuttle is an open source UNIX program that delivers messages from applications and daemons to log routers and processors via HTTPs.
One of the motivations behind log-shuttle is to provide a simpler form of encrypted & authenticated log delivery. Using HTTPs & Basic Authentication is simpler than the techniques described in RFC5425. TLS transport mapping for Syslog requires that you maintain both client & server certificates for authentication. In multi-tenant environments, the maintenance of certificate management can be quite burdensome.
When using log-shuttle with logplex it is recommended that you spawn 1 log-shuttle per logplex token. This will isolate data between customers and ensure a good QoS. Log-shuttle accepts input from stdin in a newline (\n) delimited format.
When using log-shuttle with Amazon's Kinesis, all the details for the region, stream and access credentials are supplied in the -logs-url (or $LOGS_URL env variable). See the Kinesis section of this document.
To block as little as possible, log-shuttle will drop outstanding batches if it accumulates > -back-buff amount.
log-shuttle sends data into Kinesis using the PutRecords API call. Each Kinesis record is encoded as length prefixed rfc5424 encoded logs as per rfc6587 (this is the same format logplex accepts). One record per log line.
Log-shuttle expects the following encoding of -logs-url when using Amazon Kinesis:
``` https://<AWS_KEY>:<AWS_SECRET>@kinesis.<AMAZON_REGION>.amazonaws.com/<STREAM NAME> ```
See the Amazon Endpoints documentation for supported regions and hostnames.
Things that should be handled better/things you should know:
STREAM NAMEneed to be properly url encoded.
- log-shuttle assumes a 200 response means everything is good. Kinesis can return a 200, meaning the http request was good, but include per record errors in the response body.
- The maximum number of records in a PutRecords requests is 500, so set the batch size no higher than 498 (500 - 2 records for possible drops / lost).
- Logplex max line length is 10k, Kinesis max record size is 50k of base64
encoded data. A
-max-line-lengthof somewhere less than 37500 should work for Kinesis w/o causing errors.
- Kinesis does not support the -gzip option as that option compresses the body of the request.
- Even with
-kinesis-shards, no guarantees can be made about writing to unique shards.
go get -u github.com/heroku/log-shuttle/...
$GOPATH/bin/log-shuttle should be available.
- dpkg (see also
brew install dpkg)
- go 1.6+
There is a Makefile target named
docker that can be used to build a docker
Hacking on log-shuttle
Fork the repo, hack, submit PRs.
go test -v ./...
- Open an issue on GitHub.
- Keep changes in a feature branch
- Submit PR
Copyright (c) 2013-15 Heroku Inc.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.