-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
chore: Fix linter findings for errorlint (part4) #12723
Conversation
Download PR build artifacts for linux_amd64.tar.gz, darwin_amd64.tar.gz, and windows_amd64.zip. 📦 Click here to get additional PR build artifactsArtifact URLs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks @zak-pawel!
Co-authored-by: Pawel Zak <Pawel Zak> (cherry picked from commit 312fb04)
@zak-pawel Does it have anything to do with not getting a metrics for an hour? |
@edeno1 I have no idea. Could you elaborate on this? Is there any issue? |
@zak-pawel I take metrics in cloudwatch and send them via http to prometheus remote write Lately every day I don't see metrics for an hour and then it comes back this thing affects me a lot because I issue alerts in real time with these metrics
|
@edeno1 how is that in any way related to these linter fixes? |
@edeno1 Can you create separate issue in which you provide Telegraf version, logs and describe everything? |
@zak-pawel yes |
Address findings for errorlint - finds code that can cause problems with the error wrapping scheme introduced in Go 1.13.
It is only part of the bigger job.
After all findings in whole project are handled, we can enable
errorlint
linter to guard this.Following findings in
plugins/inputs/[a-e]*
packages were fixed: