Operations | Monitoring | ITSM | DevOps | Cloud

In order to have the most successful deployment, there are a few best practices that software development teams should be mindful of. First, following a continuous delivery approach allows software development teams to release in shorter cycles, so that building, testing, and releasing can be done with greater speed and reduced error rates. As stated in an earlier post of ours, you’re doing continuous delivery when: Your software is deployable throughout its lifecycle.

As of October 15, 2020, Mattermost Extended Support Release (ESR) version 5.19 will no longer be supported. If any of your servers are not on ESR 5.25 or later, we highly recommend that you upgrade immediately. With our simple upgrade steps, it takes only a few minutes. Mattermost adopts a monthly tick-tock release cycle, with a new version shipping on the 16th of each month.

With one of the largest threats to a company’s security and privacy being its own employees, having employees work remotely only adds to the risk. While this year’s Verizon Data Breach Investigations Report chalks it up to internal errors rather than intentional malice, the threat remains. Many corporations have sent employees to work from the confines of their homes, creating a greater need for protection against data and security breaches.

Who doesn’t like a good ole’ game of “Guess how many M&Ms or marbles are in that jar”? Are you off by 20, 50, or by a couple hundred? Or maybe you’re fairly close estimating the number of spheres in a confined space. Now think about your IT assets in your organization. Are all of them accounted for? Where are they located? Take a guess. Guess again. A miss is as good as a mile.

In previous and great articles in here, we already talked about what Cloud is and the types that exist floating above our heads. But today, for a change, we want to focus more on one of its totally forgotten key aspects: Are clouds actually made of childish dreams and cotton candy? No! Just kidding! Today we are going to talk in “Pandora FMS discussions” about what cloud service types there are.

In theory, the default monitoring check settings should work in the majority of cases. However, everyday practice shows that our case does not belong to this majority. Therefore, it is necessary and worthwhile to dedicate some time to the optimal configuration of monitoring. It is also important to properly prepare the monitored website and the organization itself.

In order to have the most successful deployment, there are a few best practices that software development teams should be mindful of. First, following a continuous delivery approach allows software development teams to release in shorter cycles, so that building, testing, and releasing can be done with greater speed and reduced error rates.

Untangling a chaotic mess can be daunting. And that’s exactly the problem Alain Adler, the Head of Engineering at BetterHelp, faced.

Continuous Integration and Continuous Delivery (CI/CD) delivers services fast, effectively, and accurately. In doing so, CI/CD pipelines have become the mainstay of effective DevOps. But this process needs accurate, timely, contextual data if it’s to operate effectively. This critical data comes in the form of logs and this article will guide you through optimizing logs for CI/CD.

Microservice architecture is widely popular. The ease of building and maintaining apps, scaling CI/CD pipelines, as well as the flexibility it offers when it comes to pivoting technologies are some of the main reasons companies like Uber and Netflix are all in on this approach. As the amount of services in a microservice architecture rises, complexity naturally also rises.