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: Managing privileged system access may be performed by a risk management system controlling user access privilege to production systems. One example method of operation may provide at least one of detecting an insecure user action at a user device, reducing an access privilege of a user profile associated with the user device to one or more privileged production servers, providing the user device with an application based on the insecure user action, determining that an outcome associated with the application has been achieved, and re-instating the access privilege of the user profile.

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 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: Managing privileged system access may be performed by a risk management system controlling user access privilege to production systems. One example method of operation may provide at least one of detecting an insecure user action at a user device, reducing an access privilege of a user profile associated with the user device to one or more privileged production servers, providing the user device with an application based on the insecure user action, determining that an outcome associated with the application has been achieved, and re-instating the access privilege of the user profile.

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: Managing privileged system access may be performed by a risk management system controlling user access privilege to production systems. One example method of operation may provide at least one of detecting an insecure user action at a user device, reducing an access privilege of a user profile associated with the user device to one or more privileged production servers, providing the user device with an application based on the insecure user action, determining that an outcome associated with the application has been achieved, and re-instating the access privilege of the user profile.

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 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: Managing privileged system access may be performed by a risk management system controlling user access privilege to production systems. One example method of operation may provide at least one of detecting an insecure user action at a user device, reducing an access privilege of a user profile associated with the user device to one or more privileged production servers, providing the user device with an application based on the insecure user action, determining that an outcome associated with the application has been achieved, and re-instating the access privilege of the user profile.

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: Enabling question object owner and status tracking can include establishing one or more question objects within an email message from a sender to a set of recipients. Question objects can be maintained on the server with unique identifiers. The question object(s) can have multiple sub question objects. Each question object or sub question object can be delegated a question owner, which can be maintained in the server. Recipients (answer providers) can take responsibility for answering various parts of the question object or the whole question object or for tackling a task associated with the question object. The server can associate and record question providers with their various responsibilities or answers. The server can then dynamically update a portion or all of the originally sent email message in the question owner's email account and the recipients' (answer providers') email accounts to show the answer and the answer provider.

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: Enabling question object owner and status tracking can include establishing one or more question objects within an email message from a sender to a set of recipients. Question objects can be maintained on the server with unique identifiers. The question object(s) can have multiple sub question objects. Each question object or sub question object can be delegated a question owner, which can be maintained in the server. Recipients (answer providers) can take responsibility for answering various parts of the question object or the whole question object or for tackling a task associated with the question object. The server can associate and record question providers with their various responsibilities or answers. The server can then dynamically update a portion or all of the originally sent email message in the question owner's email account and the recipients' (answer providers') email accounts to show the answer and the answer provider.