PracHub
QuestionsPremiumCoachesLearningGuidesInterview Prep
|Home/System Design/LinkedIn

Design a company-wide monitoring system

Last updated: Mar 29, 2026

Quick Overview

This question evaluates skills in designing large-scale observability and monitoring systems, covering telemetry collection (metrics, logs, traces), high-throughput ingestion, storage and scaling strategies, alerting pipelines, and operational trade-offs like cardinality, retention, and backpressure.

  • medium
  • LinkedIn
  • System Design
  • Software Engineer

Design a company-wide monitoring system

Company: LinkedIn

Role: Software Engineer

Category: System Design

Difficulty: medium

Interview Round: Onsite

You are asked to design a **monitoring system used company-wide**. ## Goals - Collect and query telemetry for many services/hosts - Support alerting and dashboards for engineers and SREs - Handle high ingestion volume and multi-team usage ## Telemetry types to cover - Metrics (time series) - Logs - Distributed traces (optional but strong) ## Discuss - Key requirements (SLOs, latency, retention, tenancy) - High-level architecture and data flow - Storage choices and scaling - Alerting pipeline and reliability - Operational concerns (cardinality, cost controls, backpressure)

Quick Answer: This question evaluates skills in designing large-scale observability and monitoring systems, covering telemetry collection (metrics, logs, traces), high-throughput ingestion, storage and scaling strategies, alerting pipelines, and operational trade-offs like cardinality, retention, and backpressure.

Related Interview Questions

  • Review a Web Application Architecture - LinkedIn (easy)
  • Scale a Distributed Randomized Multiset - LinkedIn (medium)
  • Design a Top-K Ranking Service - LinkedIn (easy)
  • Design a Global Calendar Service - LinkedIn (medium)
  • Design a malicious-URL checking service using an isMalicious API - LinkedIn (medium)
LinkedIn logo
LinkedIn
Nov 21, 2025, 12:00 AM
Software Engineer
Onsite
System Design
6
0

You are asked to design a monitoring system used company-wide.

Goals

  • Collect and query telemetry for many services/hosts
  • Support alerting and dashboards for engineers and SREs
  • Handle high ingestion volume and multi-team usage

Telemetry types to cover

  • Metrics (time series)
  • Logs
  • Distributed traces (optional but strong)

Discuss

  • Key requirements (SLOs, latency, retention, tenancy)
  • High-level architecture and data flow
  • Storage choices and scaling
  • Alerting pipeline and reliability
  • Operational concerns (cardinality, cost controls, backpressure)

Solution

Show

Submit Your Answer to Earn 20XP

Sign in to leave a comment

Loading comments...

Browse More Questions

More System Design•More LinkedIn•More Software Engineer•LinkedIn Software Engineer•LinkedIn System Design•Software Engineer System Design
PracHub

Master your tech interviews with 8,000+ real questions from top companies.

Product

  • Questions
  • Learning Tracks
  • Interview Guides
  • Resources
  • Premium
  • For Universities
  • Student Access

Browse

  • By Company
  • By Role
  • By Category
  • Topic Hubs
  • SQL Questions
  • Compare Platforms
  • Discord Community

Support

  • support@prachub.com
  • (916) 541-4762

Legal

  • Privacy Policy
  • Terms of Service
  • About Us

© 2026 PracHub. All rights reserved.