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

Added PHC-related logs #3036

Merged
merged 1 commit into from
Apr 23, 2024
Merged

Added PHC-related logs #3036

merged 1 commit into from
Apr 23, 2024

Conversation

RomanZavodskikh
Copy link
Member

Signed-off-by: Roman Zavodskikh roman.zavodskikh@zalando.de

@RomanZavodskikh RomanZavodskikh marked this pull request as ready for review April 22, 2024 16:40
@RomanZavodskikh RomanZavodskikh added the minor no risk changes, for example new filters label Apr 22, 2024
proxy/healthy_endpoints.go Outdated Show resolved Hide resolved
routing/endpointregistry.go Outdated Show resolved Hide resolved
@@ -21,7 +21,8 @@ func (h *healthyEndpoints) filterHealthyEndpoints(endpoints []routing.LBEndpoint
filtered := make([]routing.LBEndpoint, 0, len(endpoints))
for _, e := range endpoints {
if p < e.Metrics.HealthCheckDropProbability() {
/* drop */
ctx.Logger().Infof("dropping endpoint %q due to passive health check: p=%0.2f, dropProbability=%0.2f",
Copy link
Member

Choose a reason for hiding this comment

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

maybe use normal logrus? No need to pass it I mean

Copy link
Member Author

Choose a reason for hiding this comment

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

I still would like to have ctx.Logger() here: after #2269 it has useful feature, it adds traceId inside log entry. It may be very helpful to see the relation between trace and log entry during debugging.

proxy/proxy.go Outdated Show resolved Hide resolved
@AlexanderYastrebov
Copy link
Member

My concern is that we can flood logs with this. Lets try but we need to keep an eye and may need to disable/move to debug level these logs.

@RomanZavodskikh
Copy link
Member Author

RomanZavodskikh commented Apr 23, 2024

My concern is that we can flood logs with this. Lets try but we need to keep an eye and may need to disable/move to debug level these logs.

We discussed this topic in the meeting:

  • the logs will be written only in case some endpoint will have non-zero failed round trips ratio, not all the time
  • if there will be too many logs, we will change the mode to the Debug

Signed-off-by: Roman Zavodskikh <roman.zavodskikh@zalando.de>
@RomanZavodskikh
Copy link
Member Author

👍

1 similar comment
@szuecs
Copy link
Member

szuecs commented Apr 23, 2024

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
minor no risk changes, for example new filters
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants