Diagnosing High Response Times Due to New Relic Daemon Timeout

If you're experiencing consistent 15-second response times across your application endpoints, particularly after service restarts or deployments, this may be due to New Relic daemon connection timeout settings. Symptoms Consistent response times of approximately 15 seconds across multiple endpoints High time_starttransfer values in curl tests Issues persist after service restarts Problem occurs even for local requests within the same pod Common Causes This issue typically occurs when: New Relic account has been cancelled or downgraded New Relic daemon cannot establish connection but timeout is set The application container includes New Relic configuration with connection timeouts How to Verify Check your Dockerfile or container configuration for New Relic timeout settings, particularly looking for: newrelic.daemon.app_connect_timeout=15s Resolution If you are no longer using New Relic or have downgraded your account, you should either: Remove the New Relic configuration and agent from your application Update the New Relic configuration to reflect your current subscription level Disable New Relic monitoring if it's not needed If you still need application monitoring, consider configuring an alternative monitoring solution before removing New Relic.