SShortSingh.
Back to feed

Node.js Uptime Health Monitoring API Explained (with Rollback-Safe Status Evidence)

0
·1 views

TL;DR: A green Node.js status response is not enough evidence for a safe customer-support rollback. Keep app and job health as logs and metrics, preserve the release and request identifiers that let support reconstruct an incident, and use an external heartbeat monitor for scheduled work. The practical design is two signals: queryable runtime evidence for what happened, plus a dead-man's switch for work that never happened. My decision rule is blunt: do not roll back because one chart turned red. Roll back when the evidence ties a customer-visible failure to a release, and retain the account a

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
ProgrammingDEV Community ·

OpenAI Expands Text Provenance in the EU as AI Act Rules Drive New Watermarking Tools

OpenAI is extending its content provenance work to AI-generated text in the European Union, positioning the move as part of its response to the EU AI Act. The company is taking a phased approach: eligible API customers worldwide can opt in to text watermarking for select models, while watermarking for eligible ChatGPT and Codex outputs is planned for the EU in the coming weeks. The key qualification is equally important. OpenAI says text watermarking remains an early technology, not conclusive evidence of who wrote a piece of content or whether a human was involved. The October 5, 2026 update

0
ProgrammingDEV Community ·

🌿 Flora Scout: Offline Trail Flora & Plant Identifier

🌟 What I Built It runs an open-weight vision model locally on-device using WebGPU/Ollama, paired with an open-source agent framework (Mastra) to organize local trail findings, cross-reference native/invasive species databases locally, and log discovered flora. The app is built so that screen time is minimized to a quick 5-second snapshot, letting you get back to enjoying nature. 🍃 How It Gets People Outside ("Touch Grass") Fast Trail Identification: Snap a photo on the trail, get immediate identification and brief ecology insights, and immediately put the phone away. Zero Signal Needed: Desi

0
ProgrammingDEV Community ·

Node.js Realtime Backpressure Contracts for Shared Kanban Board Tests

Short answer: keep the board's event log authoritative, apply backpressure at the connection boundary, and test state convergence instead of hoping wall-clock sleeps line up. For a healthtech chat room or shared kanban board, presence accuracy is the decision axis: a delayed cursor is annoying, but a stale "online" clinician can misroute work. The useful contract is small. Every mutation gets an ordered sequence, every reconnect asks for a cursor, and presence is explicitly soft state with a lease. A test should control delivery and acknowledgements with a virtual clock.

0
ProgrammingDEV Community ·

Eye of the Beholder: How Westwood's 1991 Dungeon Crawler Turned AD&D into a Real-Time Nightmare

Retro game retrospective #8 — 1991, Westwood Associates / Strategic Simulations, MS-DOS (Amiga, PC-98, Sega CD, Super NES ports followed) In 1991, the scariest monster in video games had no hit points you could see and no initiative order to hide behind. It was waiting at the bottom of a sewer under the city of Waterdeep, and it wanted you to know it was there the whole way down. Eye of the Beholder — the first game in SSI's "Legend Series" of Advanced Dungeons & Dragons computer products — took the dungeon crawler, made it real-time, and aimed it squarely at the oldest fear in tabletop gaming

Node.js Uptime Health Monitoring API Explained (with Rollback-Safe Status Evidence) · ShortSingh