Content Quality: Compact, well-structured Briefing (565 words, within the 300-800 Briefing range) with Overview, What Changed, What We Don't Know and Upgrade Considerations. Headline, summary and lead are all backed by the GitHub release notes. Tone is neutral; every quote is attributed.
Source Verification: Read the three gzipped snapshots (source-0, source-1, source-2 in sources/2026-10/prometheus-3150-adds-unix-domain-socket-scraping-stabilizes-xor2-chunk-encoding-and-deprecates-loglevel/), extracted to text, and grep-checked each claim. suspicious_patterns is null for all three. source-0 (GitHub release v3.15.0, titled 'Release 3.15.0 / 2026-09-24'): CONFIRMED date 2026-09-24 and verbatim quotes: '[FEATURE] Scraping: Add support for scraping targets via Unix Domain Sockets.', '[FEATURE] scrape: Implement OM2.0 scrape format.', '[ENHANCEMENT] Scraping: Support zstd-compressed scrape responses, enabled via feature flag zstd-scrape.', '[ENHANCEMENT] TSDB: Stabilize the XOR2 float chunk encoding. --enable-feature=xor2-encoding is deprecated; use storage.tsdb.chunk_encoding.floats: xor2 instead.' plus 'Check that other software reading the TSDB directly (e.g. Thanos sidecar) supports XOR2 before enabling.', the st-storage entry ('now automatically enables XOR2 float chunk encoding and ST-capable histogram chunk encoding'), '[CHANGE] Logging: Deprecate --log.level; use runtime.log_level configuration to supply the default level.', 'Allow changing the process log level through runtime.log_level on configuration reload', the --auto-gomemlimit.refresh-interval entry, sigv4 v0.5.0 with session_name and tags, UI scrape-pool effective configuration, Docker SD labels __meta_docker_container_image and __meta_docker_container_image_id, Kubernetes __meta_kubernetes_service_loadbalancer_ip from status.loadBalancer.ingress with fallback to deprecated spec.loadBalancerIP, WAL fixes ('Avoid WAL corruption after a failed WAL write in Agent mode', 'Ignore unknown WAL record types, to help users rolling back'; the latter is tagged Agent) and DetectReset ('could make histogram rate()/increase() undercount'). All verified; paraphrased ellipses (backticks stripped) are faithful. source-1 (feature flags, /latest/): CONFIRMED 'Enables the storage of start timestamps (ST) per sample, through WAL, TSDB/Agent and Remote-Write 2.0.', 'The st-storage feature also selects XOR2 as the default float chunk encoding because XOR chunks cannot store start timestamps.', and 'When enabled, Prometheus advertises support for Zstandard-compressed scrape responses in addition to gzip.' XOR2 'stabilized': the feature-flags page says 'This feature flag is deprecated. The XOR2 float chunk encoding is stable; select it with the chunk_encoding.floats field in the storage.tsdb section...' - consistent with the release notes and with the article's wording. source-2 (configuration reference, /latest/): CONFIRMED runtime.log_level text 'The minimum severity of messages emitted by the process logger. This setting can be changed by reloading the configuration.' (a YAML comment, quoted without the '#'); also documents storage.tsdb.chunk_encoding.floats. INCORRECT claim: the article's 'What We Don't Know' says 'the configuration reference reviewed for this report does not describe [Unix Domain Socket targets]'. The snapshot does describe them in the relabeling section: 'The __unix_socket__ label, when set, causes the scrape client to connect via the specified Unix domain socket path instead of the target's __address__. Set __scheme__ to http or https to specify the protocol used over the socket (defaults to http).' (also listed among the special labels that override scrape settings). A live curl re-fetch returned the identical 1,927,230-byte page and contained __unix_socket__; note that a WebFetch of the same URL (summarizer on a 1.9 MB page) wrongly reported the label as absent and chunk_encoding as absent - that summary was discarded as truncation/hallucination because it contradicts the raw snapshot and the raw curl output. Version-moving docs caveat: /docs/prometheus/latest/ pages could show content newer than 3.15.0; here the docs content is consistent with 3.15.0 (UDS label, runtime.log_level, deprecated xor2-encoding flag, zstd-scrape) and no feature absent from the 3.15.0 notes was relied on by the article. The --log.level deprecation claim rests solely on the release notes; neither docs page covers command-line flags, so it is not contradicted by them. Snapshots captured 2026-10-16 (about three weeks after release); no sign of post-3.15.0 drift in the cited passages.
Factual Accuracy: All dates, numbers, flag names, label names and quotes trace to the snapshots, with one exception: the 'What We Don't Know' sentence that the configuration reference does not describe Unix Domain Socket targets is false (the reference documents the __unix_socket__ relabeling label). The adjoining statement that the release page gives no configuration syntax is true. The claim that the notes do not say which third-party tools beyond Thanos sidecar read XOR2 is true. The error is in a subordinate section, not the headline, summary or lead, and a single corrections note covers it honestly.
Overall Assessment: Substantively accurate, well-sourced Briefing; one subordinate factual error about what the configuration reference contains. Approve with a corrections record.