- Bump to v1.0.0
- Add support for validating max message bytes
- Add CWLogsWritable#reduceOversizedMessage method to allow custom handling of oversized messages to reduce their size.
- Add CWLogsWritable#event:oversizeLogEvent event that is fired for messages that are dropped due to their size.
- Change CWLogsWritable#getMessageSize to accurately measure the byte size if the estimate puts it over the max size.
- Change CWLogsWritable#dequeueNextLogBatch to drop log events if:
- getMessageSize returns a size for the message that is over the limit, and...
- Passing the message through reduceOversizedMessage does not reduce the message to fit within the limit.
- Fix determining log "message" size not handling multi-byte chars [#13]
- Fix error thrown if no 'error' event listeners on stream [#15]
Breaking Changes:
- Remove
CWLogsWritable#nextLogBatchSizein favor of CWLogsWritable#dequeueNextLogBatch
Non-Breaking Changes:
- Add CWLogsWritable#dequeueNextLogBatch to get the next batch of log events,
and also handle chronological limits of PutLogEvents API call [#2]
- Batch of log events must be in chronological order by timestamp
- Batch of log events cannot exceed 24 hours
- Add live tests for chronological limits of PutLogEvents
- Add options for auto-handling common AWS errors [#10][#12]
- Add code coverage support (including coveralls)
- Add missing CWLogsWritable test for internal filter method
- Change logGroupName/logStreamName props to be writable [#11]
- Fix CWLogsWritable test for error handling
- Add optional "safe-json-stringify" NPM dependency
- Add CWLogsWritable#safeStringifyLogEvent protected method
- Add CWLogsWritable#event:stringifyError event
- Change CWLogsWritable#createLogEvent to call
CWLogsWritable#event:safeStringifyLogEvent to safely stringify
non-string log events. Circular references are replaced with
"[Circular]"and any other errors will fire a CWLogsWritable#stringifyError event.
- Initial version