feat(core): Add Health Check and Structured Logging #152

New issue

Open

opened 2026-01-28 13:02:33 +00:00 by chartgerink · 0 comments

chartgerink commented

2026-01-28 13:02:33 +00:00

Owner

Adding a few production-ready touches to make it easier to monitor and debug in staging and production would be helpful.

✅ Goals

Add a simple /health (or /ping) endpoint so Docker and load balancers can check liveness.
Replace println!-style logs with structured JSON logging using tracing + tracing-subscriber.
Optional: add /version to track which commit is deployed.

🛠 Why?

Health checks help orchestration (Docker/K8s) know if the app is actually ready.
Structured logs are way easier to parse and search in tools like Grafana, Loki, or even jq.
Knowing the version helps us debug issues across deploys.

📦 Suggested Dependencies

tracing = "0.1"
tracing-subscriber = { version = "0.3", features = ["env-filter", "json"] }

💬 Notes

I’m happy to review or pair on this!

Adding a few production-ready touches to make it easier to monitor and debug in staging and production would be helpful. ## ✅ Goals - Add a simple /health (or /ping) endpoint so Docker and load balancers can check liveness. - Replace println!-style logs with structured JSON logging using tracing + tracing-subscriber. - Optional: add /version to track which commit is deployed. ## 🛠 Why? - Health checks help orchestration (Docker/K8s) know if the app is actually ready. - Structured logs are way easier to parse and search in tools like Grafana, Loki, or even jq. - Knowing the version helps us debug issues across deploys. ## 📦 Suggested Dependencies - tracing = "0.1" - tracing-subscriber = { version = "0.3", features = ["env-filter", "json"] } ## 💬 Notes - I’m happy to review or pair on this!