Abstract: A method for implementing rules in a complex event processing (CEP) engine is shown. The method includes displaying an interactive diagramming tool to a user on a user interface. The method includes receiving, via the interactive diagramming tool, one or more commands to create a rule. The method includes generating the rule for a complex event processing (CEP) engine based on the received commands. The method includes performing a validation process of the rule and, in response to completion of the validation process, integrating the rule into the CEP engine.

Abstract: A method and technique for data lifecycle management includes storing in a memory from a monitored system one or more metrics. A fault from the monitored system is identified and a first metric from the one or more metrics as being related to the fault is identified. A lifespan is assigned to the first metric, and the first metric is removed from the memory if the lifespan is over.

Abstract: A method and technique for data lifecycle management includes identifying a fault from a monitored system. A time period window is defined associated with the fault based on a time the fault occurred. One or more metrics that are related to the fault that fall within the time period window are identified from the monitored system and stored in a memory. A lifespan is assigned to the one or more metrics based on the fault, and the one or more metrics are removed from the memory when their associated lifespans are over.

Abstract: A method and technique for data lifecycle management includes storing in a memory from a monitored system one or more metrics. A fault from the monitored system is identified and a first metric from the one or more metrics as being related to the fault is identified. A lifespan is assigned to the first metric, and the first metric is removed from the memory if the lifespan is over.

Abstract: Mechanisms for anomaly detection in a network management system are provided. The mechanisms collect metric data from a plurality of network devices and determine metric types for the metric data using metric type reference data. The mechanisms determine and apply properties from the metric type reference data to metrics of the determined metric types. The mechanisms monitor subsequent metric data for anomalies that do not conform to the applied properties.

Abstract: A method and technique for data lifecycle management includes identifying a fault from a monitored system. A time period window associated with the fault is defined based on when the fault occurred. One or more metrics that are related to the fault and that fall within the time period window are identified and stored in a memory. A lifespan condition associated with the fault is identified, and varying levels of lifespans are assigned to the one or more metrics based on a level of relationship between the respective one or more metrics. The one or more metrics are removed from the memory if their associated lifespans are over.

Abstract: A method and technique for data lifecycle management includes identifying a fault from a monitored system. A time period window is defined associated with the fault based on a time the fault occurred. One or more metrics that are related to the fault that fall within the time period window are identified from the monitored system and stored in a memory. A lifespan is assigned to the one or more metrics based on the fault, and the one or more metrics are removed from the memory when their associated lifespans are over.

Abstract: A method and technique for data lifecycle management includes identifying a fault from a monitored system. One or more metrics that are related to the fault are identified and stored in a memory. A lifespan condition associated with the fault is identified, and a lifespan for the one or more metrics is added or changed based on the identified lifespan condition. The one or more metrics are removed from the memory if their associated lifespans are over.

Abstract: Mechanisms for anomaly detection in a network management system are provided. The mechanisms collect metric data from a plurality of network devices and determine metric types for the metric data using metric type reference data. The mechanisms determine and apply properties from the metric type reference data to metrics of the determined metric types. The mechanisms monitor subsequent metric data for anomalies that do not conform to the applied properties.

Abstract: A building management system includes one or more computer-readable storage media having instructions stored thereon that, when executed by one or more processors, cause the one or more processors to receive a threat, the threat comprising a particular threat type, the threat indicating an incident affecting a risk value associated with an asset. The instructions cause the one or more processors to determine, based on the threat and the asset, the risk value at a first point in time, select a decay model based on the particular threat type, and update the risk value at a plurality of points in time after the first point in time with the decay model causing the risk value to decay.

Abstract: Mechanisms for anomaly detection in a network management system are provided. The mechanisms collect metric data from a plurality of network devices and determine metric types for the metric data using metric type reference data. The mechanisms determine and apply properties from the metric type reference data to metrics of the determined metric types. The mechanisms monitor subsequent metric data for anomalies that do not conform to the applied properties.

Abstract: A method and technique for data lifecycle management includes identifying a fault from a monitored system. A time period window associated with the fault is defined based on when the fault occurred. One or more metrics that are related to the fault and that fall within the time period window are identified and stored in a memory. A lifespan condition associated with the fault is identified, and varying levels of lifespans are assigned to the one or more metrics based on a level of relationship between the respective one or more metrics. The one or more metrics are removed from the memory if their associated lifespans are over.

Abstract: Data lifecycle management is performed by managing metrics from a monitored system. A fault is identified from the monitored system. One or more metrics that are directly related to the fault and one or more metrics that are indirectly related to the fault by virtue of being directly or indirectly related to the one or more directly related metrics are identified and stored in a memory. A lifespan condition associated with the fault is identified. A lifespan for each of the directly and indirectly related metrics based on the identified lifespan condition is added or changed. A metric that is critically related to another metric will inherit the same lifespan, and a metric that is related but not critically related to another metric will not inherit the other metric's lifespan. Metrics are removed from the memory if their associated lifespans are over.

Abstract: A method and technique for data lifecycle management includes identifying a fault from a monitored system. One or more metrics that are related to the fault are identified and stored in a memory. A lifespan condition associated with the fault is identified, and a lifespan for the one or more metrics is added or changed based on the identified lifespan condition. The one or more metrics are removed from the memory if their associated lifespans are over.

Abstract: A method, system and computer program product for data lifecycle management is provided. A method for managing metrics from a monitored system comprises: identifying a fault from the monitored system; identifying from the monitored system, one or more metrics are that are directly related to the fault and one or more metrics that are indirectly related to the fault by virtue of being directly or indirectly related to the one or more directly related metrics; identifying a lifespan condition associated with the fault; adding or changing a lifespan for each of the directly and indirectly related metrics based on the identified lifespan condition; and removing metrics from the storage if their associated lifespans are over.

Abstract: Data lifecycle management is performed by managing metrics from a monitored system. A fault is identified from the monitored system. One or more metrics that are directly related to the fault and one or more metrics that are indirectly related to the fault by virtue of being directly or indirectly related to the one or more directly related metrics are identified and stored in a memory. A lifespan condition associated with the fault is identified. A lifespan for each of the directly and indirectly related metrics based on the identified lifespan condition is added or changed. A metric that is critically related to another metric will inherit the same lifespan, and a metric that is related but not critically related to another metric will not inherit the other metric's lifespan. Metrics are removed from the memory if their associated lifespans are over.

Abstract: An apparatus for comparing event data sets. A system and computer program for comparing event data sets comprising: calculating one or more derivatives for each event in a first and second set of events; classifying each event by the calculated derivatives; and evaluating a similarity of the first and second sets of events based on the classifications of the respective events.

Abstract: A method and apparatus for comparing event data sets. A method, system and computer program for comparing event data sets comprising: calculating one or more derivatives for each event in a first and second set of events; classifying each event by the calculated derivatives; and evaluating a similarity of the first and second sets of events based on the classifications of the respective events.

Abstract: Alerting a calling party in a Voice over IP (VoIP) setting that a called party might not be able to hear ring tones. In response to a call arriving on an IP connection, the audible level of ring-tones that are generated by a microphone associated with a VoIP computer application is sampled, and responsive to the audible level of ring-tones being below a minimum threshold, a message is transmitting to the calling party via any available connection that the called party might be unable to hear the ring-tones.

Abstract: Mechanisms for anomaly detection in a network management system are provided. The mechanisms collect metric data from a plurality of network devices and determine metric types for the metric data using metric type reference data. The mechanisms determine and apply properties from the metric type reference data to metrics of the determined metric types. The mechanisms monitor subsequent metric data for anomalies that do not conform to the applied properties.