liveBook · Manning

Dashboard

As explained in Machine Learning Platform Engineering

A dashboard is a visual interface that presents queried operational measurements and other status information.

Production systems need answers that logs alone cannot give quickly: how many requests arrived, how response times changed, or whether incoming model data has drifted. A dashboard turns collected measurements into a visual interface for checking those questions over time. It complements logs, which provide detail for debugging individual failures. section 3.5 section 6.2.2

Build the view from the measurements the system already produces:

  • For an application, expose a `/metrics` endpoint, let Prometheus scrape it, then use Grafana to query Prometheus and chart the results. The Prometheus UI is useful for checking scraped values; Grafana is the dashboarding tool. section 3.5
  • For batch inference, generate an Evidently drift report from current features and reference training data. Add its results to a dashboard on each pipeline run; filter the view to inspect changes over time. section 6.2.2
  • For an instrumented RAG application, inspect Langfuse traces, costs, and latency to find usage patterns and guide retrieval or resource optimizations. section 12.4.3

Chart requests by response code

A Grafana query can sum the increase in `starlette_requests_total` over `[10m]`, grouped by `response_code`. The resulting time-series chart shows recent request counts; if every response has the same status code, it shows one line. section 3.5

Figure 3.17 Application 1 and Application 2 expose an endpoint for metrics. Prometheus scrapes those metrics, which are then visualized by Grafana. Alertmanager uses those metrics to check if any alerts need to be routed to a channel; in this case, it’s an email.
A diagram of a diagram

AI-generated content may be incorrect.

Follow the monitoring path from application metrics endpoints through Prometheus scraping to Grafana visualization; Alertmanager handles the separate notification path. section 3.5

Choose panels for decisions, not decoration. Resource and request metrics support service monitoring; application-specific metrics add context. Pipeline metrics made visible in a shared dashboard shorten feedback loops, while drift panels help check whether new data still resembles the reference data. section 11.4 section 8.2 section 6.2.2

How Machine Learning Platform Engineering covers it

How deep it goes
Shows metric exposure, scraping, querying, and charting, plus pipeline-driven dashboard updates; does not specify a general dashboard design procedure.
Examples
Uses a request-count time-series chart, an Evidently drift dashboard, Kubeflow pipeline metrics, and a Langfuse RAG observability view.
What it assumes
Introduces why metrics complement logs, while the drift workflow assumes an inference pipeline with current features and reference training data.
What you can do after
Apply it via Grafana to chart Prometheus metrics, or via Evidently to review drift results after inference pipeline runs.
How it connects
Connects dashboards to Prometheus, Grafana, alerting, data drift detection, Kubeflow Pipelines, and distributed tracing.

Also explained in

Compare how 15 books explain dashboard →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Machine Learning Platform Engineering. The section links point to the parts of the book it draws on.