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

Report collector error messages back to Graylog #301

Merged
merged 3 commits into from
Nov 1, 2018

Conversation

mpfz0r
Copy link
Contributor

@mpfz0r mpfz0r commented Oct 12, 2018

If a collector fails, slurp its stderr and stdout logfiles
and report them back to graylog.
Users can inspect them in the Sidecar status page.

Log validation errors only once.

Fixes Graylog2/graylog2-server#5043

If a collector fails, slurp its stderr and stdout logfiles
and report them back to graylog.
Users can inspect them in the Sidecar status page.

Log validation errors only once.

Fixes Graylog2/graylog2-server#5043
@mariussturm
Copy link
Contributor

Refs Graylog2/graylog2-server#5208

@mpfz0r mpfz0r force-pushed the graylog-issue-5043 branch 2 times, most recently from 046ee7e to 357165e Compare October 30, 2018 12:26
In some cases the collector error messages can be over 10 lines
long. Having it separate allows us to build an uncluttered collector
overview page.
@mariussturm
Copy link
Contributor

verbose_message could also be used for configuration validation to show the raw collector output.

@mariussturm mariussturm merged commit e8d6363 into master Nov 1, 2018
@mariussturm mariussturm deleted the graylog-issue-5043 branch November 1, 2018 11:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants