90% of a Service's Metrics Require Zero Instrumentation Code, Analysis Shows

·53 views

A software engineer analysed the full metrics output of a production service and found 67 total metric records in its snapshot. Of those, 59 came automatically from the platform runtime and only 6 were written by the service itself. Metrics covering liveness, readiness, build version, broker delivery, Postgres pool state, and Go runtime internals all appeared without a single line of custom instrumentation. The engineer stores metrics as a diffable snapshot file rather than relying on a live scrape endpoint, making changes trackable over time. The finding challenges the common assumption that meaningful observability requires deliberate instrumentation effort from developers.

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)

HN Asks: Has AI Produced Anything Truly New on Its Own?

A Hacker News user asks the community to name something genuinely new that an AI system has accomplished entirely by itself. The poster notes that after two years of AI development, they have not yet encountered such an example. In their view, apparent discoveries usually depend on a human identifying the novel element. Alternatively, the models appear to be merely combining existing data from separate sources that had never been connected. The post drew 4 points and 7 comments at the time it was captured.

0 comments Read more at Hacker News

ProgrammingHacker News ·

U.S. Producer Prices Climb 6.5% Annually in October, Highest Since late 2022

U.S. producer prices rose 6.5% year over year in October, the fastest pace since November 2022. That reading came in slightly below analysts' expectations of 6.6% and up from 6.3% in the prior period. On a monthly basis, producer prices increased 0.3%, short of the anticipated 0.4% gain. September's monthly figure was also revised upward, from 1.3% to 1.4%.

0 comments Read more at Hacker News

ProgrammingHacker News ·

Haskell community publishes a technical vision for its ecosystem

A technical vision document for the Haskell ecosystem has been posted on the Haskell Discourse forum. The post was shared on Hacker News, where it gathered 4 points and no comments at the time of capture. The source material provided contains only the links and engagement metrics, so the specific proposals in the vision are not described here. Readers are directed to the Discourse thread for the full content and any community discussion.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

Connector design should expose partial failures so agents can tell empty results from errors

A connector returning an empty array can signal several different outcomes, including a successful query with no matches, a request that failed before reaching the service, a partially loaded result, or unparseable data. The article argues these should be distinguished, since an agent cannot safely decide its next step if all of them appear as an empty list. It proposes returning results as structured reports that state the status (complete, empty, partial, retryable error, or action required), the source, the fetch time, and any continuation cursor or warnings. Continuation cursors should be saved only after a page is accepted, so an interrupted pagination can resume rather than presenting an incomplete list as complete. For write operations, the author recommends idempotency keys and recording whether an operation was confirmed, since a timeout after a write leaves the outcome ambiguous.

0 comments Read more at DEV Community