SShortSingh.
Back to feed

Study Finds Flawed Telemetry Can Mislead AI Agents Into Wrong Health Conclusions

0
·17 views

A joint post by OllyGarden and Causely describes an incident where an agent queried logs for ERROR-level records, found none, and wrongly reported a payment service as healthy. The severity was embedded in message text rather than the severity field, so the query returned an empty result that looked valid. The authors argue that telemetry can be well-formed and schema-compliant yet still fail to reflect what actually happened, which is harder to detect than obvious problems like log storms. Drawing on audits of OpenTelemetry data from several organizations between July and October, they report frequent gaps such as error spans lacking status messages or exception events, and missing or default service names. They also found that many traces consisted of a single span, often signaling broken context propagation. The authors caution that their sample reflects teams that sought telemetry quality help and is not an industry-wide survey.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingHacker News ·

Spamhaus Announces New Email Sender Requirements Taking Effect in November

Spamhaus has published updated sender guidelines outlining new requirements for email senders. The changes are scheduled to take effect in November. The guidelines are available on the organization's website for senders to review. The source material includes limited detail beyond the announcement itself, so the specific requirements are not described here. Discussion of the update has appeared on Hacker News, where it received modest engagement.

0
ProgrammingDEV Community ·

Study finds OTP delivery to shared virtual numbers varies widely by app and country

A receive-SMS service analyzed about 900 tries on shared free numbers between 27 October and 16 November 2026, counting whether verification codes arrived. Success rates differed sharply by app and country, with Marktplaats in France delivering codes 98% of the time while Telegram rarely delivered any. The company says some large apps refuse shared numbers entirely, and waiting longer does not change the outcome. It also notes that many users cancel too early, although international SMS can take several minutes. The authors recommend private numbers for reliable automated testing, and the full dataset is published under a CC BY 4.0 license.

0
ProgrammingDEV Community ·

Can You Compete in Tech Without Strong English? A Two-Part Answer

Many developers worry that weak English will hold them back, but the author argues the answer depends on what is meant by competing. Most English speakers worldwide learned it as a second language, and English's share of websites has been shrinking, while programming keywords are simple to memorize. AI assistants now make it far easier to read technical material in one's own language, and history shows great software has emerged outside English. However, the surrounding tech conversation, including issues, reviews, talks, and interviews, still largely happens in English, which can slow learning, reduce visibility, and limit pay. The author recommends training reading, writing, listening, and speaking as separate skills through short daily practice.

0
ProgrammingDEV Community ·

Audit of 37 B2B Directories Finds Zero Usable Backlinks for a Static Site

A developer running a 897-page, ten-language static site on Cloudflare Workers audited 37 B2B directories to see which ones gave company pages a clickable link back to their site. None of the directories provided a usable link. The author describes six methodological errors made along the way, such as mistaking search results for backlinks and relying on static HTML fetches that miss client-rendered content. A key lesson was that plain-text domain mentions can look like links in search results but are not anchors in the page's DOM. The post also explains that checking rel attributes requires distinguishing nofollow from security directives like noopener and noreferrer.