syslog: Add support for SYSLOG_TIMESTAMP #260
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Logspout is currently hardcoded to use RFC3339 timestamps. This can
cause problems when using SYSLOG_FORMAT=rfc3164 because some
old-fashioned syslog servers insist on "Mmm dd hh:mm:ss" format.
Make logspout more flexible by adding support for a SYSLOG_TIMESTAMP
environment variable containing a Go template. This template will be
applied to a SyslogMessage value and defaults to {{.Timestamp}}, so
there is no change to the current behavior.
Legacy "Mmm dd hh:mm:ss" timestamps can now be specified with:
SYSLOG_TIMESTAMP='{{.Time.Format "Jan 02 15:04:05"}}'
Or RFC3339 timestamps with nanosecond precision can be specified with:
SYSLOG_TIMESTAMP='{{.Time.Format "2006-01-02T15:04:05.999999999Z07:00"}}'
billimek
added a commit
to billimek/logspout
that referenced
this pull request
Mar 2, 2017
* upstream/master: Dockerfile: use alpine 3.5 to fix build issue from missing context pkg syslog: Add support for SYSLOG_TIMESTAMP (gliderlabs#260) first pass at tests (gliderlabs#218) install ca-certificates fixes gliderlabs#247 Update README.md
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Logspout is currently hardcoded to use RFC3339 timestamps. This can cause problems when using
SYSLOG_FORMAT=rfc3164because some old-fashioned syslog servers insist on "Mmm dd hh:mm:ss" format.Make logspout more flexible by adding support for a
SYSLOG_TIMESTAMPenvironment variable containing a Go template. This template will be applied to aSyslogMessagevalue and defaults to{{.Timestamp}}, so there is no change to the current behavior.Legacy "Mmm dd hh:mm:ss" timestamps can now be specified with:
Or RFC3339 timestamps with nanosecond precision can be specified with: