Skip to content

Latest commit

 

History

History
67 lines (47 loc) · 26.2 KB

168-designing-a-metric-system.md

File metadata and controls

67 lines (47 loc) · 26.2 KB
Raw
layout title date comments categories language slides references
post
Designing a metric system
2019-08-26 11:58
true
system design
en
false

Requirements

Log v.s Metric: A log is an event that happened, and a metric is a measurement of the health of a system.

We are assuming that this system’s purpose is to serve metrics - namely, counters, conversion rate, timers, etc. for monitoring the system performance and health. If the conversion rate drops drastically, the system should alert the on-call.

  1. Monitoring business metrics like signup funnel’s conversion rate
  2. Supporting various queries, like on different platforms (IE/Chrome/Safari, iOS/Android/Desktop, etc.)
  3. data visualization
  4. Scalability and Availability

Architecture

Two ways to build the system:

  1. Push Model: Influx/Telegraf/Grafana
  2. Pull Model: Prometheus/Grafana

The pull model is more scalable because it decreases the number of requests going into the metrics databases - there is no hot path and concurrency issue.

Server Farm
Server Farm
write
write
telegraf
telegraf
InfluxDB
InfluxDB
REST API
REST API
Grafana
Grafana
InfluxDB Push Model
InfluxDB Push Model
Prometheus Pull Model
Prometheus Pull Model
Application
Application
Exporter
Exporter
client library
client library
3rd Party
Application
3rd Party<br>Application
pull
pull
Prometheus
Prometheus
Retrieval
Retrieval
Service Discovery
Service Discovery
Storage
Storage
PromQL
PromQL
Alertmanager
Alertmanager
Web UI / Grafana / API Clients
Web UI / Grafana / API Clients
PagerDuty
PagerDuty
Email
Email

Features and Components

Measuring Sign-up Funnel

Take a four-step sign up on the mobile app for example

INPUT_PHONE_NUMBER -> VERIFY_SMS_CODE -> INPUT_NAME -> INPUT_PASSWORD

Every step has IMPRESSION and POST_VERIFICATION phases. And emit metrics like this:

{
  "sign_up_session_id": "uuid",
  "step": "VERIFY_SMS_CODE",
  "os": "iOS",
  "phase": "POST_VERIFICATION",
  "status": "SUCCESS",
  // ... ts, contexts, ...
}

Consequently, we can query the overall conversion rate of VERIFY_SMS_CODE step on iOS like

(counts of step=VERIFY_SMS_CODE, os=iOS, status: SUCCESS, phase: POST_VERIFICATION) / (counts of step=VERIFY_SMS_CODE, os=iOS, phase: IMPRESSION)

Data Visualization

Graphana is mature enough for the data visualization work. If you do not want to expose the whole site, you can use Embed Panel with iframe.