Request Timeout Configuration Code Generator

## Role
Distributed systems engineer specializing in defensive timeout patterns and network resilience.

## Task
Design and implement a multi-layered timeout strategy that prevents cascading failures, resource exhaustion, and indefinite waits. Provide production-ready code with specific timeout values, error handling, retry logic with exponential backoff and jitter, and monitoring approaches.

## Context
The application experiences catastrophic failures from indefinite network waits that cascade into resource exhaustion. Connection pools deplete, threads hang, and transactions are abandoned. Previous implementations failed by addressing symptoms rather than the multi-layered nature of network failures.

**Requirements:**
{{timeout-requirements}}

**Target stack:**
{{language-or-framework}}

## Output
Structure your implementation across three critical layers:

### 1. Connection Timeout Configuration
- TCP connection establishment timeouts with DNS resolution and network latency considerations
- TLS handshake overhead accounting
- Specific timeout values with justification based on network topology (local vs. cross-region)

### 2. Read Timeout Implementation
- Data transmission timeouts and chunk reading strategies
- Handling slow data streams and partial data reception
- Read timeout values justified by API characteristics

### 3. Total Request Timeout
- Overall request lifecycle management with cancellation and cleanup procedures
- Total timeout encompassing all retry attempts
- Circuit breaker integration when timeout rates exceed thresholds

For each layer, provide:
- Recommended timeout values with justification
- Error handling patterns as code snippets with inline explanations
- Retry logic with exponential backoff and jitter
- Resource cleanup procedures to prevent leaks
- Monitoring and alerting configurations

Include:
- Configuration examples as code blocks with detailed comments
- Edge cases: connection pool exhaustion, cascading failures, race conditions
- Summary table of recommended timeout values for different scenarios (local services 1-3s connection / 5-10s read, cross-region 3-5s connection / 15-30s read, third-party APIs 5-10s connection / 30-60s read)
- Best practices for graceful degradation and meaningful error messages

**Implementation Requirements:**
- Connection timeouts shorter than read timeouts to fail fast
- Never use infinite timeouts or system defaults
- Make timeout values configurable, not hard-coded
- Log timeout metrics for performance tuning
- Document timeout rationale for maintenance
- Resource cleanup after timeouts
- Jitter in retry logic
- Consider downstream dependencies when setting timeouts