Service Monitor Data Object

Purpose

The Service Monitor data object defined monitoring policies for CIs; that is, for the Actual Product Instance, or its underlying systems. The purpose is to understand the current status of the running service. The monitoring policies can for example specify:

  • Monitoring of the performance and availability (of the Digital Products and its components and dependencies)

  • Monitoring of user experience

  • Monitoring of security and scans for potential vulnerabilities

  • Monitoring of availability of the actual Digital Product and its components (and dependencies)

  • Monitoring of performance and capacity (e.g., utilization of resources)

The Service Monitor definition is created in the Integrate value stream as part of the release package, and activated from the Fulfillment Orchestration functional component.

Key Attributes

The Service Monitor data object shall have the following key data attributes:

  • Id: unique identifier for the Service Monitor

  • Name: name of the Service Monitor

  • Description: description of the Service Monitor

  • Type: type of the Service Monitor (system, application, network, security, etc.)

  • Measurement Definitions: definitions of the measurements that the Service Monitor is collecting about the monitored entity (i.e., CI)

  • Last Run Time: date/time that the Service Monitor was last run

  • Last Run Status: the success, or not, of the last run of the Service Monitor

Key Data Object Relationships

The Service Monitor data object shall maintain the following relationships:

  • Service Monitor to Log (1:n): enables the traceability from the log entries that are created to the Service Monitor that defined the collection of data

  • Service Monitor to Event (1:n): an event can be created/updated by a Service Monitor.

  • Service Monitor to Actual Product Instance (1:n): the Actual Product Instance is the CI being monitored