syslog-release v11.7.9

What's Changed

• Truncate overly long fields by @Benjamintf1 in #73

Full Changelog: v11.7.8...v11.7.9

syslog-release v11.7.8

What's Changed

• Bump to go 1.18.1
• As part of bumping to Go 1.18 certificates that are signed with the SHA-1 hash function will no longer be accepted.
• Change syslog library to loggregator library rather then papertrail. Should cause no changes.

New Contributors

• @ctlong made their first contribution in #70

Full Changelog: v11.7.7...v11.7.8

syslog-release v11.7.7

• bump-golang to v0.94.0

✨ Built with golang 1.17.5

⚠️ IPv4 addresses containing decimal components with leading zeros will be rejected

With the upgrade to Go 1.17, the ParseIP and ParseCIDR functions now reject IPv4 addresses which contain decimal components with leading zeros.

Ensure that for configuring a syslog_forwarder, and elsewhere, the address does not contain leading zeros if it is an IP address.

For more information on the context of this change, please refer to the Go 1.17 release notes.

syslog-release v11.7.6

• update blackbox to include performance fixes.

syslog-release v11.7.5

Changelog

• Update Golang version

✨ Built with golang 1.16.4

v11.7.0

Changelog

• Human-readable timestamp

BOSH property changes

• Added syslog_forwarder.logging.format.timestamp

GO Version: 1.15.2

v11.6.1

• update golang

v11.6.0

• Bump Golang for CVE-2019-17596

v11.5.0

• syslog.max_message_size is now a configurable property. The default value is 8k.
• syslog.blackbox.log_filename property configures blackbox to tag its log lines with the filename. Default will not include filename.
• Adds a parsable logstash filter that makes log messages more filterable by processing inner JSON and ensuring timestamps are human readable.
• Bump golang to address glang CVE-2019-16276

v11.4.0

Quick on the heels of our previous release, we've got two new features.

• syslog.filter_legacy_vcap_messages, a off-by-default feature that addresses log duplication caused by Cloud Foundry Application Runtime releases that use tee to send logs directly to rsyslog and to a file on the disk, where blackbox now picks them up. This should eliminate the need for a custom rule that manifest maintainers have needed to maintain to avoid massive log volume. We may switch this to on-by-default at some point in the future, but that will be a breaking change with attendant major version bump if/when we do.
• syslog.heuristically_filter_debug_messages, another off-by-default feature to address log volume. This one targets debug logs, but since the PRI field does not actually reflect the priority in the logs we're interested in, we have to use a text-matching heuristic. Manifest maintainers have historically needed to either maintain a rule doing much the same thing, or manually set, for instance, UAA's logging level to INFO from its default of DEBUG. For those that cannot or do not wish to change UAA's logging behavior, this property should be helpful, though it will not eliminate all DEBUG-like messages from all components, and will drop some DEBUG logs from any other components that happen to emit them, as well.

See the spec for the syslog_forwarder job for details on these new properties.