Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A storage monitoring system including a storage device, a manager, a plurality of agents, a client which sends a request for component metric information to the manager, and a server which requests the storage device to generate or delete a component and a relay device between the server and the storage device, the storage device comprising: a plurality of types of components, the plurality of types of components including a plurality of components of a first type, the manager comprising: a first processor and a first memory, wherein the first processor stores information representing a first monitoring range of the plurality of components of the first type to be monitored by a first agent out of the plurality of agents in association with information representing the first agent in the first memory and notifies the first agent of the information representing the first monitoring range; stores information representing a second monitoring range of the plurality of components of the first type to be monitored by a second agent out of the plurality of agents in association with information representing the second agent in the first memory and notifies the second agent of the information representing the second monitoring range; calculates a number of the plurality of components of the first type to be contained in the first monitoring range and a number of the plurality of components of the first type to be contained in the second monitoring range, based on a number of the plurality of components of the first type divided by a number of the plurality of agents, thus determining the information representing the first monitoring range and the information representing the second monitoring range so that the number of the plurality of components of the first type to be contained in the first monitoring range and in the second monitoring range will be even within a preset error range; updates information representing an end time of monitoring associated with information representing monitoring ranges already stored in the first memory; stores the information representing the first monitoring range and the information representing the second monitoring range, thus determined, each together with information representing a start time of monitoring, into the first memory; and from information representing a period consisting of a start time and an end time included in a request sent by the client, specifies agents in a group out of the plurality of agents, the agents in the group retaining pieces of component metric information that is requested for the period included in the request, based on information stored in the first memory, and sends a request to the specified agents in the group wherein, in response to the request sent to the agents in the group, the agents in the group send the manager the pieces of the component metric information that is requested, wherein the first processor of the manager receives and assembles the pieces of the component metric information and sends that information to the client, and wherein the first processor of the manager, when the number of the plurality of components of the first type is changed, calculates the number of the plurality of components of the first type to be contained in the first monitoring range and the number of the plurality of components of the first type to be contained in the second monitoring range, based on the changed number of the plurality of components of the first type and the number of the plurality of agents, thus determining the information representing the first monitoring range and the information representing the second monitoring range so that the number of the plurality of components of the first type will be even within a preset error range, the first agent comprising: a second processor and a second memory, wherein the second processor stores the information representing the first monitoring range notified from the manager into the second memory, acquires, from the storage device, first component metric information on components in the first monitoring range out of the plurality of components of the first type, based on the information representing the first monitoring range stored in the second memory, and stores the acquired first component metric information into the second memory, the second agent comprising: a third processor and a third memory, wherein the third processor stores the information representing the second monitoring range notified from the manager into the third memory, acquires, from the storage device, second component metric information on components in the second monitoring range out of the plurality of components of the first type, based on the information representing the second monitoring range stored in the third memory, and stores the acquired second component metric information into the third memory, wherein the server sends a request to generate or delete a component to the relay device, wherein the relay device receives a request to generate or delete a component and sends the request to the storage device and the manager, wherein the storage device receives a request to generate or delete a component and generates or deletes a component, and wherein the first processor of the manager receives request to generate or delete a component.
A storage monitoring system tracks performance metrics of storage device components by distributing monitoring tasks among multiple agents. The system includes a storage device with various components, a manager, multiple agents, a client, a server, and a relay device. The manager assigns monitoring ranges to agents, ensuring balanced workload distribution by calculating component counts per agent based on total components and agent count, allowing for a preset error margin. When a client requests component metric data for a specific time period, the manager identifies agents with relevant data and retrieves it. If the number of components changes, the manager recalculates monitoring ranges to maintain balance. Agents store and provide metric data for their assigned components. The server requests component generation or deletion via the relay device, which forwards the request to both the storage device and manager. The storage device executes the request, while the manager updates monitoring assignments accordingly. This system ensures efficient, scalable monitoring of storage components by dynamically adjusting agent responsibilities based on component changes.
2. The storage monitoring system according to claim 1 , wherein the first processor of the manager, when the number of the plurality of agents increases, calculates the number of the plurality of components of the first type to be contained in the first monitoring range and the number of the plurality of components of the first type to be contained in the second monitoring range, based on the number of the plurality of components of the first type and the increased number of the plurality of agents, thus determining the information representing the first monitoring range and the information representing the second monitoring range so that the number of the plurality of components of the first type will be even within a preset error range.
A storage monitoring system dynamically adjusts monitoring ranges to ensure balanced workload distribution among agents. The system includes a manager with a first processor and multiple agents monitoring storage components. When the number of agents increases, the first processor recalculates the distribution of storage components between a first and second monitoring range. The calculation is based on the total number of storage components and the increased number of agents, ensuring the components are evenly distributed within a preset error range. This adjustment prevents overloading any single agent and maintains efficient monitoring performance. The system dynamically reallocates components to maintain balance as the agent count changes, optimizing resource utilization and system reliability. The manager's processor ensures that the distribution remains consistent, even when the number of agents fluctuates, by recalculating the monitoring ranges accordingly. This approach improves scalability and reduces the risk of monitoring bottlenecks in large-scale storage environments.
3. The storage monitoring system according to claim 1 , wherein the first processor of the manager, when the first agent is deleted, calculates the number of the plurality of components of the first type to be contained in the first monitoring range and the number of the plurality of components of the first type to be contained in the second monitoring range, based on the number of the plurality of components of the first type and the number of the plurality of agents less the first agent, thus determining the information representing the second monitoring range so that the number of the plurality of components of the first type will be even within a preset error range; directs the first agent to relocate the first component metric information stored in the second memory to a third agent out of the plurality of agents; and updates the information representing the first monitoring range stored in the first memory to that information associated with information representing the third agent, and wherein the first agent relocates the first component metric information stored in the second memory to the third agent.
This invention relates to a storage monitoring system designed to efficiently manage and distribute monitoring tasks across multiple agents in a distributed storage environment. The system addresses the challenge of maintaining balanced workload distribution when an agent is removed, ensuring that the remaining agents can continue monitoring storage components without performance degradation or uneven resource utilization. The system includes a manager with a processor and a memory, and multiple agents responsible for monitoring storage components. Each agent collects and stores metric information about assigned storage components. When an agent is deleted, the manager recalculates the distribution of storage components across the remaining agents. The manager determines the number of components of a specific type that should be monitored in each monitoring range, ensuring the distribution remains balanced within a predefined error range. The manager then directs the affected agent to transfer its stored component metric information to another agent, updating the monitoring assignments accordingly. This ensures seamless redistribution of monitoring tasks without disrupting ongoing operations. The system dynamically adjusts monitoring ranges to maintain efficiency and reliability in the storage environment.
4. The storage monitoring system according to claim 1 , wherein the server sends a request to generate a component to the relay device, when generating a virtual machine, and sends a request to delete a component to the relay device, when deleting a virtual machine.
A storage monitoring system for managing virtual machine (VM) components in a networked environment. The system addresses the challenge of efficiently tracking and managing storage resources allocated to VMs, particularly when VMs are created or removed. The system includes a server that communicates with a relay device to dynamically adjust storage components based on VM lifecycle events. When a new VM is generated, the server sends a request to the relay device to create a corresponding storage component, ensuring the VM has the necessary storage resources. Conversely, when a VM is deleted, the server sends a request to the relay device to remove the associated storage component, freeing up storage resources. The relay device acts as an intermediary, facilitating communication between the server and storage systems to execute these requests. This approach ensures that storage resources are allocated and deallocated in sync with VM operations, optimizing storage utilization and preventing resource leaks. The system is particularly useful in cloud computing and virtualized environments where VMs are frequently created and terminated.
5. The storage monitoring system according to claim 4 , wherein the second processor of the first agent measures performance of storing the first component metric information into the second memory, determines that the measured performance has become lower than a preset threshold value, and notifies the manager of that fact.
A storage monitoring system is designed to track and manage the performance of data storage operations in a distributed computing environment. The system addresses the challenge of ensuring efficient and reliable storage of performance metrics, which are critical for system optimization and troubleshooting. The system includes multiple agents, each with processing capabilities, that collect and store performance data from various components of the computing environment. A first agent is responsible for gathering metric information from a first component and storing it in a second memory. A second processor within this agent monitors the performance of this storage operation. If the storage performance degrades below a predefined threshold, the second processor detects this decline and alerts a central manager. The manager can then take corrective actions, such as redistributing storage tasks or initiating maintenance, to maintain system efficiency. This proactive monitoring helps prevent data loss or performance bottlenecks, ensuring smooth operation of the storage infrastructure. The system is particularly useful in large-scale environments where real-time performance tracking is essential for maintaining system health.
6. The storage monitoring system according to claim 5 , wherein the components are volumes and the component metric information is information representing performance of read/write from/to the volumes.
A storage monitoring system tracks performance metrics of storage volumes to optimize data access. The system monitors read and write operations to and from individual storage volumes, collecting performance data such as latency, throughput, and error rates. This information is used to identify bottlenecks, predict failures, and balance workloads across storage resources. The system may also correlate volume performance with other storage system metrics, such as disk utilization or network latency, to provide a comprehensive view of storage health. By analyzing these metrics, administrators can proactively manage storage resources, ensuring efficient data access and minimizing downtime. The system may integrate with existing storage management tools to automate alerts, capacity planning, and performance tuning. This approach helps maintain high availability and reliability in storage systems, particularly in environments with high I/O demands, such as databases or virtualized infrastructures.
7. A monitoring method for a storage monitoring system comprising a storage device, a manager, a plurality of agents, a client which sends a request for component metric information to the manager, and a server which requests the storage device to generate or delete a component and a relay device between the server and the storage device, wherein the manager stores information representing a first monitoring range of a plurality of components of a first type, out of a plurality of types of components contained in the storage device, to be monitored by a first agent out of the plurality of agents in association with information representing the first agent and notifies the first agent of the information representing the first monitoring range; stores information representing a second monitoring range of the plurality of components of the first type to be monitored by a second agent out of the plurality of agents in association with information representing the second agent and notifies the second agent of the information representing the second monitoring range; calculates a number of the plurality of components of the first type to be contained in the first monitoring range and a number of the plurality of components of the first type to be contained in the second monitoring range, based on a number of the plurality of components of the first type divided by a number of the plurality of agents, thus determining the information representing the first monitoring range and the information representing the second monitoring range so that the number of the plurality of components of the first type to be contained in the first monitoring range and in the second monitoring range will be even within a preset error range; updates information representing an end time of monitoring associated with information representing monitoring ranges already stored in the first memory; stores the information representing the first monitoring range and the information representing the second monitoring range, thus determined, each together with information representing a start time of monitoring, into the first memory; and from information representing a period consisting of a start time and an end time included in a request sent by the client, specifies agents in a group out of the plurality of agents, the agents in the group retaining pieces of component metric information that is requested for the period included in the request, based on information stored in the first memory, and sends a request to the specified agents in the group, wherein, in response to the request sent to the agents in the group, the agents in the group send the manager the pieces of the component metric information that is requested, wherein the first processor of the manager receives and assembles the pieces of the component metric information and sends that information to the client, wherein the first processor of the manager, when the number of the plurality of components of the first type is changed, calculates the number of the plurality of components of the first type to be contained in the first monitoring range and the number of the plurality of components of the first type to be contained in the second monitoring range, based on the changed number of the plurality of components of the first type and the number of the plurality of agents, thus determining the information representing the first monitoring range and the information representing the second monitoring range so that the number of the plurality of components of the first type will be even within a preset error range, wherein the server sends a request to generate or delete a component to the relay device, wherein the relay device receives a request to generate or delete a component and sends the request to the storage device and the manager, wherein the storage device receives a request to generate or delete a component and generates or deletes a component, and wherein the first processor of the manager receives request to generate or delete a component, wherein the first agent stores the information representing the first monitoring range notified from the manager, acquires, from the storage device, and stores first component metric information on components in the first monitoring range out of the plurality of components of the first type, based on the stored information representing the first monitoring range, and wherein the second agent stores the information representing the second monitoring range notified from the manager, acquires, from the storage device, and stores second component metric information on components in the second monitoring range out of the plurality of components of the first type, based on the stored information representing the second monitoring range.
A storage monitoring system tracks performance metrics of components within a storage device. The system includes a manager, multiple agents, a client, a server, a relay device, and the storage device itself. The manager assigns monitoring responsibilities to agents by dividing components of a specific type into distinct ranges. Each agent is notified of its assigned range and collects metric data for components within that range. The manager calculates these ranges by dividing the total number of components by the number of agents, ensuring an even distribution within a preset error margin. When the number of components changes, the manager recalculates the ranges accordingly. The system also handles component generation or deletion requests, which are relayed to both the storage device and the manager. Agents store their assigned ranges and periodically collect metric data from the storage device. When a client requests metric information for a specific time period, the manager identifies which agents have relevant data and retrieves it. The manager then assembles and sends the collected data to the client. This approach ensures efficient, distributed monitoring of storage components while maintaining balanced workloads among agents.
Unknown
March 10, 2020
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.