Operations | Monitoring | ITSM | DevOps | Cloud

Incident severity levels are a measurement of the impact an incident has on the business. Classifying the severity of an issue is critical to decide how quickly and efficiently problems get resolved.

We’ve reached the final piece of our five-part series, and while I’m sad to end it, I hope you or your DBA teams have learned enough to move forward with the Information Management Maturity Model (IMMM). Although there are five steps to this model, several DBAs stop at the fourth. It’s common for large organizations to give this step to management and higher-ups, rather than DBA teams.

As technical professionals we spend a lot of time developing technical skills. Checking the right boxes of experience with languages, tools, and technologies is what typically lands us a job interview for our specialty. But what wins the job in DevOps — and carries you to success in it — are your human skills. Even more than technical chops, personal traits like mindset, communication skills, and work habits are your strongest assets in making DevOps work.

The largest remote working experiment the world has ever faced is entering a new phase as the era of hybrid work begins. For IT and DevOps teams on the frontline, this is a time of enormous pressure. Along with its many benefits, hybrid working can also bring considerable disruption. Enabling and supporting the hybrid model is the next big challenge facing organizations around the globe. We wanted to find out what this new reality means for these teams.

In a previous post, we described how we envision cloud-native initiatives reaching the 2.0 phase, where phase 1 was centered around providing clusters and running its underlying infrastructure effectively. Now that teams are starting to move some of their existing services to a microservices architecture, developers and platform engineers are being tasked with implementing the right policies and governance controls to ensure applications are running as securely as possible.

Let’s step back and take a very basic look at DHCP. In fact, let’s look at the analogy of assigning a street address to your house. Usually, this is done by the local 911 dispatch office, or some other central authority. They typically use either a survey map or a latitude, longitude pair to locate you, before they assign your house numbers from a pool of available addresses, compatible with other addresses in the area.

Two factor authentication (2FA) increases your account security further than just using a username and password. In addition to a password (the first factor), you need another factor to access your account. A great example to demonstrate this is when you withdraw money from an ATM. To access your bank account you need both your physical bank card and to know your PIN number. These are the two factors you need to withdraw money = 2 factor authentication!

Have you ever heard the mantra “Don’t deploy on Fridays?” There are blog posts, tweets, and t-shirts shouting this slogan to anyone who will listen. Maybe your organization follows this policy. The purpose of not deploying on Fridays is to give the team better work/life balance by preventing them from having to work on the weekends if something goes wrong during or after the deployment.

We’re delighted to announce the freshly-updated JFrog Technology Partner Program, a powerful initiative that will elevate our already large and vibrant ecosystem of integration partners and strengthen JFrog’s “too integrated to fail” commitment to its customers and the DevOps community. The program is a natural next step for JFrog.