Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ignored Nan and Infinite float values #73

Merged
merged 4 commits into from
Sep 2, 2020
Merged

Conversation

jorik
Copy link
Contributor

@jorik jorik commented Sep 1, 2020

These values cannot be handled by NRDB, and POMI currently logs an error message for every single NaN/Infinite value it processes, which can be confusing.

These values cannot be handled by NRDB, and POMI currently logs an error message for every single NaN/Infinite value it processes, which can be confusing.
@jorik jorik requested a review from ardias September 1, 2020 10:22
Copy link
Member

@paologallinaharbur paologallinaharbur left a comment

Choose a reason for hiding this comment

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

LGTM! thanks for the change!

if err != nil {
return nil, errors.Wrap(err, "could not create new Harvester")
}

// Wrap the harvester so we can filter out invalid float values: NaN and Infinity.
// If we do send them, the harvester will always output these as errors
h = harvesterDecorator{h}
Copy link
Member

Choose a reason for hiding this comment

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

nice approach!

Copy link
Member

@paologallinaharbur paologallinaharbur left a comment

Choose a reason for hiding this comment

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

LGTM, Thanks for the update!

@jorik jorik merged commit 339c78b into main Sep 2, 2020
@jorik jorik deleted the feature/remove-nan-errors branch September 2, 2020 08:50
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.

2 participants