-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Remove global logp calls from libbeat/kibana and libbeat/template #18258
Conversation
Pinging @elastic/integrations-services (Team:Services) |
💚 Build SucceededExpand to view the summary
Build stats
Test stats 🧪
|
libbeat/kibana/client.go
Outdated
@@ -271,7 +274,7 @@ func (client *Client) ImportJSON(url string, params url.Values, jsonBody map[str | |||
|
|||
body, err := json.Marshal(jsonBody) | |||
if err != nil { | |||
logp.Err("Failed to json encode body (%v): %#v", err, jsonBody) | |||
client.log.Errorf("Failed to json encode body (%v): %#v", err, jsonBody) |
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.
I wonder if this log is redundant. The error returned also contains the original error message. The jsonBody maybe we always want to log at debug level?
Would it make sense to add debug logs to other places? E.g. before and after a request is send?
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.
I've just run setup --dashboards
with debug logging. It prints which dashboard it is loading and if there is an error it is logged, too. I think that should be enough.
25eaa04
to
0f52f74
Compare
Thanks! |
No description provided.