Use options to add timestamp into meta on each log #31
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
|
Did this ever get looked at? Would be a great addition. |
|
+1 @chrisjhoughton ... wonder if @indexzero could help. |
ducas
changed the title
indexzero
added a commit
that referenced
this pull request
Oct 28, 2015
Use options to add timestamp into meta on each log
|
Did the NPM version get bumped here? Thanks |
OtterCode
pushed a commit
to OtterCode/winston-loggly
that referenced
this pull request
Jun 22, 2018
Update package version
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
When logging lots of data into loggly via winston, it became apparent that the events are not received in the order they are logged. To combat this fact, this change adds a timestamp to the meta for each call to log.