Method for monitoring and managing a client device in a distributed autonomic computing environment

• US 7,788,534 B2
• Filed: 12/11/2007
• Issued: 08/31/2010
• Est. Priority Date: 12/11/2007
• Status: Expired due to Fees

• Current Assignee: LinkedIn Corporation (Microsoft Corporation)
• Original Assignee: International Business Machines Corporation
• Inventors: Suzuki, Yasuhiro, Akiyama, Kazuhito, Tsumura, Tadashi, Nishimura, Yasutaka
• Primary Examiner(s): Beausoliel; Robert
• Assistant Examiner(s): Lottich; Joshua P
• Application Number:
  US11/954,061
• Publication Number:
  US 20090150716A1
• Time in Patent Office: 994 Days
• Field of Search: 714/25, 714/26, 714/27, 714/37, 714/48
• US Class Current: 714/26
• CPC Class Codes: G06F 11/0736 in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function testing or monitoring of automated control systems G05B23/02
• CPC Class Codes: G06F 11/0748 in a remote unit communicating with a single-box computer node experiencing an error/fault remote testing G06F11/2294
• CPC Class Codes: G06F 11/079 Root cause analysis, i.e. error or fault diagnosis in a hardware test environment G06F11/22; in a software test environment G06F11/36
• CPC Class Codes: G06F 11/0793 Remedial or corrective actions recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40

Abstract

A stale of a managed client device in a distributed autonomic computing environment is attached to an event occurring on the managed client device. The event is sent, with the attached state of the managed client device, to a server. The state of the managed client device is saved at the server. The event is analyzed for identifying a problem at the client device. An action for solving the problem is generated based on a state of the managed client device at the time the event is analyzed. An execution condition is dynamically generated based on the saved state of the managed client device. The execution condition is added to the action to be executed and sent to the managed client device. At the managed client device, a determination is made whether to execute the action based on the execution condition and a current state of the managed client device.

Claims

1. A method for monitoring and managing a client device in a distributed autonomic computing environment, comprising:

monitoring a state of a managed client device in the distributed autonomic computing environment;

attaching the state of the managed client device to an event occurring on the managed client device;

sending the event, with the attached state of the managed client device, to a server in the distributed autonomic computing environment;

saving the state of the managed client device at the server;

analyzing the event and identifying a problem occurring at the client device;

generating an action to be performed by the managed client device for solving the problem, wherein the action is generated based on a state of the managed client device at the time the event is analyzed;

dynamically generating an execution condition for the action to be performed by the managed client device based on the saved state of the managed client device;

adding the execution condition to the action to be executed;

sending the execution condition with the action to be performed from the server to the managed client device; and

determining, at the managed client device, whether to execute the action based on the execution condition and a current slate of the managed client device.

2. The method of claim 1, wherein the step of determining includes:

detecting a difference between the state of the managed client device at the time the server analyzes the event and the current state of the managed client device based on the execution condition; and

determining whether the action is needed based on the detected difference.

3. The method of claim 1, wherein the step of determining includes deciding to execute the action, execute an alternative action, re-execute an action, stop execution of an action, or notify the server of an event based on the execution condition and the current state of the managed client device.

4. The method of claim 1, wherein the state of the managed client device includes at least one of CPU usage, a parameter unique to the managed client device, and a set item.