You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have multiple ESPv2 services in my Kubernetes cluster. A those services generate logs by each kubernetes readiness or liveness prove and for each google global load balancer liveness prove.
Because I have multiple of these solutions running in the same cluster, the cluster generate a lot of GET /healthz logs. downloaded-logs-20221104-122130.csv
In conclusion, my problem is that I can't bypass the GET /healthz logs, and those logs don't add value to my troubleshooting, otherwise those logs create unnecessary cost and unnecessary cognitive load.
Please I ask for your help to reduce my logs costs, by skipping those logs in the ESPv2 container.
thanks.
The text was updated successfully, but these errors were encountered:
I have multiple ESPv2 services in my Kubernetes cluster. A those services generate logs by each kubernetes readiness or liveness prove and for each google global load balancer liveness prove.
Because I have multiple of these solutions running in the same cluster, the cluster generate a lot of GET /healthz logs.
downloaded-logs-20221104-122130.csv
In conclusion, my problem is that I can't bypass the GET /healthz logs, and those logs don't add value to my troubleshooting, otherwise those logs create unnecessary cost and unnecessary cognitive load.
Please I ask for your help to reduce my logs costs, by skipping those logs in the ESPv2 container.
thanks.
The text was updated successfully, but these errors were encountered: