Notification management for monitoring system

1. A method to manage notifications related to a condition definition, comprising:

receiving a condition definition from a first user;

receiving a first instruction from the first user to provide the first user and the second user with access to the condition definition;

receiving a second instruction from the first user to subscribe the first user to the condition definition;

receiving a third instruction from the second user to unsubscribe the second user from the condition; and

receiving an instruction from the first user to enable logging of an event summary record that characterizes a period between a detection of an active state of the condition and a detection of an inactive state of the condition.

2. A method according to claim 1 , further comprising:

detecting a change in the state of the condition definition; and

determining that the first user is subscribed to the condition definition; and

notifying the first user of the state change.

3. A method according to claim 2 , wherein notifying the first user of the state change comprises:

determining a notification routing associated with the first user; and

notifying the first user of the state change in accordance with the notification routing.

4. A method according to claim 1 , wherein receiving the first instruction from the first user comprises receiving a fourth instruction to provide a third user with access to the condition definition, the method further comprising:

receiving a fifth instruction from the third user to associate a notification routing with the third user.

5. A method according to claim 1 , wherein the event summary record includes a start time and an end time.

6. A medium storing processor-executable process steps to manage notifications related to a condition definition, the process steps comprising:

a step to receive a condition definition from a first user;

a step to receive a first instruction from the first user to provide the first user and a second user with access to the condition definition;

a step to receive a second instruction from the first user to subscribe the first user to the condition definition;

a step to receive a third instruction from the second user to unsubscribe the second user from the condition definition; and

a step to receive an instruction from the first user to enable logging of an event summary record that characterizes a period between a detection of an active state of the condition and a detection of an inactive state of the condition.

7. A medium according to claim 6 , the process steps further comprising:

a step to detect a change in the state of the condition definition; and

a step to determine that the first user is subscribed to the condition definition; and

a step to notify the first user of the state change.

8. A medium according to claim 7 , wherein the step to notify the first user of the state change comprises:

a step to determine a notification routing associated with the first user; and

a step to notify the first user of the state change in accordance with the notification routing.

9. A medium according to claim 6 , wherein the step to receive the first instruction from the first user comprises a step to receive a fourth instruction to provide a-third user with access to the condition definition, and the process steps further comprising:

a step to receive a fifth instruction from the third user to associate a notification routing with the third user.

10. An apparatus to manage notifications related to a condition definition, the apparatus comprising:

a memory storing processor-executable process steps; and

a processor in communication with the memory and operative in conjunction with the stored process steps to:

receive a condition definition from a first user;

receive a first instruction from the first user to provide the first user and a second user with access to the condition definition;

receive a second instruction from the first user to subscribe the first user to the condition definition;

receive a third instruction from the second user to unsubscribe the second user from the condition definition; and

receive an instruction from the first user to enable logging of an event summary record that characterizes a period between a detection of an active state of the condition and a detection of an inactive state of the condition.

11. An apparatus according to claim 10 , the processor further operative in conjunction with the stored process steps to:

detect a change in the state of the condition definition; and

determine that the first user is subscribed to the condition definition; and

notify the first user of the state change.

12. An apparatus according to claim 11 , wherein notification of the first user of the state change comprises:

determination of a notification routing associated with the first user; and

notification of the first user of the state change in accordance with the notification routing.

13. An apparatus according to claim 10 , wherein reception of the first instruction from the first user comprises reception of a fourth instruction to provide a third user with access to the condition definition, and the processor further operative in conjunction with the stored process steps to:

receive a fifth instruction from the third user to associate a notification routing with the third user.

14. A medium storing processor—executable process steps to provide:

an event detector to subscribe to solution members of a condition definition, to receive changes to the solution members, and to evaluate a state of the condition definition;

a subscription manager to determine users associated with the condition definition;

a notification manager to identify a notification routing for each of the determined users; and

an excursion logger to log an event summary record that characterizes a period between a detection of an active state of the condition and a detection of an inactive state of the condition.

15. A medium according to claim 14 , the process steps to provide:

a notification handler to route a notification to each of the determined users based on the identified notification routing.

16. A medium according to claim 14 , wherein the event detector is to receive a subscription to the condition definition from the subscription manager, and to notify the subscription manager of a change in the state of the condition definition, and

wherein the subscription manager is to identify users associated with the condition definition in response to the change in the state of the condition definition.

17. A medium according to claim 14 , the process steps to provide:

an alert server to receive a plurality of condition definitions, a plurality of subscriptions to the condition definitions, and a plurality of notification routings associated with the plurality of subscriptions from a user, and to pass the plurality of condition definitions, plurality of subscriptions to the condition definitions, and plurality of notification routings associated with the plurality of subscriptions to the subscription manager.

18. A medium according to claim 17 , wherein the alert server is to subscribe to the solution members, to receive the changes to the solution members, and to pass the changes to the event detector.

19. A medium according to claim 17 , wherein the subscription manager is to store the plurality of condition definitions, plurality of subscriptions to the condition definitions, and plurality of notification routings associated with the plurality of subscriptions in a memory.

20. A medium according to claim 14 ,

wherein the excursion logger is to receive an indication of the change in the state of the condition definition from the event detector, and to log the change of state in a memory.