Operations | Monitoring | ITSM | DevOps | Cloud

The widespread adoption of mobile apps is driving workforce productivity from almost anywhere across nearly every industry. Workers are relying on mobile technologies more than ever to get their work done every day—from short-staffed nurses who need to update information on the go to field service technicians who need to complete tasks and access critical information in real time to desk workers who need visibility into communications and company resources from anywhere.

I don’t care about religious wars over “which logger is the best”. They all have their issues. Having said that, the worst logger is probably the one built “in-house”… So yes, they suck, but re-inventing the wheel is probably far worse. Let’s discuss making these loggers suck less with proper usage guidelines that range from the obvious to subtle. Hopefully, you can use this post as the basis of your company’s standard for logging best practices.

We have many articles on what Qovery is and how to use it, but today we cover a critical topic: security! Protecting your business is probably one of the most important criteria when choosing a product, and here at Qovery, we take this topic very seriously, so let me ease your mind and show you what makes Qovery secure 🔒

When IT operators and architects begin their journey with Google Cloud, Day 0 observability needs tend to focus on infrastructure and aim to address questions about resource needs, a plan for scaling, and similar considerations. During this phase, developers and DevOps engineers also make a plan for how to get deep observability into the performance of third-party and open-source applications running on their Compute Engine VMs.

Let’s face it. Incidents can be expensive—really expensive. But the high cost of incidents within a production environment isn’t always due to a compromised service or negative customer experience.

I recently had a wonderful opportunity to contribute to the Computer Weekly Developer Network (CWDN) ultimate series on “Infrastructure as Code” that collected articles and overviews from vendors and experts operating in the IaC space to form a formidable reference on all aspects of IaC. My contributions were to offer some insight into our architecture that has been designed to monitor infrastructure that has been deployed as code automatically and without tedious manual configuration.

It’s been a week. A long week. After the most recent Board of Directors meeting, your senior leadership tasked you with finding a security analytics solution. Over the last month, you’ve worked with leadership to develop some basic use cases to determine which solution meets your security and budget needs. You started your research, but everything on the market seems really overwhelming.

The one certainty you will find in IT, developer, and SRE roles is that things always change! One hot topic in DevOps communities is observability. A long word, you may be wondering what it really means and how you can add it to your skillset. Here’s a quick primer to get you going on your path to observability.

Automation goes beyond just building solutions to replace complex or time-consuming manual processes. As the popular saying goes, “anything that can be automated should be automated.” For example, deploying updates to applications can and should be automated. In this tutorial, I will show you how to set up hands-free deployment of a FeathersJS app to Heroku.

On March 30th, 2022, rumors began to swirl around a GitHub commit from a researcher containing proof of concept (POC) exploit code. The exploit targeted a zero-day in the Spring Core module of the Spring Framework, and was quickly confirmed against specific versions of Spring Core with JDK 9 and above. Anything running Tomcat is most at risk given the POC was based on Tomcat apps. This threat posture will evolve over time as new vectors and payloads are discovered and distributed.