Metrics
32 items tagged with "metrics"
Best Practices4
OpenTelemetry Instrumentation Guidelines
Best practices for generating consistent traces, metrics, and logs using OpenTelemetry.
RED & USE Monitoring Methodologies
Standard approaches for selecting golden signals (Rate-Errors-Duration / Utilisation-Saturation-Errors).
The Four Golden Signals
Google SRE's four core metrics for monitoring a user-facing system: latency, traffic, errors, and saturation.
Prometheus Monitoring Best Practices
Guidance for naming metrics, controlling label cardinality, and writing alerting rules in Prometheus, the CNCF metrics and alerting system.
Anti-Patterns4
Story Point Inflation
Estimates in story points drift upward over time so velocity rises without more real work, turning a planning aid into a gamed vanity number.
Vanity Metrics
Tracking impressive-looking numbers that do not inform decisions or correlate with real outcomes, creating an illusion of progress.
Feature Factory
An organization that measures success by the volume of features shipped rather than the outcomes they produce, optimizing output over impact.
HiPPO Decision-Making
Decisions driven by the Highest Paid Person's Opinion rather than data, evidence, or the expertise of those closest to the problem.
Tutorials2
How to Instrument an Application with OpenTelemetry
Add OpenTelemetry traces, metrics, and logs to a service and export them through the OpenTelemetry Collector to your backend.
How to Expose Prometheus Metrics from a Service
Add a metrics endpoint with counters, gauges, and histograms, then scrape it with Prometheus and query the results.
Products2
Stacks4
PLG Stack (Prometheus + Loki + Grafana)
Open-source observability stack: Prometheus collects metrics, Loki aggregates logs, and Grafana unifies visualization, dashboards, and alerting.
Prometheus + Thanos
A scalable, highly available metrics stack extending Prometheus with Thanos for global query, long-term object-storage retention, and multi-cluster aggregation.
Jaeger + OpenTelemetry + Prometheus
An open-source observability stack combining OpenTelemetry instrumentation, Jaeger distributed tracing, and Prometheus metrics, visualized in Grafana.
Loki + Tempo + Mimir
Grafana Labs' scalable, object-storage-backed observability stack for logs (Loki), traces (Tempo), and metrics (Mimir), unified in Grafana.
Benchmarks10
API Translation Benchmark
Measures ability to translate between API specifications (REST, GraphQL, gRPC)
Cloud Configuration Translation
Evaluates accuracy of translating cloud configs (CloudFormation to Terraform, etc.)
Security MTTR Benchmark
Measures mean time to remediate security findings, from detection to fix verification, segmented by severity and asset criticality.
DORA Metrics Benchmark
Measures software delivery and operational performance via four key metrics: deployment frequency, lead time, change failure rate, and time to restore.
Code Coverage Benchmark
Measures the proportion of code exercised by automated tests, across line, branch, statement, and function coverage, as a test-completeness indicator.
Mutation Testing Score Benchmark
Measures test-suite effectiveness by injecting small faults into code and checking how many are detected, reported as the mutation score.
Flaky Test Rate Benchmark
Measures the prevalence and impact of nondeterministic tests that pass and fail without code changes, eroding trust in the test suite.
CI Build Time (p95) Benchmark
Measures continuous-integration pipeline duration, focusing on the p95 build time and its phases, to quantify developer feedback latency.
Defect Escape Rate Benchmark
Measures the proportion of defects that reach production undetected by pre-release testing, indicating the effectiveness of quality gates.
CI/CD Pipeline Reliability Benchmark
Measures how dependably a delivery pipeline succeeds, reporting pass rate, infrastructure-failure share, and mean time to recover a broken pipeline.
FAQs3
What is the DriftScore and how is it calculated?
The DriftScore is a metric from 0–100 that represents how far behind your codebase is relative to current stable ecosystem baselines. Lower scores mea...
What are CRA remediation metrics?
When `vg scan --vulns` runs in a git repository, Vibgrate attributes each vulnerability to the commit that introduced the affected version and measure...
Does Vibgrate measure real mean time to remediate (MTTR)?
Yes. As well as how long open vulnerabilities have been exposed, Vibgrate reconstructs closed exposure windows from git history — a vulnerable version...
Glossaries3
DriftScore
DriftScore is Vibgrate’s 0–100 measure of maintainability drift — how far a stack has moved from current, supported baselines — where 0 is fully current and 100 is maximum drift.
DriftRisk™
DriftRisk™ is Vibgrate’s derived 0–100 executive headline, computed purely from DriftScore and RiskScore — one number for how much pressure a codebase puts on the team to act.
Libyear
A libyear is the calendar time between the dependency version you use and the latest stable release — a simple, ecosystem-comparable measure of dependency freshness.