Committing to Anomaly Detection Four Days Before AWS Announced It
Mihir Soni included inThe anomaly-detection repo under Open Distro for Elasticsearch was created on November 15th, 2019. My first commit landed a week later, on November 22nd — a small fix to the test workflow config, the kind of unglamorous CI plumbing that has to work before anyone can trust the rest of the repo. Four days after that, on November 26th, AWS published “Introducing real-time anomaly detection in Open Distro for Elasticsearch” and the plugin became public.
I don’t think it’s a coincidence that the commit came before the announcement rather than after. By the time AWS is ready to publish a blog post like that, the code already has to be in decent enough shape to point people at. Someone has to get it there first, quietly, in the days right before — this time that someone was me, fixing a CI workflow nobody outside the team could see yet.
On the Kibana side, anomaly-detection-kibana-plugin has an interesting wrinkle: its git history goes back to July 2019, four months before the public repo existed on GitHub in November. That’s not a mistake in the dates — it’s what open-sourcing already-in-progress internal work looks like. The commits are real, the dates are real, they just predate the repo being something the public could see.
Not a big dramatic story — a CI fix, four days, and a blog post. But it’s the same pattern I keep noticing: the public announcement is the last step, not the first one, and by the time you read it, someone’s already been living inside that code for weeks.