Operations | Monitoring | ITSM | DevOps | Cloud

The ITIL definition of an incident is “an unplanned interruption to or a quality reduction of an IT service”. In your IT ecosystem, an incident may be caused due to a malfunctioning asset, or a network failure. Common incidents include issues with the printer, Wi-Fi connectivity, application locks, email service, laptop, file sharing, unresponsive servers, or even authentication errors.

At InfluxData, we pride ourselves on building a platform – InfluxDB – for developers, by developers. It’s not enough to simply “talk the talk.” As an engineering leader, it’s really important to me that InfluxData “walks the walk,” too. This requires a holistic understanding of our users, their familiarity with time series, the environments in which they work, and the problems they’re trying to solve.

For IT and EUC teams, reducing costs is easier said than done. You can’t just blindly reduce headcount, delay transformation projects, or extend hardware lifecycles in the hopes of appeasing your CFO’s demands for short-term cost reduction. The reality is, rushed cost-cutting will put your service desk under pressure. In turn, such self-inflicted inefficiencies will only result in performance degradations, additional tickets, and escalations.

With organizations across industries facing inflationary pressures and the threat of recession, CFOs are forced to impose cost-cutting measures to improve cost efficiency across teams to tide through these tough times. This has resulted in IT teams being faced with a dilemma. How to improve the cost-effectiveness of the team without impacting employee satisfaction and service desk productivity?

AWS re:Invent was back and BIG last week in Las Vegas. Approximately 50,000 AWS customers and partners got together in Las Vegas to learn, talk shop, and maybe attend a couple of parties here and there. Not only did Lumigo have a booth, but our own Saar Tochner, R&D Team Lead and AWS Community Builder gave a well-received talk on Lambda extensions.