Now
Featured
Featured
DeepSeek Status Page Migration: From Atlassian to Flashduty
DeepSeek moved its public status page from Atlassian Statuspage to Flashduty Statuspage. The engineering math behind it: why they switched, whether to self-host, whether it migrates cleanly, and the key differences between Flashduty and Atlassian.
Flashduty Support
AI SRE can now delegate to your agents — and vice versa
Register an external agent in the console and AI SRE can hand whole tasks over to it, with progress streaming back into the conversation. It works the other way too: AI SRE exposes a standard A2A endpoint and accepts work from other agents.
Flashduty Engineering
Safe cluster access for AI SRE: no kubeconfig, no open ports
To bring a cluster into AI SRE we wanted three things at once: no public exposure, tight permissions, and no hand-written tool list. What we shipped runs real kubectl, has your cluster dial out to us, and leaves every permission decision to Kubernetes.
Flashduty Engineering
Introducing AI SRE Artifacts
Reports, design documents, and pages from your AI SRE sessions can now be published as artifacts. An artifact does two things: it stays, with its own address in the team gallery, and it goes out, over a public link that needs no sign-in.
Flashduty Product
Working at 3 a.m.: five ways to use AI SRE Automations
Five ways to use Flashduty AI SRE Automations — weekly insights, alert governance, incident analysis, deploy checks, change risk reads — each with the exact task prompt, plus how results reach people.
Flashduty Product
Introducing GitHub and GitLab Apps for AI SRE
AI SRE can now connect to your GitHub organization or GitLab instance: it reads recent commits during an investigation, reads the failing CI logs on its own, and opens PRs for small fixes. You never paste a token.
Flashduty Product
From MCP to a CLI: how our AI SRE operates all of Flashduty
In January we wired a built-in MCP server into every agent session. By late May we had replaced it with a CLI. Why we didn't expand the MCP, why we passed on search-based loading, and what the switch cost us.
Flashduty Engineering
From a Real User Error to a Fix PR in 8 Minutes: RUM × AI SRE
A user hit three frontend errors while creating a monitoring rule. RUM preserved the session, version, and SourceMap stack; AI SRE located the right repository, made a one-line fix, and opened a PR.
Flashduty Engineering
Sending Alerts to a Group Chat Does Not Mean Someone Owns the Incident
Group chat alerts improve visibility, but they do not create ownership. Real incident response needs an owner, acknowledgment, escalation, closure, a timeline, and reviewable follow-up.
Flashduty Product
A CLI for humans and agents
Why an incident response platform builds a CLI at all, and why we made it the entry point for AI coding agents to operate Flashduty — an engineering note on CLI design tradeoffs.
Flashduty Engineering
An SDK shouldn't be smarter than its API
go-flashduty is the official Go client for the Flashduty Open API: thin, strongly typed, and generated from an OpenAPI spec. We want to talk about how to design and maintain an SDK spanning 27 services and 253 endpoints — why we chose codegen over hand-writing, why we keep a strict 1:1 boundary with the API, and how that boundary keeps the SDK from rotting over the years.
Flashduty Engineering
We stopped writing docs by hand
A small team with no dedicated product manager built an AI agent to find hundreds of documentation gaps, write the missing docs, and open PRs. The fix was not asking engineers to remember docs; it was making drift visible.
Flashduty Engineering
How to Turn an Alert Storm Into Actionable Incidents: A Practical Noise-Reduction Playbook
A Flashduty noise-reduction playbook covering events, alerts, incidents, label enrichment, Pipeline cleanup, grouping, storm warnings, flapping detection, silences, suppression, and a 14-day validation method.
Flashduty Support
Is PagerDuty Too Expensive? How to Calculate On-call Cost for a 100-Person Engineering Team
A cost model for comparing PagerDuty and Flashduty On-call: responders, notification-only users, licenses, communication quotas, Add-ons, and the questions teams often miss.
Flashduty Product
Is Alertmanager enough?
Where Prometheus Alertmanager ends and a dedicated On-call platform begins: routing, schedules, automatic escalation, incidents, IM collaboration, and analytics — with a side-by-side selection table and a concrete path for connecting Alertmanager to Flashduty.
Flashduty Product
Flashduty Monitors now supports Loki and VictoriaLogs
Flashduty Monitors supports Grafana Loki and VictoriaLogs with native query syntax, three alerting modes, separate recovery logic, and raw log samples in alert messages.
Flashduty Engineering
Scheduling is the easy part
Integration, label enrichment, grouping, suppression, schedules, escalation, acknowledgement, collaboration, notification, analytics — every stage of On-call explained, along with how far to push each one and where the traps are.
Flashduty Product
On-call practice in the futures industry
Futures trading spans multiple sessions and runs under tight latency and risk-control requirements. This case shows how one futures company used a unified monitoring and incident response platform to speed up alert response and reduce operations pressure.
Flashduty Support
Don't let on-call burn out your best people
Plenty of teams claim everyone is on-call, and yet the most conscientious person ends up doing the most work, getting the most average review, and quitting. Here is how to make on-call both fair and sustainable, plus a checklist of anti-patterns to avoid.
Flashduty Product
How Google and Datadog run on-call
Google open-sourced Borg into Kubernetes and Borgmon into Prometheus. So what about Outalator, its internal on-call tool? We unpack the mature on-call practices at Google SRE and Datadog, show why the hard part was never the tooling, and look at what teams can actually borrow.
Flashduty Product