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

Feat/more verbose parse error #31

Merged
merged 3 commits into from
Aug 5, 2024

Conversation

itaispiegel
Copy link
Contributor

Description

In our environment we encountered the same error described in #29: our dnsmasq-exporter reports a lease parsing error, and meanwhile we don't have metrics and don't know why this is happening.
I thought that a better handling in this case could be to continue parsing the file while ignore the faulty lease, and reporting the line with the error.
Let me know what you think about this 😄

Copy link

google-cla bot commented Aug 4, 2024

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Copy link
Collaborator

@stapelberg stapelberg left a comment

Choose a reason for hiding this comment

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

Thanks for your PR!

collector/collector.go Outdated Show resolved Hide resolved
@stapelberg stapelberg merged commit 60faf8a into google:main Aug 5, 2024
2 checks passed
@itaispiegel itaispiegel deleted the feat/more-verbose-parse-error branch August 5, 2024 17:55
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