blumeops/docs/changelog.d/fix-real-client-ip-logging.bugfix.md at 3415cad38c6c2977fe1e1ceb81e2f1fbb1b95eeb - eblume/blumeops - Forgejo: Beyond coding. We Forge.

eblume/blumeops

Erich Blume 3415cad38c

Deploy Fly.io Proxy / deploy (push) Successful in 59s

Details

Log real client IPs via Fly-Client-IP header (#130 )

## Summary
- Add `client_ip` field to the Fly.io nginx JSON log format, sourced from `Fly-Client-IP` header
- Extract `client_ip` in the Alloy pipeline so it's available as a parsed field in Loki
- Keeps `remote_addr` (the internal proxy IP) for debugging

Fixes: Grafana access logs for docs.eblu.me showing 172.16.11.178 for every request instead of real visitor IPs.

## Deployment and Testing
- [ ] Deploy updated fly.io proxy: `fly deploy` from `fly/` directory
- [ ] Verify in Grafana that new log lines include `client_ip` with real IPs
- [ ] Confirm `remote_addr` still shows the proxy IP (preserved for debugging)

Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/130

2026-02-09 11:02:06 -08:00

1 line

122 B

Markdown

Raw Blame History

Log real client IPs in Fly.io proxy access logs using Fly-Client-IP header instead of showing the internal proxy address.