Operations | Monitoring | ITSM | DevOps | Cloud

StatusGator now monitors more than 10,000 services. Cloud platforms, AI tools, payment providers, communication apps, developer infrastructure, school software, business SaaS: if your team depends on it, there is a good chance we are already checking its status page. We started in 2015 with a few hundred providers and one idea, that nobody should have to keep multiple vendor status pages bookmarked to find out why the office suddenly cannot log in.

Every SRE team operates services it cannot see into: a vendor binary, an inherited legacy deployment, a container whose owning team dissolved two reorgs ago. The routes are undocumented, the dependencies are unknown, and when a request takes 130 milliseconds nobody can say whether that time is application work or a wait across a network boundary.

For food and FMCG companies, managing freezers becomes more complex once equipment moves outside warehouses and company facilities. Freezers may be placed at supermarkets, retail stores, restaurants, distributors, convenience stores, and other customer locations, often across hundreds of cities or territories. At that scale, spreadsheets and manual field checks make it difficult to answer basic operational questions. Where is a particular freezer? Which outlet is responsible for it?

Icinga Director’s CLI commands have supported import sources and sync rules for a long time, which includes listing, checking and running them. Before Icinga Director v1.11.6 two things you couldn’t do from the CLI, though, were narrowing a health check down to a single object, or deleting an import source or sync rule without opening the web UI. I’ll walk through both, using examples.

If your engineering teams run on ServiceNow, incidents are where they get work done. Putting cost work into an incident gives it the same path to resolution as any other work item your team handles. When a cost anomaly arrives as an incident, your teams route it, assign it, and resolve it on their usual SLAs. When a savings recommendation arrives as an incident, an engineer owns it and acts on it. Now you can send either straight into ServiceNow.