v1.0.7

[K0lin]

Release: Caddy Support Added

We're excited to announce the latest update to LogLynx, now with full support for Caddy access logs!

What's New

✨ Caddy Integration

• New Parser: Added dedicated parser for Caddy JSON access logs
• Auto-Discovery: Automatic detection of Caddy log files in standard locations
• Configuration: New CADDY_LOG_PATH environment variable for custom log paths
• Comprehensive Parsing: Extracts all relevant fields from Caddy logs including:
  • Client information (IP, port, user ID)
  • Request details (method, host, path, query, headers)
  • Response data (status, size, content type, timing)
  • TLS information (version, cipher, server name)
  • Upstream/backend details

Compatibility

LogLynx now supports:

• Pangolin (Docker Compose setup)
• Traefik (JSON and CLF formats)
• Caddy (JSON format)

Technical Details

• Parser detects Caddy logs by checking for logger field containing "http.log.access"
• Supports all standard Caddy JSON log fields
• Handles client IP fallback from X-Forwarded-For headers
• Converts TLS version and cipher codes to human-readable names
• Extracts upstream information for backend analysis

Migration

No breaking changes. Existing Traefik and Pangolin configurations continue to work unchanged. Simply add your Caddy log path to start monitoring Caddy traffic.

Feedback

As always, we welcome feedback and contributions! If you encounter any issues with Caddy log parsing or have suggestions for improvements, please open an issue on GitHub.

---

What's Changed

• feat: add support for Caddy access logs by @K0lin in feat: add support for Caddy access logs #53

Full Changelog: v1.0.6...v1.0.7

---

This discussion was created from the release v1.0.7.