Method, device and computer program product for monitoring access request
Techniques for monitoring an access request are described. For instance, a method comprises: obtaining a request parameter indicating a target storage space to which the access request is directed; determining a target address range of the target storage space based on the request parameter; determining, in a set of kernel logs, a target kernel log associated with the access request based on the target address range, the set of kernel logs recording operations that occur in a kernel of an operating system; and determining information of an operation of the access request based on the kernel log, the operation corresponding to the target kernel log.
1. A method, comprising:
obtaining, by a system comprising a processor, a request parameter indicating a target storage space to which an access request is directed;
determining a target address range of the target storage space based on the request parameter;
determining, in a set of kernel logs, a target kernel log associated with the access request based on the target address range, the set of kernel logs recording operations that occur in a kernel of an operating system;
determining information of an operation of the access request based on the target kernel log, the operation corresponding to the target kernel log, wherein the information comprises a timestamp of the operation;
determining, based on the timestamp, whether an abnormity has occurred in the operation; and
in response to determining the abnormity has occurred, setting, based on a type of the abnormity of the operation, at least one policy to reduce a performance degradation caused by an overload of a node.
2. The method according to claim 1 , wherein the obtaining the request parameter comprises:
obtaining a file identifier of a file to which the access request is directed, an offset of the target storage space in the file, and a size of the target storage space.
3. The method according to claim 2 , wherein the determining the target address range comprises:
obtaining a file address range corresponding to the file based on the file identifier; and
determining, from the file address range, the target address range based on the offset and the size.
4. The method according to claim 1 , wherein the determining the target kernel log comprises:
obtaining a first address range associated with a first kernel log of the set of kernel logs; and
in response to the first address range being within the target address range, determining the first kernel log as the target kernel log.
5. The method according to claim 1 , wherein the information is of a first type of information, and the method further comprises:
determining a second type of information of the operation of the access request based on the target kernel log, the operation corresponding to the target kernel log, and wherein the second type of information includes at least one of the following: a status of the operation, and content of the operation.
6. The method according to claim 1 , further comprising:
in response to determining the abnormity occurred, providing an indication for the occurrence of the abnormity in the operation.
7. The method according to claim 1 , further comprising:
providing a visualized display of the timestamp.
8. A device, comprising:
at least one processing unit;
at least one memory coupled to the at least one processing unit and having instructions stored therein, the instructions, when executed by the at least one processing unit, causing the device to perform acts comprising:
obtaining a request parameter indicating a target storage space to which the access request is directed;
determining a target address range of the target storage space based on the request parameter;
determining, in a set of kernel logs, a target kernel log associated with the access request based on the target address range, the set of kernel logs recording operations that occur in a kernel of an operating system;
determining information of an operation of the access request based on the target kernel log, the operation corresponding to the target kernel log, wherein the information comprises a timestamp of the operation;
determining, based on the timestamp, whether an abnormity occurred in the operation; and
in response to determining the abnormity occurred, setting at least one policy to reduce a performance degradation caused by an overload of a node.
9. The device according to claim 8 , wherein the obtaining the request parameter comprises:
obtaining a file identifier of a file to which the access request is directed, an offset of the target storage space in the file, and a size of the target storage space.
10. The device according to claim 9 , wherein the determining the target address range comprises:
obtaining a file address range corresponding to the file based on the file identifier; and
determining, from the file address range, the target address range based on the offset and the size.
11. The device according to claim 8 , wherein the determining the target kernel log comprises:
obtaining a first address range associated with a first kernel log of the set of kernel logs; and
in response to the first address range being within the target address range, determining the first kernel log as the target kernel log.
12. The device according to claim 8 , wherein the information is of a first type of information, and the acts further comprise:
determining a second type of information of the operation of the access request based on the target kernel log, the operation corresponding to the target kernel log, and wherein the second type of information includes at least one of the following: a status of the operation, the timestamp of the operation, and content of the operation.
13. The device according to claim 8 , the acts further comprising:
in response to determining the abnormity occurred, performing, based on a type of the abnormity of the operation, at least one predetermined action corresponding to the type.
14. The device according to claim 8 , the acts further comprising:
providing a visualized display of the timestamp.
15. A computer program product being stored on a non-transitory computer storage medium and comprising machine-executable instructions which, when executed in a device, cause the device to perform operations, comprising:
obtaining a request parameter indicating a target storage space to which the access request is directed;
determining a target address range of the target storage space based on the request parameter;
determining, in a set of kernel logs, a target kernel log associated with the access request based on the target address range, the set of kernel logs recording operations that occur in a kernel of an operating system;
determining information of an operation of the access request based on the target kernel log, the operation corresponding to the target kernel log, wherein the information comprises a timestamp of the operation; and
in response to determining, based on the timestamp, an occurrence of an abnormity in the operation,
providing an indication for the occurrence of the abnormity in the operation, and
setting, based on a type of the abnormity of the operation, at least one policy to avoid a performance degradation caused by an overload of a node.
16. The computer program product according to claim 15 , wherein the obtaining the request parameter comprises:
obtaining a file identifier of a file to which the access request is directed, an offset of the target storage space in the file, and a size of the target storage space, and
wherein the determining the target address range comprises:
obtaining a file address range corresponding to the file based on the file identifier; and
determining, from the file address range, the target address range based on the offset and the size.
17. The computer program product according to claim 15 , wherein the determining the target kernel log comprises:
obtaining a first address range associated with a first kernel log of the set of kernel logs; and
in response to the first address range being within the target address range, determining the first kernel log as the target kernel log.
18. The computer program product according to claim 15 , wherein the performing operations comprises:
based on the abnormity being with respect to a block device layer, detecting whether a bad driver appears.
19. The computer program product according to claim 15 , wherein the operations further comprise:
sending the indication for the occurrence of the abnormity in the operation to a user device via a user interaction module.
20. The computer program product according to claim 15 , wherein the providing of the indication comprises providing a visual display of log information determined from the target kernel log.