Monitoring Types

I often get asked when discussing operational activities or event management about how we should monitor our environment. There are several methods to accomplish this depending on what you’re monitoring, what resources you have available and the criticality of what you’re monitoring. Defining these elements will then help you choose one or more of the following methods.

Active monitoring:

Ongoing device interrogation to determine its status.
Resource intensive.
Usually used proactively for critical devices or systems

Passive monitoring:

Transmits event to a listening device.
Most commonly used method
Requires good definition of events and instrumentation of systems being monitored.

Reactive Monitoring:

Requests or triggers action following an event or failure
Used for exceptions and normal operations
Can be used to diagnose which device is causing the failure and under what conditions.

Proactive Monitoring:

Used to detect event patterns that can indicate a system or service is about to fail.
Used to determine real time status of a device or system
Usually used for critical components or following the recovery of a failed device to ensure full recovery has taken place
Records are correlated over time to build trends or patterns. These patterns are then defined and programmed into correlation engines for future recognition.

Continuous Monitoring:

Focus on real time monitoring to ensure compliance to a performance norm.
Differs from Active Monitoring which may not be continuous.
This, like Active Monitoring, can be resource intensive so normally reserved for critical services or components.

Exception –Based Monitoring:

Does not report on real time performance but detects and reports on exceptions.
Less resource intensive more cost effective.
May result in lengthier outages (reactive).
Used on less critical systems or services.
Use must be reflected in SLAs and OLAs.

Comments

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.” Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...

What Is A Service Offering?

The ITIL 4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group. As a service provider, we can’t stop there! We must know what the contracts of our service offering are and be able to put them into context as required by the customer. Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include: Goods, Access to Resources, and Service Actions 1. Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods. Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you. You the consumer own these and they are yours to take with you. ...

What is the difference between Process Owner, Process Manager and Process Practitioner?

This article was originally published in 2015. With the Introduction of ITIL 4, some of this best practice has changed. See ITIL 4 and the Evolving Role of Roles . Updated Definitions in ITIL 4: Process Owner: In ITIL 4, the concept of 'processes' has expanded into broader 'practices.' Consequently, the Process Owner is now often referred to as the 'Practice Owner.' This individual is accountable for the overall design, performance, integration, and improvement of a specific practice within the organization. They ensure that the practice achieves its intended outcomes and aligns with the organization's objectives. Process Manager: Now commonly known as the 'Practice Manager' in ITIL 4, this role is responsible for the day-to-day management of the practice. The Practice Manager ensures that activities are carried out as intended, manages resources assigned to the practice, and oversees the practitioners performing the work. Process Practit...

Search