HN user

nishantmodak

590 karma
Posts63
Comments60
View on HN
github.com 16d ago

Show HN: L9gpu – GPU telemetry that ties each GPU to the K8s pod or Slurm job

nishantmodak
20pts0
github.com 4mo ago

Call a Human MCP

nishantmodak
4pts1
last9.io 6mo ago

Why high-cardinality workloads fail differently in Prometheus vs. ClickHouse

nishantmodak
3pts0
last9.io 6mo ago

Why high-cardinality labels stress metrics databases

nishantmodak
2pts1
blog.last9.io 4y ago

Running SLOs

nishantmodak
1pts0
blog.last9.io 4y ago

Latency SLO

nishantmodak
3pts0
blog.last9.io 5y ago

Observe a Service Not a Server

nishantmodak
2pts0
blog.last9.io 5y ago

Need for Systems Observability

nishantmodak
1pts0
blog.hotstar.com 5y ago

Monitoring at IPL Scale

nishantmodak
2pts0
github.com 5y ago

Show HN: SLO Computer

nishantmodak
1pts0
www.bbc.com 5y ago

Fascinating Story of a Vaccine from 1800s

nishantmodak
1pts0
news.ycombinator.com 5y ago

Clever Hans Fallacy of Monitoring Tools

nishantmodak
6pts1
www.catb.org 10y ago

Unix Philosophy

nishantmodak
4pts0
github.com 10y ago

Non HTTP Microservices framework

nishantmodak
2pts0
www.crowdsupply.com 11y ago

XBee networks over smartphone using BLE

nishantmodak
4pts0
thenextweb.com 13y ago

Bangalore brings India's startup ecosystem into limelight

nishantmodak
3pts0
alestic.com 13y ago

Cost of Transitioning from S3 to Glacier

nishantmodak
1pts0
news.ycombinator.com 13y ago

Hacking the System

nishantmodak
1pts1
arxiv.org 13y ago

Physicist challenges a traffic case about running a red light. He Won [pdf]

nishantmodak
8pts4
chrome.google.com 13y ago

SSH Shell [Chrome Plugin]

nishantmodak
1pts0
startupdesi.com 14y ago

Fire bottom 1% of your customers

nishantmodak
1pts0
m.timesofindia.com 14y ago

Censor posts or face China-like ban: Delhi high court

nishantmodak
2pts0
oreilly.com 14y ago

Free as in Freedom : Richard Stallman

nishantmodak
7pts1
www.ysearchblog.com 14y ago

Yahoo Opens Content Analysis Technology

nishantmodak
2pts0
m.timesofindia.com 14y ago

Recreating a volcanic eruption to cool Earth

nishantmodak
1pts0
online.wsj.com 15y ago

Change Your Brain

nishantmodak
4pts1
www.eweek.com 15y ago

IBM Launches Maqetta HTML5 Tool

nishantmodak
6pts0
m.economictimes.com 15y ago

Indian governments Internet kill switch

nishantmodak
4pts0
news.ycombinator.com 15y ago

Offer HN : One Thread for all

nishantmodak
13pts6
en.wikipedia.org 15y ago

Engineer's Day - India

nishantmodak
2pts1
Call a Human MCP 5 months ago

I built a small MCP server that lets any AI agent (Claude Desktop, Cursor, Windsurf) block and wait for a human response before taking irreversible actions.

  Two tools:
  - ask_human(question) – agent blocks until you reply
  - request_approval(action) – agent blocks until you click Approve or Deny

  Notifications via Slack (with interactive buttons), or native macOS
  dialogs. Works with any MCP-compatible client over stdio or SSE.

  The use case that motivated it: I kept coming back to find my agent had done
  something I didn't want while I was away. Now it just asks.

  GitHub: https://github.com/nishantmodak/call-a-human-mcp

I wrote this after seeing the same failure modes across multiple teams and metrics stacks.

The intent here isn’t to argue that high cardinality is bad but to explain the mechanical reasons unbounded cardinality shows up later as cost surprises, slow queries, and trust erosion.

Curious if others have seen similar query-time or indexing issues they have noticed.

I have a different take

Engineers have to pre-define and send all telemetry data they might need – since it’s so difficult to make changes after the fact – regardless of the percentage chance of the actual need.

YES. Let them send all the data. The best place to solve for it is at Ingestion.

There's typically 5 different stages to this process.

Instrumentation -> Ingestion -> Storage -> Query (Dashboard) -> Query (Alerting)

Instrumentation is the wrong place to solve this.

Ingestion - Build pipelines that allow to process this data and provide for tools like streaming aggregation, cardinality controls that allow to 'process it' or act on anomalous patterns. This atleast makes working on observability data 'dynamic' instead of having to go change instrumentation always. Storage - Provide blaze (2hours), hot(1 month), cold(13 months) of tiered data storage with indipendent read paths.

This, in my opinion has solved for the bulk of cost & re-work challenges associated with telemetry data.

I believe, Observability is the Big Data of today, without the Big Data tools! (Disclosure: I work at Last9.io and we have taken a similar approach to solve for these challenges)

https://last9.io/data-tiering/

The rice farmers I met in Bihar, for instance, are now growing a new variety of flood-tolerant rice—nicknamed “scuba” rice—that can survive two weeks underwater.

Found this extremely interesting. Probably because, I was surprised by the thought that, this could be done

Agree! With http://tah.io/get we have tried to make use of BLE not just as beacons but also for combining the power of your physical sensors with 'smartphone' sensors to have much more interesting use cases!

“If we had had the same progress in the aircraft industry, you and I could be flying between London and New York in 500,000-seat planes and the fare would be about 25 cents,” he once said.

What kind of progress/innovation does he refer to in this?

Totally agree. I wondered the same. May be - since he is a _famous_ hacker - an update about his location might help those in the area with communities / talks etc?