How do I approach System Design interview questions?

System Design questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master system design interviews.

What difficulty level is this interview question?

This is a hard difficulty System Design question, commonly asked during Technical Screen rounds at LinkedIn.

What role is this question designed for?

This question is commonly asked for Machine Learning Engineer candidates at LinkedIn during technical interviews.

Design a scalable metrics monitoring system | LinkedIn Interview Question

Quick Overview

This question evaluates the ability to design scalable, multi-tenant metrics monitoring systems, testing competencies in system architecture, ingestion and aggregation pipelines, time-series storage, alerting, capacity planning, and operational observability; it falls under the System Design domain and targets practical, architecture-level application rather than low-level coding. Interviewers commonly ask this to probe reasoning about trade-offs in cloud-native environments—such as collection models, sharding and replication, high-cardinality handling, retention and backfill, and monitoring-the-monitoring—while assessing judgment on reliability, latency, and tenant isolation; this summary is in English.

Design a Metrics Monitoring System for Large-Scale Services

Context

You are designing a metrics monitoring system for large-scale, cloud-native microservices running across multiple regions and clusters. Services are ephemeral (containers/autoscaling), and the platform is multi-tenant (infra teams, ML/feature teams, product services). Assume on the order of tens of thousands of hosts and hundreds of thousands of service instances, with strict SLOs for data freshness and alerting.

Requirements

Compare push vs. pull metrics collection models:
- When to choose each.
- Impacts on reliability, backpressure, service discovery, network usage, and failure isolation.
Describe the end-to-end architecture:
- Client libraries/agents (e.g., SDK or node agent/sidecar).
- Ingestion layer (APIs, gateways), queueing, and streaming aggregation.
- Time-series storage, query layer, alerting, dashboards, and SLOs.
Propose aggregation and rollup strategies at each layer:
- Client-side, agent-side, stream processors, storage-side.
- Handling high-cardinality labels, downsampling, late/out-of-order data, retention policies, and backfill.
Provide a capacity plan, sharding and replication strategy, and multi-tenant isolation.
Explain how you would test and monitor the monitoring system itself.

Make minimal, explicit assumptions as needed and call out trade-offs and guardrails.

Quick Overview

Context

Requirements

Compare push vs. pull metrics collection models:

When to choose each.
Impacts on reliability, backpressure, service discovery, network usage, and failure isolation.

Describe the end-to-end architecture:

Client libraries/agents (e.g., SDK or node agent/sidecar).
Ingestion layer (APIs, gateways), queueing, and streaming aggregation.
Time-series storage, query layer, alerting, dashboards, and SLOs.

Propose aggregation and rollup strategies at each layer:

Client-side, agent-side, stream processors, storage-side.
Handling high-cardinality labels, downsampling, late/out-of-order data, retention policies, and backfill.

Provide a capacity plan, sharding and replication strategy, and multi-tenant isolation.

Explain how you would test and monitor the monitoring system itself.

Make minimal, explicit assumptions as needed and call out trade-offs and guardrails.

Design a scalable metrics monitoring system

Quick Overview

Design a Metrics Monitoring System for Large-Scale Services

Context

Requirements

Solution

Comments (0)

Design a scalable metrics monitoring system

Quick Overview

Design a Metrics Monitoring System for Large-Scale Services

Context

Requirements

Solution

Comments (0)