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

[Metricbeat] migrate postgres to ReporterV2 with new error handling #11636

Conversation

fearful-symmetry
Copy link
Contributor

See #11374

I removed the ReportingFetchV2() calls from TestData(), as WriteEventsReporterV2Error() should check to make sure it has data.

Also cleaned things up so the linters should be happy.

@fearful-symmetry
Copy link
Contributor Author

jenkins, test this

@fearful-symmetry fearful-symmetry force-pushed the migration/mb/reporterv2error/postgres branch from 6fd7b79 to 56fc8ac Compare April 3, 2019 20:30
@@ -42,6 +42,7 @@ func init() {
}
}

//NewModule returns a new instance of the module
Copy link
Member

Choose a reason for hiding this comment

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

Nit: we normally add a space after the //. Applies to few other places.

Thanks for adding the missing doc blocks.

@fearful-symmetry fearful-symmetry merged commit 2ec788f into elastic:master Apr 4, 2019
@fearful-symmetry fearful-symmetry deleted the migration/mb/reporterv2error/postgres branch April 4, 2019 13:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Metricbeat Metricbeat
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants