Aggregate Logs & Metrics

Three services each write logs to their own local disk. When an incident spans all three, an engineer has to SSH into every host and grep files by hand, with no unified view and no metrics. Centralize observability.

Context

Centralized logging and metrics ship structured telemetry from every service to one aggregator (e.g. ELK, Loki, a metrics store), queryable through a dashboard. This gives a single view across the system, so incidents are diagnosed without touching individual hosts. It is the foundation of observability that distributed tracing then builds on.

Requirements

•Add a central log/metrics aggregator that all services ship to
•Each service emits structured logs and metrics to the aggregator
•Add a dashboard or query layer on top of the aggregated data

Non-Functional Requirements

•Diagnosing an incident must not require logging into individual hosts

Constraints

•Focus on the aggregation topology — ignore log schema, retention policy, and alerting rules

Evaluation Criteria

Evaluation criteria and weights will be revealed after you submit your solution. This ensures a fair assessment of your design skills.

Ready to solve this challenge?

Draw your architecture diagram, explain your design decisions, and get AI-powered feedback.

For the best experience, design challenges on a desktop or tablet — drawing the architecture on a phone is hard.

Start drawing nowNo account needed to draw. Sign up only to see your score (2 free evaluations).Already have an account? Sign in