Skip to content

Conversation

@nason
Copy link
Contributor

@nason nason commented Jan 24, 2017

No description provided.

Copy link
Contributor

@mattjstar mattjstar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

export default function ClientLogentriesLogger({ name, token }) {
try {
// If a LE logger does not exist with this name, this will throw
LE.to(name);
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This goes down this path: https://github.com/rapid7/le_js/blob/master/src/le.js#L342

The issue we're seeing comes from the init call being made for every logger instance (including children) when a logentries token is present. This was introduced by the refactor in #68

@coveralls
Copy link

Coverage Status

Coverage remained the same at 77.66% when pulling 754b6e8 on logentries-fix into 7be8ddd on master.

Copy link
Contributor

@i8ramin i8ramin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure I fully understand the nature of this change, but I trust ya.

@nason nason merged commit de636ab into master Jan 24, 2017
@nason nason deleted the logentries-fix branch January 24, 2017 17:15
@nason
Copy link
Contributor Author

nason commented Jan 24, 2017

@i8ramin we're seeing this error when we have logentries configured:

screen shot 2017-01-24 at 12 17 36 pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants