envoy.http.downstream.request.total

Total downstream HTTP requests

Dimensions:None

Technical Annotations (22)

Configuration Parameters (4)

retry.perRetry.backOff.baseIntervalrecommended: 1s or greater

0s causes proto validation failure and complete route rejection

concurrencyrecommended: 2

Worker threads for services under 1000 RPS via proxy.istio.io/config annotation or meshConfig.defaultConfig

accessLogging.disabledrecommended: true

Disables access logging in Telemetry resource to reduce CPU

tracing.disableSpanReportingrecommended: true

Disables span reporting in Telemetry resource to reduce CPU

Error Signatures (6)

5xxhttp status

route_not_foundlog pattern

Proto constraint validation failedlog pattern

value must be greater than 0slog pattern

RouteConfigurationValidationErrorexception

RetryBackOffValidationError.BaseIntervalexception

CLI Commands (1)

kubectl exec -it deploy/my-app -c istio-proxy -- curl -s localhost:15000/stats | grep "server.concurrency\|server.total_connections"

diagnostic

Technical References (11)

BackendTrafficPolicycomponentHTTPRoutecomponentdynamic_route_configscomponentxDSprotocolRouteConfigurationcomponentenvoy-gatewaycomponentworker threadsconceptevent loopconceptTelemetry resourcecomponenttagOverridescomponentVirtualServicecomponent

Related Insights (5)

High 5xx error rate indicates upstream instability or misconfigurationcritical

▸

BackendTrafficPolicy with baseInterval: 0s causes all routes to return 404critical

▸

Excessive worker threads cause unnecessary baseline CPU consumptionwarning

▸

Telemetry collection consumes excessive CPU per requestwarning

▸

Complex routing rules with regex are expensive per requestinfo

▸