Design Structured JSON Logging for a Healthcare Rails Monolith
Overview
What this challenge is about.
Design a structured JSON logging migration for a healthcare Rails monolith and earn a verifiable certificate.
The scenario
The company sells patient-intake software to ambulatory (outpatient) clinics across the United States and must satisfy HIPAA, the federal law governing protected health information. Its engineering surface is a single Ruby on Rails monolith maintained by a small backend team that also carries the on-call pager.
The Brief
What you'll do, and what you'll demonstrate.
Design a migration from plain-text Rails logs to structured JSON logs that redact protected health information at the source and feed a Loki ingest path without causing label-cardinality blow-up.
Earning criteria — what you'll demonstrate
- Design a log schema that simultaneously serves debugging (on-call) and audit (compliance) audiences
- Implement redaction by field convention so protected health information never leaves the application process
- Choose Loki labels that keep cardinality low while preserving useful query dimensions
- Build a Promtail-based ingest path from a Rails monolith into Loki and Grafana
- Write operator documentation that lets two audiences independently verify and tune a logging system
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Aligned coursework coming soon.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
- Structured Logging
Apply structured logging to solve real industry problems and demonstrate production-level capability.
- Loki
Apply loki to solve real industry problems and demonstrate production-level capability.
- Phi Redaction
Apply phi redaction to solve real industry problems and demonstrate production-level capability.
- Observability
Apply observability to solve real industry problems and demonstrate production-level capability.
- Label Cardinality
Apply label cardinality to solve real industry problems and demonstrate production-level capability.
- Compliance
Apply compliance to solve real industry problems and demonstrate production-level capability.
Careers
Career paths this challenge builds toward
Completing this challenge demonstrates skills that transfer directly to these roles:
Backend Engineer (Observability)
This challenge mirrors the daily work of an observability-focused backend engineer: shaping log schemas, wiring ingest pipelines, and protecting query systems from cardinality blow-up. You leave able to take a noisy monolith from plain text to structured, queryable telemetry.
This challenge sharpens
- structured-logging
- loki
- observability
Platform Engineer
Platform engineers own the logging and metrics stack that every team depends on. By designing a Promtail-to-Loki ingest path and a defensible labeling plan, you practice the exact trade-offs between query power and storage cost that platform teams manage in production.
This challenge sharpens
- loki
- label-cardinality
- observability
Healthcare Compliance Engineer
Compliance engineering in regulated health software means proving sensitive data is controlled, not just claiming it. Building source-level redaction with fuzz tests and a verifiable runbook prepares you to demonstrate HIPAA-grade data handling to auditors and on-call staff alike.
This challenge sharpens
- phi-redaction
- compliance
- structured-logging