What problem does it solve? Engineers struggle to find the right BytedTrace metric names, tags, and SDK APIs when monitoring QPS, latency, and error rates or adding custom spans and metrics to their services. ## Core Features & Use Cases - Metrics Query Guide: Explains the 4-segment metric format (bytedtrace.sdk.<family>.<suffix>) with ready-to-use query patterns for server QPS, client latency P99, and log event rates. - Go SDK Usage: Covers Tracer initialization, Span/Event/Metrics APIs, metrics pre-registration, span inheritance (in-process and cross-process via Inject/Extract), and post-sampling. - Framework Integration Matrix: Lists minimum versions for kitex, hertz, ginex, MySQL, Redis, Kafka, TOS, ByteES, FaaS, and more across Go, Java, C++, Python, Rust, and Node.js. - Use Case: You want to monitor your PSM's downstream call latency. Look up the client span metric bytedtrace.sdk.span.client.latency.us.pct99 with _psm and _to_service tags, then verify your kitex version meets the integration minimum. ## Quick Start Ask how to query the P99 latency and QPS metrics for your PSM using BytedTrace.