Operations | Monitoring | ITSM | DevOps | Cloud

You’ve forgotten to add frontend validation to number fields, and now people are getting an error when they enter text into those fields. However, this is an issue that’s easily preventable—by implementing a proper test that checks for edge cases, but how do get started with software testing? Avoiding bugs in production is just one advantage of testing, it also helps you be more confident about your applications, opens up the potential for a full CI/CD pipeline, and much more.

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.

An on-call schedule forms the backbone of your incident response system in the event of an outage or when an issue is raised. This type of schedule does not keep end-users waiting and helps maintain the reliability and availability of your software. However, on-call management practices often induce worry and anxiety in team members. In extreme cases, it can even be a contributing factor in employee burnout.

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.

As you may have heard, Microsoft has just released the highly anticipated SCOM Managed Instance (SCOM MI) – cloud-hosted SCOM. In conjunction with this, we have launched a plugin for SquaredUp that lets you connect straight into SCOM MI and pull all the monitoring data you need!

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.

It feels like everything is getting a “smart” upgrade these days. From the cars we drive to how we operate our domestic appliances, almost every gadget has had a smart upgrade or now uses Artificial Intelligence (AI) to improve our lives – or so they claim…

Uncertain times are often a catalyst for important innovations. During the Great Depression, for example, inventors created nylon, magnetic tape recording, and the first working helicopter—all of which are still in use today. To be prepared for the future, you need to take stock of where you’ve been, what you’ve accomplished, and where you want to go. Let’s look at four tech trends that are resonating with ServiceNow customers.