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

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People: Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products: These are the technology managem

What Is A Service Offering?

The ITIL4 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 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. Note: Goods may not always be provided for every Service Offe

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

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the

Search