Note: This scenario was originally submitted to the Performance Monitoring workgroup. It is moved here since it is more pertinent to the goals of the Reconciliation workgroup.

Pre-conditions

1. Monitoring solutions expose the list of resources they are monitoring
2. Discovery solutions expose the list of resources they have discovered
3. A monitoring coverage report tool queries across the two to see where there are resources that have been discovered but are not monitored.

Steps

The following defines 3 fundamental actions/events that would be visible to clients:

1. Reporting Actions
   1. A user can leverage a product’s reporting capability, via its GUI or command-line, to generate a list of computer systems that are known to be enabled or disabled for monitoring.
2. Service Instance Action
   1. This is the scenario where there is context whereby a user will perform an action in order to gain insight into whether the members (i.e. Computer Systems) of a collection are configured for monitoring or not. An example of a user action would be to request to generate the list of computer systems of a Service Instance (Business Server or Business Application) definition that are known to not have any monitoring configured or not.
3. Singleton Action
   1. This is the scenario where a user will perform an action in order to gain insight into whether a specifically chosen computer system, via a product GUI or command-line, has been configured for monitoring or not.
   2. If endpoint has been configured for monitoring, monitoring provider will provide a UI preview of monitor configuration

Variations on the Scenario

1. Types of Monitoring
   In the above information, it is not explicitly mentioned what endpoint monitoring means. Additionally, only a ComputerSystem resource is mentioned. So what is not accounted for that will add variations is the types of Resources and types of monitoring that need to be considered. The base case scenario could simply be Operating System Agent monitoring of a ComputerSystem. Whereas, a variation could be Database Agent (SoftwareServer) monitoring of database instances.
2. Additional Insights
   It should be pointed out that although this scenario is focused on determining monitoring coverage, this is really just one type of environment insight opportunity. By the nature of a proposed implementation which has not been mentioned and taking into consideration of new domains, the following are additional example of variations on this coverage scenario:
   1. Provide a standardized method of determining if an endpoint has been discovered
   2. Provide a standardized method of determining if an endpoint is a managed asset
   3. Provide a standardized method of determining if an endpoint is <place your relevant OSLC Domain here.>