sususu98 c41ce77eea fix(logging): add API response timestamp and fix request timestamp timing ...

Previously:
- REQUEST INFO timestamp was captured at log write time (not request arrival)
- API RESPONSE had NO timestamp at all

This fix:
- Captures REQUEST INFO timestamp when request first arrives
- Adds API RESPONSE timestamp when upstream response arrives

Changes:
- Add Timestamp field to RequestInfo, set at middleware initialization
- Set API_RESPONSE_TIMESTAMP in appendAPIResponse() and gemini handler
- Pass timestamps through logging chain to writeNonStreamingLog()
- Add timestamp output to API RESPONSE section

This enables accurate measurement of backend response latency in error logs.

2026-01-29 22:22:18 +08:00

..

gin_logger_test.go

test(logging): add unit tests for GinLogrusRecovery middleware panic handling

2026-01-21 10:57:27 +08:00

gin_logger.go

test(logging): add unit tests for GinLogrusRecovery middleware panic handling

2026-01-21 10:57:27 +08:00

global_logger.go

fix(thinking): update ValidateConfig to include fromSuffix parameter and adjust budget validation logic

2026-01-18 16:37:14 +08:00

log_dir_cleaner_test.go

feat(config): add log file size limit configuration #535

2025-12-20 15:52:59 +08:00

log_dir_cleaner.go

feat(config): add log file size limit configuration #535

2025-12-20 15:52:59 +08:00

request_logger.go

fix(logging): add API response timestamp and fix request timestamp timing

2026-01-29 22:22:18 +08:00

requestid.go

feat(logging): implement request ID tracking and propagation

2025-12-24 08:32:17 +08:00