Metric
A metric is a quantitative measure used to characterize or assess a property, condition, behavior, performance, or outcome.
Data-Driven Cybersecurity
A quantitative measure derived or interpreted using statistical methods to assess performance, conditions, or change under uncertainty.
- How it is used
- Connects security performance and risk measurements to business goals, resource priorities, and decisions.
- How deep it goes
- Defines selection criteria and develops a goal-to-measurement-to-improvement cycle, emphasizing interpretation rather than statistical formulas.
- Examples
- Uses patching time, vulnerability remediation, incident detection time, and industry-specific security measures to illustrate actionable choices.
- What you can do after
- Practice/perform selecting, benchmarking, reporting, and revisiting security metrics to guide improvements and communicate decisions.
Effective Data Analysis
A model evaluation metric is a quantitative measure of how well a statistical model fits data or performs its intended task.
- How it is used
- Uses metrics to track organizational goals over time and to assess the fit or performance of statistical models.
- How deep it goes
- Develops SMART design and interpretation for organizational metrics, then explains what several regression evaluation scores and residuals indicate.
- Examples
- Uses website engagement measures and a housing-price regression summary to make metric selection and model evaluation concrete.
- What you can do after
- Practice/perform organizational metric design and diagnose/debug regression fit using evaluation scores alongside residuals.
Experimentation for Engineers
A quantitative measure of business performance, such as revenue, engagement, or time spent using an application.
- How it is used
- Guides acceptance or rejection of production changes through online measurements of business outcomes.
- How deep it goes
- Defines business metrics and develops selection, stakeholder, update, and multi-metric trade-off practices without deriving experimental statistics.
- Examples
- Uses daily revenue, DAU, swipe prediction, video comments, time spent, advertising revenue, and trading profit and risk.
- What you can do after
- Operate/configure metric-driven experiments by selecting business-specific measures, thresholds, and trade-offs for production decisions.
Logs and Telemetry
A metric is a usually numeric measurement with a descriptive label that represents the state or activity of hardware or software.
- How it is used
- Supports observability by representing resource and business measurements for near-real-time monitoring, aggregation, routing, and incident investigation.
- How deep it goes
- Explains collection, tagging, log conversion, and name-based filtering, while deferring detailed Prometheus metric-type documentation to its reference.
- Examples
- Demonstrates CPU, disk, memory, and network collection; dummy JSON logs converted to Prometheus metrics; and node_cpu metric selection.
- What you can do after
- Operate/configure it by collecting host measurements, deriving Prometheus metrics from logs, and restricting exported metric names.
Automating API Delivery
A business metric is a quantitative measure of an organization's commercial performance, customer outcomes, quality, or cost.
- How it is used
- Guides API product improvement decisions by relating developer activity and experience to a business focus metric.
- How deep it goes
- Explains metric selection through PDSA, developer-journey touchpoints, and product categories; treats lower-level measures as hypothesized leading indicators.
- Examples
- Uses active-subscriber goals, landing-page visitors, referrals, sign-ups, daily active users, retention, and conversion rate.
- What you can do after
- Apply it via developer journey mapping and product analytics to choose, capture, share, and review API improvement measures.
Machine Learning System Design
An evaluation measure that can be calculated only after a system is deployed and its output is used in a real business context.
- How it is used
- Measures whether a deployed system advances its business goal when people use its output.
- How deep it goes
- Defines the offline–online distinction and outlines proxy selection, A/B testing, and reporting without deriving individual metrics.
- Examples
- Contrasts search clicks and purchases with offline ranking scores, and pairs spam, inventory, and search outcomes with offline measures.
- What you can do after
- Evaluate/understand it by checking business effects in an A/B test and comparing them with offline results before making rollout decisions.
Machine Learning for Tabular Data: XGBoost, Deep Learning, and AI
A quantitative measure used to monitor or assess model performance rather than directly define the training objective.
- How it is used
- Monitors model training and guides feature selection, hyperparameter optimization, and early stopping.
- How deep it goes
- Distinguishes metrics from optimization losses and outlines their operational uses, but does not define particular metric formulas.
- Examples
- Uses XGBoost training, feature selection, hyperparameter search spaces, cross-validation schemes, and early stopping as practical contexts.
- What you can do after
- Evaluate and tune models by comparing configurations, monitoring training, testing generalization, and stopping unproductive iterations.
Read how Machine Learning for Tabular Data: XGBoost, Deep Learning, and AI explains metric →
ScyllaDB in Action
A metric is a numeric measurement of a system, database, or workload property collected for observation over time.
- How it is used
- Supports monitoring a ScyllaDB cluster by collecting observable measurements for dashboards, alerts, load testing, and incident response.
- How deep it goes
- Defines metrics through concrete node measurements, time-series collection, PromQL queries, and dashboard interpretation without detailing metric instrumentation.
- Examples
- Uses cache-partition insertions, 95th-percentile read latency, reads in progress, compactions, and Grafana CQL-read graphs.
- What you can do after
- Diagnose/debug with metrics by querying time-series data and relating latency changes to reads or compactions.
Building LLM Applications with DSPy
A criterion or measurement used to assess the quality of a language-model application's outputs.
- How it is used
- Scores LM responses to compare prompts and assess likely production performance.
- How deep it goes
- Defines a custom Python scoring function and illustrates Boolean and graded scores; defers built-in metrics and optimization details.
- Examples
- Uses airline-intent labels, partial credit for similar intents, and accuracy-versus-cost trade-offs.
- What you can do after
- Apply it via a DSPy custom metric to score classifier responses, then evaluate a test set against additional production concerns.
Read how Building LLM Applications with DSPy explains metric →
Build and Orchestrator in Go (From Scratch)
A metric is a measured value describing the state or performance of a worker machine.
- How it is used
- Supports task placement by reporting each worker’s current resource state to a manager.
- How deep it goes
- Builds a periodic collector and JSON endpoint, while deferring a deep explanation of the Linux /proc filesystem.
- Examples
- Uses a restaurant seating analogy, Linux /proc file output, a CollectStats loop, and a GET /stats route.
- What you can do after
- Apply it via goprocinfo and a GET /stats endpoint to expose a worker’s current resource state.
Read how Build and Orchestrator in Go (From Scratch) explains metric →
Think Like a CTO
A metric is a quantifiable measure used to assess a condition, activity, or outcome.
- How it is used
- Guides team reporting, accountability, hiring decisions, and operational monitoring with measures suited to each purpose.
- How deep it goes
- Explains selection, collection, review cadence, and comparison, but gives no formulas or fixed numerical thresholds.
- Examples
- Uses support resolution times and interaction counts, ticket and release measures, and CPU, memory, and disk usage.
- What you can do after
- Practice/perform it by choosing team-specific measures, reviewing them regularly, comparing appropriate baselines, and investigating deviations.
Machine Learning Platform Engineering
A custom metric is an application-defined quantitative measurement exposed for monitoring a specific behavior or outcome.
- How it is used
- Tracks application behavior that default service metrics miss, supporting operational alerting and reporting.
- How deep it goes
- Defines metric types, records observations in service code, verifies /metrics exposure, and visualizes results in Grafana.
- Examples
- Uses object-detection confidence histograms and recommendation-request counters for concrete monitoring cases.
- What you can do after
- Build it from scratch with prometheus-client, expose observations from inference code, and query them in Grafana.
Read how Machine Learning Platform Engineering explains metric →
Think Like a Software Engineering Manager
A metric is a quantitative measure used to assess performance against defined success criteria.
- How it is used
- Uses quantitative measures to assess engineering-manager and cross-functional team performance against defined project or organizational goals.
- How deep it goes
- Defines metrics as objective gauges and lists performance dimensions, but does not provide a general method for selecting or calculating them.
- Examples
- Illustrates success with a product launch targeting 20% higher customer satisfaction and 30% fewer escalations, plus platform reliability and cost measures.
- What you can do after
- Evaluate engineering-management and cross-functional outcomes against business, delivery, quality, collaboration, and customer measures.
Read how Think Like a Software Engineering Manager explains metric →
gRPC Microservices in Go
A metric is a numerical measurement of a system or application property collected over time.
- How it is used
- Tracks microservice behavior over time and supports dashboards and alerts that expose operational problems.
- How deep it goes
- Defines Prometheus metric fields and grouping, then examines quality indicators and the limitations of average latency.
- Examples
- Uses a service memory-usage alert and contrasting request latencies to show alerting and reporting pitfalls.
- What you can do after
- Apply it via OpenTelemetry instrumentation and Prometheus collection to monitor services and configure metric-based alerts.
Deep Learning with R, Third Edition
A custom metric is a task-specific quantitative measure defined to evaluate success according to particular project goals.
- How it is used
- Defines project success measures and monitors model performance during training and evaluation.
- How deep it goes
- Explains custom Keras metrics through subclassing, state updates, result reporting, and resetting.
- Examples
- Contrasts classification measures and demonstrates a sparse-label RMSE metric.
- What you can do after
- Build a custom Keras metric by subclassing Metric and implementing state updates, result reporting, and reset behavior.
Read how Deep Learning with R, Third Edition explains metric →
Effective Conversational AI
A metric is a quantitative measure used to evaluate a system's performance or outcomes.
- How it is used
- Guides iterative conversational-system improvement by tracking outcomes tied to business goals and user satisfaction.
- How deep it goes
- Connects metric selection to monitoring and improvement decisions through deployment comparisons and a business-impact example.
- Examples
- Uses deployment failure comparisons and an insurance claim flow measured by opt-outs, escalations, task completion, and user scores.
- What you can do after
- Evaluate whether fixes worked by comparing outcomes across deployments and use relevant measures to target improvements.
Related concepts
- evaluationused by · Evaluation is the systematic assessment of a system, result, or approach against relevant criteria, evidence, or objectives.
- optimizationused by · Optimization is the systematic selection or adjustment of values, actions, or system designs to improve a specified objective, often subject to constraints.
- mean absolute percentage errorincludes · Mean absolute percentage error is the average absolute prediction error divided by the corresponding actual value, expressed as a percentage.
- Prometheusused by · Prometheus is an open-source monitoring and alerting system that collects, stores, and queries time-series metrics.
- alertingused by · Alerting is the generation and delivery of notifications when monitored conditions or events meet defined criteria or require attention or action.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.