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

expfmt: Don't panic on decoding corrupt data #72

Closed
beorn7 opened this issue Jan 5, 2017 · 0 comments · Fixed by #73
Closed

expfmt: Don't panic on decoding corrupt data #72

beorn7 opened this issue Jan 5, 2017 · 0 comments · Fixed by #73
Assignees
Labels

Comments

@beorn7
Copy link
Member

beorn7 commented Jan 5, 2017

https://github.com/prometheus/common/blob/master/expfmt/decode.go#L182 panics upon an unknown metric family type. This can be triggered by corrupt input data. We should return an error instead to not crash e.g. the whole Prometheus server during ingesting metrics with corrupted data.

@beorn7 beorn7 added the bug label Jan 5, 2017
@beorn7 beorn7 self-assigned this Jan 5, 2017
beorn7 pushed a commit that referenced this issue Jan 8, 2017
This requires callers of `ExtractSamples` to be updated.

Fixes #72
beorn7 pushed a commit that referenced this issue Jan 8, 2017
This requires callers of `ExtractSamples` to be updated.

Fixes #72
@beorn7 beorn7 closed this as completed in #73 Jan 8, 2017
beorn7 pushed a commit to prometheus/prometheus that referenced this issue Jan 9, 2017
gouthamve pushed a commit to gouthamve/common that referenced this issue Jul 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant