Goals

• Admin configures maximum sizes for log records or payloads.
• Collector shortens over-long records by simple truncation (may result in invalid JSON or otherwise invalid reccords)
• Resulting log message indicates that some data was truncated or omitted.

Motivation

Some logging target systems have limits on the largest records they can accept, need to keep inside those limits.

Alternatives

Leave the target system to deal with the oversize messages. May lead to log loss.

Acceptance Criteria

Tests to verify over-long messages are reduced correctly (see story)

Risk and Assumptions

Possible performance impact from requirement to measure every message/payload size.

Documentation Considerations

Normal feature docs.