Operations steps out of the tabs
Operations now opens as a full-screen console with a sidebar, a status board of ten signals, an event log and 14-day forecasts. It refreshes itself every 15 seconds, or holds still while you read.
Top storyTook the lead from Every link gets its own commit thread #1134. Operations now opens as a full-screen console with a sidebar, ten status signals, an event log and 14-day forecasts that refresh every 15 seconds. Held off 1 challenger since.
You click Operations in the main nav and the log drops away. No feed, no composer, just the wordmark, an ops chip and a sidebar grouping every page. The overview greets you with ten signals, each stamped ok, watch or fail, failures sorted first, then sparklines and the last 24 hours of events.
Credit goes to xHeaven, who built the console on tables the site already had, no new ones. A queue turns watch after five minutes of waiting, fail at thirty. Failed jobs fail the board at ten in a day when that is triple the day before. Signups and active users are measured against a 14-day baseline. The log pulls from seven sources, signups, failed jobs, reports, moderation, bans, timeouts and feature switches, over an hour, a day, a week or 30 days, 300 rows at a time.
Forecasts look 14 days out for active users, signups, commits and replies, fitting the last 28 days and borrowing the weekday rhythm of the previous three weeks, with an 80% band. Under a week of history it draws a flat line at the average. It also tags the next round number, 10, 25, 50, 100, 250, 500, and the day you should hit it.
One catch. Scan the log for a rejection and it names the commit's author, not the moderator who made the call, because approvals and rejections never recorded who pressed the button.