The Start of the Monitoring Journey in DevOps

Under pressure to innovate and deliver rapid updates to their applications, developers often place monitoring as an after-thought. In today’s world, where a slowdown can translate to customer attrition and an outage can lead to millions of dollars in losses and negative press, ensuring satisfactory response time has evolved to be one of the most critical needs in the early stages of development and is a common goal to ensure DevOps success.

The Shift-Left of Monitoring: To study emerging patterns of how and when DevOps teams start monitoring, we interviewed several DevOps squads. Almost unanimously the responses were:

  1. They care most about knowing, Is the application up and loading quickly? Are all critical user interactions with the application responding within acceptable standards?
  2. They would like to get this information proactively throughout the development life cycle so they can determine if any code check-in impacted the performance/
  3. They would like to monitor with minimum setup and configuration and don’t have the time to learn complex tools/

To satisfy these needs, synthetic monitoring becomes the starting point for monitoring.

Read more at :


About itspi
Product Manager at IBM, Cloud and Analytics Geek, Mixed Media Artist, Traveler, Volunteer for Non-Profits

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: