Developer Finds OpenTelemetry Spans Logged Correctly But Captured Zero Real Timing

·4 views

A developer documented their first hands-on experience with OpenTelemetry, adding instrumentation to a Python-based blog pre-publication checker. All 15 spans appeared correctly in the Jaeger UI with proper names and attributes, but the child spans collectively totalled only 0.085 ms while the parent span recorded over 1,000 ms. The discrepancy occurred because the spans were wrapping result-reading code rather than the actual execution of each check. After rewriting the instrumentation to wrap the real work, the 15 child spans correctly summed to 1,183 ms. The author shared the experience as a practical record of common first-timer mistakes with distributed tracing tools.

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)

Traditional SEO Metrics Fall Short as AI Search Reshapes Brand Visibility Measurement

AI-powered search tools like ChatGPT, Perplexity, and Google AI Overviews are creating a measurement blind spot for marketers, as brands can influence users without ever receiving a website click. A Search Engine Land framework argues that conventional metrics such as rankings, impressions, and organic sessions no longer fully capture brand presence in AI-generated answers. The proposed approach tracks four new indicators: AI citations, citation share relative to competitors, authority weight within AI responses, and sentiment attached to brand mentions. This framework is not intended to replace traditional SEO reporting but to extend it for an environment where discovery and referral traffic have become decoupled. Teams relying solely on click-based data risk underestimating their brand's reach, missing competitor gains in AI answers, or failing to detect inaccurate brand portrayals that never generate a session.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Access-control bugs drain $1.4M from two DeFi protocols in weeks

Two decentralized finance protocols, RISEx and WEMIX.FI Lend, lost approximately $673,000 and $730,000 respectively due to access-control vulnerabilities in their smart contracts. Both exploits followed the same pattern: critical state-changing functions lacked proper ownership or role-based restrictions, allowing anyone to call them. The fix is straightforward — adding an access modifier like onlyOwner — but identifying the missing guard in large codebases before deployment remains the real challenge. Existing static analysis tools often generate excessive false positives by flagging unprotected functions indiscriminately, causing developers to overlook genuine threats. More precise scanners that filter out view functions, inline guards, and one-time initializers can reduce noise and help catch the one real vulnerability before it reaches mainnet.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

AI Search Is Pushing Global Websites Beyond Simple Translation to True Localization

Translation alone is no longer a sufficient strategy for international websites in the age of AI-powered search, according to a Search Engine Land analysis. Global sites must now account for how Google, local entities, and large language models assess relevance in each specific market. This requires an architectural shift, where local search signals — including SERP patterns, entity coverage, and query phrasing — should guide content decisions rather than simply replicating a source-market structure in another language. While established international SEO tools like hreflang and canonical signals remain essential, they should support a genuinely localized experience rather than mask a boilerplate translation. Experts recommend a staged approach, starting with a focused set of cornerstone entities to learn what each market actually needs before scaling broader content efforts.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Safely Run AI-Generated JavaScript Code Without Risking Your Server

As AI agents grow more autonomous, they increasingly generate and execute their own code on the fly, creating serious security risks for production systems. Running LLM-synthesized JavaScript directly within a core Node.js service can expose database credentials, trigger infinite loops, or crash entire microservice architectures. Unlike traditional agent setups where tools were pre-compiled and statically defined, modern self-directed agents require dynamic code execution that introduces untrusted input from within the system itself. Security experts recommend isolating such code in ephemeral, sandboxed environments — similar to AWS Lambda functions or dedicated micro-containers — that are stripped of network access and system-level permissions. Developers building AI agents in Node.js or TypeScript are urged to treat sandboxing as a foundational architectural requirement, not an optional safeguard.

0 comments Read more at DEV Community