The Monitoring Stipulation

  Filed under: Monitoring
  Comments: None

As we embrace the digital transformation in our lives, IT organizations also needs to transform their operations to enable it.  As new services models around IOT and cloud emerge, the monitoring tools must adapt to fit the stipulations of the IT teams. With every new service or enhancement, there has to be a requirement analysis done for monitoring it.

Each tier within the IT organization must identify these monitoring requirements, aligned to their roles and KPI’s.

  1. Support and Operations Team:- This team is responsible to detect and resolve services problems and to proactively manage the IT infrastructure. Common parameters of interest are availability, temperature, bandwidth, processes, queries , utilization of CPU’s, memory and storage etc. Above and beyond, the team needs to consider what if scenario’s, automation of the routine monitoring tasks and root cause analysis while building their monitoring strategy. The SLA’s which can be committed to the customer depends upon what exactly this team can monitor.
  2. Operations Management :- This tier is responsible for continuous operations of the IT environment and to provide governance. Beyond the technical stats, they need to monitor fault and performance trends, vendors performance, service delivery against the SLA’s, validity of licenses etc. Operations management relies heavily on an agile reporting engine in monitoring tools to crunch out custom reports to various vendors, field operations and higher management based upon historical and real time data.
  3. Chief Information Officer:- The CIO’s have overarching responsibility of end to end service delivery, across the entire IT infrastructure. Rather than monitoring various layers within the IT environment like network, compute, storage and operating systems, CIO’s are more concerned about complete service delivery like Wi-Fi service, CRM, ERP and billing etc. Hence the need for features like dependency maps, rules engines and artificial intelligence in the monitoring tools. These techniques abstract the underlaying infrastructure performance into service level monitoring. This concept is commonly called conditional monitoring.

The monitoring tool should be customizable to meet specific use cases of the organization. This needs a mind shift  from getting it “off the shelf” to “tailor-made”. Opensource, global collaboration and enhanced skill levels of resources in programming and scripting are fueling this shift already.

Forward looking IT organizations avoid tool sprawl into their environments. They come together to articulate their requirements and select a tool which addresses them all, and the best.

For more information, please visit

Be the first to write a comment.

Your feedback