Operations | Monitoring | ITSM | DevOps | Cloud

A few years ago, monitoring was simple. We had all our servers somewhere in the data center; we just had to install a monitoring tool and gather all the data from every server. Things changed when we started moving to the cloud and then to containers. Today, we often need to monitor a variety of different sources. A “server” can be a physical machine, virtual machine, container, or even a serverless application. Therefore, our approach for monitoring needs to change.

Heading to the gym, you have access to so many amenities in one place: cardio equipment, private studios, a pool, free-weight area, a basketball court. Imagine if those conveniences were located at separate facilities, forcing you to have separate memberships and make different trips to achieve a well-rounded workout – it doesn't bode for the best experience. In a different context, think about your employees' experience as they search for answers across multiple platforms for service providers.

The simplest way to ensure the safety of all the open source (OSS) components used by your teams and sites, is with a software composition analysis (SCA) tool. You need an automated and reliable way to manage and keep track of your open source usage. With JFrog Xray, you can set up vulnerability and license compliance scanning built into your software development lifecycle (SDLC).

We recently released the Lumigo Dynamic Dashboard to help our customers visualize metrics to monitor their environment the way they want.

There’s no question that the cloud offers efficiencies and innovation opportunities that are near impossible to replicate on-premise. In fact, Amazon reports that companies achieve 31% infrastructure cost savings, as well as 62% more efficient IT infrastructure management, when they move to AWS (and that doesn’t include the many other cost benefits — like improved security and on-demand services). But the extent of those efficiencies can vary.

We’re excited to present a feature update to the OnPage platform. The new update will bring more flexibility and resiliency to a team’s on-call management workflow. With the new scheduling capabilities, OnPage system administrators can create exceptions to configured, recurring on-call schedules.

COVID-19 certainly accelerated some trends. For example, in my view, COVID-19 accelerated the pace and progress of digital transformation by five to 10 years, as companies faced the need to adapt to a post-COVID-19 world, involving permanently the higher adoption of remote work, remote education, and digital touch-points. Technologies requiring less human touch and more digital touch-points will be adopted faster in the aftermath of COVID-19.

No user likes to spend time waiting for a web page to load. No web developer likes a website or app to fail either. It’s important to focus on creating quick loading pages with error-free code. JavaScript is used to build the majority of the dynamic, real-time applications. JavaScript’s strength is in the context of apps that update content dynamically with minimal latency. JavaScript performance testing should be a priority for ensuring a good end user experience and optimal performance.

Keeping up with customer demand and staying ahead of the competition requires fast releases and efficient code. This is where DevOps comes into play. Where DevOps is the practice, mindset, and culture of combining software development (i.e. Dev) and IT operations (i.e. Ops) to accelerate the development lifecycle and provide continuous delivery without compromising quality.

During the next eight weeks, our team will work to improve the overall experience of Qovery. We gathered all your feedback (thank you to our wonderful community 🙏), and we decided to make significant changes to make Qovery a better place to deploy and manage your apps. This series will reveal all the changes and features you will get in the next major release of Qovery. Let's go! Read the previous article: The Future of Qovery - Week #2.