Product/Monitoring
The system that watches itself
The strategic fifth part: response times and the database, buy links and prices, duplicates and formats, the publishing schedule, the audience in real time and the sources' health – checked around the clock, with alarms where you work.
Why
Money is lost silently – unless someone is looking
A small media company cannot check twenty thousand articles, thousands of buy links and a database around the clock. Monitoring does, and raises the alarm where you work.
In legacy systems
A broken buy link is not seen until the network stops paying. A stale price costs trust. A missed schedule leaves a hole. A slow database logs the newsroom out mid-work. Nobody notices, because nobody can look everywhere.
In VOR
The checks are run by the system, every hour and every day, and whatever is wrong comes to you as an alarm with what it costs and what to do.
Grow without growing
A media company that can grow in content and revenue without growing in staff – and a management that knows the figures are right because someone is watching them.
Every rule is a guard
The newsroom's rules – hero size, tags, no outbound links, the store's own price – are not a document. They are checks the system runs.
Never unpublish, never delete
A guard points, a person fixes in Studio, the guard checks again on its next run and closes the alarm when it is green.
System errors
What cannot be fixed in Studio goes to the system's agent, which puts the cause and the action in the order queue and in the evening report.
Five areas
The system, the money, the content, the audience, the world
The system
The performance check measures response times on the site, in Studio and in the panel around the clock, checks the database, the import, the queue and the releases. A database hiccup never logs anyone out – the page says “one moment” and reloads.
The money
The link guard fetches published pages every hour, decodes every buy link as a browser would and judges it – broken, works but without article id, not responding – with the revenue at stake. The revenue leak is followed per month. The price guard corrects prices without unpublishing.
The content
The duplicate guard (the same article never twice – in the import, in Studio and on the home page), the format guard before publishing, days short of the base schedule, failed releases, a late first draft, language versions missing or needing an update.
The audience
Real time minute by minute, drops against the same time yesterday, pages that stopped responding, keywords without hits that keep growing.
The world
The sources' health – which feeds respond – Google Trends gaps (topics being googled but never written), campaigns that are expiring.
Where you see it
The order queue (alarms as urgent orders with measurement, cause and action), Insights › Home (Alarms and health, the leak), the link guard, Studio's overview (failed releases, to do), the evening report – and Ask VOR: “Are there any alarms right now?”
How an alarm is handled
Four steps, never a deletion
The alarm says
What is wrong, since when, and what it costs – revenue per page, articles affected, visible to users or not.
Open and fix
The article, the product block, the release – in Studio. Never unpublish, never delete.
Republish or rerun
The guard checks again on its next run and closes the alarm when it is green.
System errors
Go to the system's agent, which puts the cause and the action in the order queue and in the evening report.
What runs by itself
The clock the system keeps
- The big hero switches to the next article in the rotation.
- Legacy CMS sync – changes made in the old system come in as a new revision. The shopping rows switch shopping edit.
- The order queue is emptied by the system's agent. The link guard fetches twenty published pages and clicks every buy link through. The performance check measures response times.
- The menu row is recalculated by yesterday's page views.
- The day's first draft is ready, and the morning brief sums up the night.
- The whole archive passes the link guard; the revenue leak is updated; the trend watch reads over a hundred sources around the clock.
- The evening report to management: money, articles, traffic, most read, what was published, the day's alarms and what was fixed.