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.

Sign up for GitHub

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

Jump to bottom

Add logging when monitoring cannot connect #6365

Merged
merged 1 commit into from
Feb 13, 2018
Merged

Add logging when monitoring cannot connect #6365

merged 1 commit into from
Feb 13, 2018

Conversation

ph
Copy link
Contributor

@ph ph commented Feb 12, 2018

Currently when the monitoring can not connect to Elasticsearch no errors
is show in the log making this issue really hard to debug, this change
the behavior to send any error to the log.

Fixes: #6327

@ph ph added libbeat needs_backport PR is waiting to be backported to other branches. labels Feb 12, 2018
@ph
Add logging when monitoring cannot connect
89b02f6 
Currently when the monitoring can not connect to Elasticsearch no errors
is show in the log making this issue really hard to debug, this change
the behavior to send any error to the log.

Fixes: elastic#6327
@ph ph force-pushed the fix/elasticsearch-logging-monitoring branch from f92db0f to 89b02f6 Compare February 12, 2018 22:56
@ph
Copy link
Contributor Author

ph commented Feb 12, 2018

Will show this in the log.

2018-02-12T17:53:33.418-0500    ERROR   elasticsearch/elasticsearch.go:165      Monitoring could not connect to elasticsearch, failed with 401 Unauthorized: {"error":{"root_cause":[{"type":"security_exception","reason":"unable to authenticate user [beats_system] for REST request [/_xpack?filter_path=features.monitoring.enabled]","header":{"WWW-Authenticate":"Basic realm=\"security\" charset=\"UTF-8\""}}],"type":"security_exception","reason":"unable to authenticate user [beats_system] for REST request [/_xpack?filter_path=features.monitoring.enabled]","header":{"WWW-Authenticate":"Basic realm=\"security\" charset=\"UTF-8\""}},"status":401}

@ph ph requested a review from ruflin February 12, 2018 22:58
ruflin
ruflin approved these changes Feb 12, 2018
View reviewed changes
Copy link
Member

@ruflin ruflin left a comment

Choose a reason for hiding this comment

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

WFG

@ruflin ruflin added the review label Feb 12, 2018
@ruflin ruflin merged commit b4c92f8 into elastic:master Feb 13, 2018
ph added a commit to ph/beats that referenced this pull request Feb 13, 2018
@ph
Add logging when monitoring cannot connect (elastic#6365)
640b434 
Currently when the monitoring can not connect to Elasticsearch no errors
is show in the log making this issue really hard to debug, this change
the behavior to send any error to the log.

Fixes: elastic#6327

(cherry picked from commit b4c92f8)
@ph ph mentioned this pull request Feb 13, 2018
Merged
tsg pushed a commit that referenced this pull request Feb 13, 2018
@ph @tsg
Add logging when monitoring cannot connect (#6365) (#6367)
3c9b828 
Currently when the monitoring can not connect to Elasticsearch no errors
is show in the log making this issue really hard to debug, this change
the behavior to send any error to the log.

Fixes: #6327

(cherry picked from commit b4c92f8)
@ph ph removed the needs_backport PR is waiting to be backported to other branches. label Apr 4, 2018
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
@ph @tsg
Add logging when monitoring cannot connect (elastic#6365) (elastic#6367)
33ba403 
Currently when the monitoring can not connect to Elasticsearch no errors
is show in the log making this issue really hard to debug, this change
the behavior to send any error to the log.

Fixes: elastic#6327

(cherry picked from commit fdfed27)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ruflin ruflin ruflin approved these changes

Assignees
No one assigned
Labels
libbeat review
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@ph @ruflin