What problem does it solve? Go developers at ByteDance need to emit monitoring metrics from their services and query collected data, but must choose between SDK versions (V2, V3, V4), understand agent prerequisites, and handle query quota and region configuration correctly. ## Core Features & Use Cases - SDK Instrumentation Guidance: Complete examples for emitting Counter, RateCounter, Store, Timer, and Histogram metrics using the gopkg/metrics V2, V3, and V4 clients. - Metrics Query SDK: Instructions for initializing the metrics-query client, building queries, and handling quota, region, and authentication errors. - Version Selection & Migration: Feature comparison of V2/V3/V4, incompatibility notes, and upgrade recommendations including Metrics-2.0 multi-tenant and multi-value metric support. - Use Case: A developer adding latency monitoring to a new Go microservice can follow the V4 guide to create a client, emit a multi-value Timer metric, verify emission with strace, and then query the data via the metrics-query SDK. ## Quick Start Ask the AI to show how to instrument a Go service with the Metrics V4 SDK and emit a timer metric with tags.