The shift to cloud computing and the DevOps revolution have fueled some important changes in the way we think about software development and monitoring. It has delivered huge benefits to the companies that have fully embraced the approach. In fact, the DevOps Research and Assessment (DORA) 2018 industry survey found a new small group of “elite” performers that are deploying code far more often and having a far better mean time to resolution (MTTR) than the next closest group.

The world of mobile phones is growing at a higher pace by changing the face of digital publishing. Such a rapid change is figured out from Google as it has led to the development of new handful technology which is designed for delivering faster and richer mobile experiences to the users. This is related to the Accelerated Mobile Pages (AMP) by Google and Progressive Web Application (PWA).

When you build and deploy an application, chances are that you need to store some form of secrets. These are typically things like credentials for 3rd party systems and database credentials. As an ASP.NET Core developer, Microsoft provides you with an easy way to store secrets like these in your development environment, namely the Secret Manager.

Monitoring backend issues is critical for ensuring that requests are handled in a timely manner, and validating that your services are accessible to users. But if you’re not tracking client-side errors and events to get visibility into the frontend, you won’t have any idea how often these issues prompt users to refresh the page—or worse, abandon your website altogether.

Five worthy reads is a regular column on five noteworthy items we’ve discovered while researching trending and timeless topics. This week, we define what data sprawl is and how organizations can cope with it effectively. Data sprawl—defined as the proliferation of data into endpoints, servers, applications, BYODs, operating systems, network environments, and even other geo-servers—can be a challenge to monitor and control.

There is no doubt that looking at response times and memory usage is essential to understanding the general health and performance of your application. But as I am sure you are aware, there is more than one way to monitor an application. Approaching monitoring from a different angle can be a powerful way of gaining new insights. If all you did was watch for high response times or areas of memory bloat, then you might overlook something far more simple: the user’s general level of satisfaction.

In this blog post we are going to cover how to perform Docker image scanning on the Gitlab CI/CD platform using Sysdig Secure. Container images that don’t meet the security policies that you define within Sysdig Secure will be stopped, breaking the build pipeline before being pushed to your production Docker registry.

Research firm IDC predicts that overall data volumes will grow from 33 zettabytes in 2018 to 175 zettabytes by 2025. 50% of the data will come from IoT devices and nearly 30% of the data will get consumed in real-time by 2025. The data economy has changed the game on how enterprises will need to work with digital technologies to become more effective, competitive, and innovative.

As many of you know, Gartner is recognized as one of the premier analyst firms by most enterprise IT organizations. Given the broad and diverse set of customers Gartner serves -- many risk averse and conservative towards new technologies, Gartner generally tends to recommend incremental and measured changes. Imagine our surprise when Gartner made this very bold statement "on-premises is the new legacy.

Mean time to resolution (MTTR) is defined as the sum of the total amount of time that service was interrupted divided by the number of individual incidents. The unit of measurement is some quantity of time. Ideally, you can use minutes as the unit. That is, unless you blacked out the eastern seaboard for weeks!