Skip to content

config: change log level to debug#3738

Merged
htuch merged 1 commit intoenvoyproxy:masterfrom
ramaraochavali:fix/log_level
Jun 27, 2018
Merged

config: change log level to debug#3738
htuch merged 1 commit intoenvoyproxy:masterfrom
ramaraochavali:fix/log_level

Conversation

@ramaraochavali
Copy link
Contributor

Signed-off-by: Rama rama.rao@salesforce.com

Description: Changes the log level to debug when management server is not reachable.
Risk Level: Low
Testing: Current tests
Docs Changes: None
Release Notes: NA
Fixes #3733

Signed-off-by: Rama <rama.rao@salesforce.com>
if (e == nullptr) {
stats_.update_failure_.inc();
ENVOY_LOG(warn, "gRPC update for {} failed", type_url_);
ENVOY_LOG(debug, "gRPC update for {} failed", type_url_);
Copy link
Member

Choose a reason for hiding this comment

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

Can you distinguish between the very first update and alter updates? In particular, I think we should warn when a management server is unreachable etc. but not during normal disconnects (e.g. gRPC load shed).

Copy link
Contributor Author

@ramaraochavali ramaraochavali Jun 27, 2018

Choose a reason for hiding this comment

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

If it is not unreachable during Envoy startup, we get the following warning already
[2018-06-27 13:47:24.884][27][warning][upstream] source/common/config/grpc_mux_impl.cc:235] gRPC config stream closed: 14, upstream connect error or disconnect/reset before headers

Is this sufficient? or are you thinking of some thing else?

If we do not use ADS, individual xDS apis may be still logging this for first unreachability also?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ok. So do you want this to be warn till at least one successful update has happened or one update attempt? Based on that, I think we can evaluate the corresponding stat and distinguish between debug and warn.

Copy link
Member

Choose a reason for hiding this comment

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

OK, seems fine then if we are already observing a connection level warning.

@htuch htuch self-assigned this Jun 27, 2018
@htuch htuch merged commit 4e0b252 into envoyproxy:master Jun 27, 2018
@ramaraochavali ramaraochavali deleted the fix/log_level branch June 28, 2018 03:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants