gunicorn.requests
Total HTTP requests processedDimensions:None
Technical Annotations (32)
Configuration Parameters (11)
rate_windowrecommended: 5merror_thresholdrecommended: 0.01NEW_RELIC_CONFIG_FILErecommended: newrelic.iniaccesslogrecommended: '-'statsd_prefixrecommended: your_app_namestatsd_hostrecommended: metrics-aggregator:9125worker_connectionsmax_requestsproxy_http_versionrecommended: 1.1proxy_set_header Connectionrecommended: ""workersrecommended: 2*CPU_cores+1Error Signatures (4)
5xxhttp statusstatus=~"5.."log pattern502http status400http statusCLI Commands (3)
pip install newrelicmonitoringnewrelic-admin generate-config YOUR_LICENSE_KEY newrelic.inimonitoringNEW_RELIC_CONFIG_FILE=newrelic.ini newrelic-admin run-program gunicorn myapp.wsgi:applicationmonitoringTechnical References (14)
http_requests_totalcomponentnewrelic-admincomponenttransaction tracesconceptgthreadcomponentkeepaliveconceptSIGTERMconceptmax_requestsconfigurationTransfer-EncodingprotocolRFC 7230protocolCWE-444conceptchunked encodingprotocolHTTP request smugglingconceptreverse proxycomponentOS thrashingconceptRelated Insights (9)
High 5xx error rate indicates service degradationcritical
▸
Gunicorn startup with New Relic APM wrapperinfo
▸
Request logging disabled by default prevents troubleshootingwarning
▸
Multi-process model complicates Prometheus metrics collectioninfo
▸
gthread workers hang at worker_connections limit with keepalive connectionscritical
▸
Automatic worker restarts cause brief 502 errorswarning
▸
Transfer-Encoding header smuggling enables security bypasscritical
▸
Request interpretation desynchronization between proxy and backendcritical
▸
Excessive Gunicorn workers cause OS thrashing and performance degradationwarning
▸