Operations | Monitoring | ITSM | DevOps | Cloud

Almost everyone nowadays understands what machine learning is. Some of the most exciting machine learning trends in the coming years have the potential to completely transform our current social, industrial, and economic structures. Furthermore, the machine learning industry is rapidly expanding, opening up a plethora of opportunities for business expansion.

Traditionally, provisioning an infrastructure meant a team of field engineers, system admins, storage admins, backup admins, and an application team would all provision and maintain an on-premises data center. Although this system works, it has a few flaws—slow deployment, high cost of setup and maintenance, limited automation, human error, inconsistency, and the underutilization of resources during off-peak periods.

In case you missed it, for several hours on December 7, 2021, AWS's us-east-1 region had an outage impacting multiple AWS APIs, taking out various websites across the internet. According to our own monitoring at OnlineOrNot, the outage started at 2021-12-07 15:32 UTC and began to recover well at 2021-12-07 22:48 UTC (with minor signs of life for a few minutes around 2021-12-07 20:08 UTC). Had we relied solely on AWS to update their status page before reacting, we would have been waiting a while.

In the first part of this series, we outlined the basic steps you need to take in order to begin setting up a developer environment, installing your first app, and making use of the first commands. In this installment, we’ll aim to answer the most common questions about what was installed, how it works, and how the various pieces interact with each other. Additionally, this post will lay out all the different components that are involved in the overall lifecycle of a Mattermost app.

ITAM and ITSM are two of the most ubiquitous terms used in the ITOps domain. However, the use cases and working methodologies are completely different. These are two ways to manage the IT operations of an organization, focusing on two distinct aspects: One focuses on managing all hardware and software assets, and the other, delivering IT services most efficiently.

Before I introduce myself, I first want to highlight a monumental day in our company’s story. Today, we begin writing a new chapter under a new company name. We’ve decided to name the entire company after our flagship product, the ultra-popular GitKraken Client. Why make this move now? It’s much more than a cosmetic name change. Today ushers in the next phase in our evolution – one in which we will become the premier provider of Git tools for developers around the world.