Operations | Monitoring | ITSM | DevOps | Cloud

A volatile economy, a disrupted supply chain, a widespread talent shortage, and environmental challenges have left many business leaders wondering how to move forward. In this environment, change is the only constant. Navigating these headwinds requires evolving your relationship with global uncertainty and seeing the creative opportunities it presents. ServiceNow’s Workflow special report, From adversity to advantage, offers an actionable framework for making this essential pivot.

ESnet (Energy Sciences Network) is a high-performance network backbone built to support scientific research. Funded by the U.S. Department of Energy and part of Lawrence Berkeley National Laboratory, ESnet provides fast, reliable connections between national laboratories, supercomputing facilities, and scientific instruments around the globe. Our mission is to allow scientists to collaborate and perform research without worrying about distance or location.

Kubernetes has clearly established itself as one of the most influential technologies in the cloud applications and DevOps space. Its powerful flexibility and scalability have inarguably made it the most popular container orchestration platform in modern software development, helping teams manage hundreds of containers efficiently.

Elastic Observability provides a full-stack observability solution, by supporting metrics, traces, and logs for applications and infrastructure. In a previous blog, I showed you how to monitor your AWS infrastructure running a three-tier application. Specifically we reviewed metrics ingest and analysis on Elastic Observability for EC2, VPC, ELB, and RDS.

We’ve written a ton of content about how to unlock the value of frequent deployments for your database as well as applications, from improved coding patterns to strategies for architecting smaller deployments. But the multi-million-dollar question for you and your business is something else entirely: what is the real business value of frequent deployments? That’s the question I’m going to address in this series of three posts.

As an organization grows, so does its business and IT infrastructure. The relationship between assets gets more complex, so it becomes essential to keep a map of that ecosystem to anticipate issues, optimize your budget, and reduce downtime. That’s exactly why you should learn how to build a CMDB (Configuration Management Database).

Most SaaS products have nice, organic growth when they work well. Employees log in, they click around and make stuff, then they share links with others who do the same. After a few weeks or months, there are thousand of objects. Some are abandoned, and some are mission-critical. Different people also bring different perspectives, so they name things that are relevant to their role and position in the team, which may be confusing to others outside their realm.

Better Uptime is a robust uptime monitoring and tracking tool that helps businesses ensure the availability and reliability of their websites and online services. It continuously monitors the performance and availability of a website or application and provides real-time alerts and notifications in case of disruptions or outages. They also provide a relatively simple status page, albeit gorgeous looking and useful for some simple use cases; your team will, in all likelihood, outgrow it at some point.

An important part of the client-service provider relationship is a well-written Service Level Agreement (SLA). Most service providers and clients agree on this. What some service providers don’t know is exactly how they should measure SLA. There is often a lot of confusion between the SLA metrics that define contractual agreements and the wide range of key performance indicators (KPIs) you can also use to monitor operations. They are both important, but they are not the same.