Operations | Monitoring | ITSM | DevOps | Cloud

It’s been a few years since the “Spotify Model” became the latest trend for structuring an engineering team. But, like its predecessors, the model based on tribes and squads has some pitfalls. How to structure an engineering team is a question that’s been covered at length, from the strengths and weaknesses of common team structures to a matrix of organization based on risk and scale to why you should choose your own model.

On any given day, we use rideshare apps to get from one place to another. We check public transportation apps to see when the next train is arriving at the station. We use streaming services to watch Frasier at the end of lo-ooo-ng work days. As part of engineering teams, we use application monitoring and cloud services (like CI and cloud infrastructure) to function, so that code changes seamlessly deploy into production.

ITOps teams are challenged today like never before, overwhelmed by IT noise and constantly fighting fires. And for the business this often means higher operating costs, performance and availability issues, and risks to enterprise digital initiatives. So what’s an IT Ops guy/gal gotta do? Well, lately there’s been talk about “a new sheriff in town” that claims to be able to solve this challenge, and its name is AIOps.

It’s been an exciting couple of weeks and we have been hard at work to give you the best possible status page and monitoring experience, and so here is a highlight of the new features we are the most proud of.

IT service alerting (ITSA) tools automate ticketing system workflows by incorporating intelligent alerts into the creation of a ticket. These capabilities don’t only enable IT support teams to consistently deliver great services, but they also improve their collaboration and productivity. That’s why in order to extract the full value from ticketing systems, teams should consider closing the loop by complementing their ServiceNow instance with trusted ITSA solutions such as OnPage.

In the past I’ve written about how to use informers in Kubernetes for particular resources, but what if you need to be able to receive events for any Kubernetes resource dynamically? Well, there’s a client-go package for that too. At FireHydrant, we recently updated our Kubernetes integration to watch changes for any resource you configure and I wanted to write down how we made it at a high level.