CN116405509B - Distributed monitoring method, computer equipment and storage medium thereof - Google Patents
Distributed monitoring method, computer equipment and storage medium thereof Download PDFInfo
- Publication number
- CN116405509B CN116405509B CN202310679824.5A CN202310679824A CN116405509B CN 116405509 B CN116405509 B CN 116405509B CN 202310679824 A CN202310679824 A CN 202310679824A CN 116405509 B CN116405509 B CN 116405509B
- Authority
- CN
- China
- Prior art keywords
- container
- monitoring
- instance
- target
- lock
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000012544 monitoring process Methods 0.000 title claims abstract description 198
- 238000000034 method Methods 0.000 title claims abstract description 40
- 230000002159 abnormal effect Effects 0.000 claims description 46
- 238000004590 computer program Methods 0.000 claims description 11
- 230000001174 ascending effect Effects 0.000 claims description 7
- 238000004364 calculation method Methods 0.000 abstract description 7
- 238000012216 screening Methods 0.000 description 15
- 238000012545 processing Methods 0.000 description 10
- 238000004891 communication Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 6
- 230000008859 change Effects 0.000 description 4
- 238000012790 confirmation Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 230000004044 response Effects 0.000 description 4
- 238000012797 qualification Methods 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 2
- 230000002860 competitive effect Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000003062 neural network model Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000010200 validation analysis Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000036961 partial effect Effects 0.000 description 1
- 230000001737 promoting effect Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000035945 sensitivity Effects 0.000 description 1
- 230000026676 system process Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/10015—Access to distributed or replicated servers, e.g. using brokers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/62—Establishing a time schedule for servicing the requests
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a distributed monitoring method, a computer device and a storage medium thereof, comprising a relay processor, wherein the relay processor is used for: acquiring first lock fetching requests sent by a plurality of instance containers; determining, based on the first lock fetch request, any one of the plurality of instance containers as a first target instance container, and determining instance containers other than the first target instance container as a plurality of listening instance containers; determining that the first target instance container successfully acquired a distributed lock; and configuring a preset monitoring environment for the first target instance container so that the first target instance container monitors the target data. The monitoring task executed by the first target instance container in the cloud computing architecture has uniqueness, so that the calculation power loss caused by the fact that a plurality of instance containers execute the same monitoring task is avoided, and the monitoring efficiency is optimized.
Description
Technical Field
The present application relates to the field of cloud computing, and in particular, to a distributed monitoring method, a computer device, and a storage medium.
Background
Cloud monitoring refers to fully referencing the technical ideas of cloud computing, cloud storage, data centers, business intelligence and the like in the development process of the IT industry, optimally designing and developing data center architecture and technology of multimedia services such as monitoring, and promoting the overall architecture to have the characteristics of robustness, expandability, operability and standardization through security large networking practice, so that video data are more and more centralized, and informatization of the data are further realized.
In the prior art, cloud monitoring is often customized according to the customization requirement of a user, specifically, according to the monitoring index selected by the user, a corresponding monitoring program is added in a cloud data link, so that the monitoring requirement of the user is realized.
The inventor of the application discovers in the research that in the field of cloud monitoring, the monitoring demands of a plurality of users are always the same, and because of lack of unified management, a plurality of monitoring programs repeatedly execute the same monitoring tasks, so that the cloud computing resources are seriously wasted.
Disclosure of Invention
In order to solve the technical problems, the embodiment of the application provides a distributed monitoring method, a device, equipment and a storage medium capable of carrying out non-repeated monitoring on data.
In order to achieve the above object, the present application provides a distributed listening method, including a relay processor, where the relay processor is configured to:
acquiring first lock fetching requests sent by a plurality of instance containers;
determining, based on the first lock fetch request, any one of the plurality of instance containers as a first target instance container, and determining instance containers other than the first target instance container as a plurality of listening instance containers;
determining that the first target instance container successfully acquired a distributed lock;
and configuring a preset monitoring environment for the first target instance container so that the first target instance container monitors the target data.
Optionally, the determining, based on the first lock fetching request, any one of the plurality of instance containers as the first target instance container includes:
respectively acquiring time stamps of the received first lock fetching requests;
the time stamps are arranged in an ascending order to generate a time sequence;
and determining an instance container corresponding to the timestamp positioned at the first bit in the time sequence as the first target instance container.
Optionally, after the configuring the preset listening environment to the first target instance container, the method includes:
After the state information of the first target instance container is updated, receiving second lock fetching requests sent by the plurality of monitoring instance containers;
and determining any one of the plurality of monitoring instance containers as a second target instance container according to the second lock fetching request so as to enable the second target instance container to replace the first target instance container.
Optionally, the first target instance container is further configured to:
writing a state container into a preset distributed key value database;
and in the data monitoring process, the state information is sent to the state container, so that the state container updates the state data according to the state information.
Optionally, the status container is further configured to:
acquiring registration requests of the plurality of monitoring instance containers;
and configuring the monitoring authorities of the plurality of monitoring instances according to the registration request.
Optionally, the plurality of listening instances are further for:
sending the registration request to the status container;
monitoring state information in the state container according to the monitoring authority configured by the registration request;
and when the state information is monitored to be updated, sending a preset second lock taking request.
Optionally, the first target instance container is further configured to:
collecting monitoring information of the target data, wherein the abnormal index is abnormal data which cannot be classified in the existing database;
dividing the monitoring information into hot data and cold data based on a preset classification strategy;
and locally storing the hot data, and sending the cold data to a preset remote storage space for storage.
Optionally, the first target instance container is further configured to:
acquiring abnormal indexes of the target data;
according to the abnormal index, a depth monitoring strategy for performing depth monitoring on the abnormal index is read;
unlocking the distributed lock according to the depth monitoring strategy, and sending a depth monitoring lock request;
and carrying out deep monitoring on the abnormal data represented by the abnormal index according to the locking result of the deep monitoring locking request.
To achieve the above object, the present application also provides a computer apparatus including a memory and a processor; the memory is used for storing a computer program; the processor is configured to execute the computer program and implement any one of the distributed monitoring methods provided by the embodiments of the present application when the computer program is executed.
To achieve the above object, the present application further provides a computer readable storage medium storing a computer program, where the computer program when executed by a processor causes the processor to implement the distributed listening method according to any one of the embodiments of the present application.
The beneficial effects of the application are: and determining a plurality of instance containers with the same monitoring task in the cloud link, wherein the plurality of instance containers are distributed and configured into the cloud computing architecture, and the plurality of instance containers all send a first lock-taking request to conduct competing for lock. Screening a first target instance container from a plurality of instance containers according to a first lock taking request, further determining that the first target instance container has the qualification of monitoring data, determining that the first target instance container successfully acquires the distributed lock, and stopping executing the data monitoring task by other instance containers after the first target instance container acquires the distributed lock, so as to turn into a monitoring instance container. Therefore, the monitoring task executed by the first target instance container in the cloud computing architecture has uniqueness, so that the calculation power loss caused by the fact that a plurality of instance containers execute the same monitoring task is avoided, and the monitoring efficiency is optimized.
Drawings
The foregoing and/or additional aspects and advantages of the application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings, in which:
FIG. 1 is a schematic diagram of a basic flow of a distributed monitoring method according to an embodiment of the present application;
fig. 2 is a basic structural block diagram of a computer device according to an embodiment of the present application.
Detailed Description
Embodiments of the present application are described in detail below, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to like or similar elements or elements having like or similar functions throughout. The embodiments described below by referring to the drawings are illustrative only and are not to be construed as limiting the application.
As used herein, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless expressly stated otherwise, as understood by those skilled in the art. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It will be understood by those skilled in the art that all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs unless defined otherwise. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the prior art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
As will be appreciated by those skilled in the art, a "terminal" as used herein includes both devices of a wireless signal receiver that have only wireless signal receivers without transmitting capabilities and devices of receiving and transmitting hardware that have devices capable of performing two-way communications over a two-way communications link. Such a device may include: a cellular or other communication device having a single-line display or a multi-line display or a cellular or other communication device without a multi-line display; a PCS (Personal Communications Service, personal communication system) that may combine voice, data processing, facsimile and/or data communication capabilities; a PDA (Personal Digital Assistant ) that can include a radio frequency receiver, pager, internet/intranet access, web browser, notepad, calendar and/or GPS (Global Positioning System ) receiver; a conventional laptop and/or palmtop computer or other appliance that has and/or includes a radio frequency receiver. As used herein, a "terminal" may be portable, transportable, installed in a vehicle (aeronautical, maritime, and/or land-based), or adapted and/or configured to operate locally and/or in a distributed fashion, to operate at any other location(s) on earth and/or in space. The "terminal" used herein may also be a communication terminal, a network access terminal, a music/video playing terminal, for example, a PDA, a MID (Mobile Internet Device ) and/or a mobile phone with music/video playing function, and may also be a smart tv, a set-top box, etc.
The application refers to hardware such as a server, a client, a service node, and the like, which essentially is an electronic device with personal computer and other functions, and is a hardware device with necessary components disclosed by von neumann principles such as a central processing unit (including an arithmetic unit and a controller), a memory, an input device, an output device, and the like, wherein a computer program is stored in the memory, and the central processing unit calls the program stored in the memory to run, executes instructions in the program, and interacts with the input and output devices, thereby completing specific functions.
It should be noted that the concept of the present application, called "server", is equally applicable to the case of server clusters. The servers should be logically partitioned, physically separate from each other but interface-callable, or integrated into a physical computer or group of computers, according to network deployment principles understood by those skilled in the art. Those skilled in the art will appreciate this variation and should not be construed as limiting the implementation of the network deployment approach of the present application.
One or more technical features of the present application, unless specified in the clear, may be deployed either on a server for implementation and the client remotely invokes an online service interface provided by the acquisition server for implementation of the access, or may be deployed and run directly on the client for implementation of the access.
The neural network model cited or possibly cited in the application can be deployed on a remote server and can be used for implementing remote call on a client, or can be deployed on a client with sufficient equipment capability for direct call, unless specified by plaintext, and in some embodiments, when the neural network model runs on the client, the corresponding intelligence can be obtained through migration learning so as to reduce the requirement on the running resources of the hardware of the client and avoid excessively occupying the running resources of the hardware of the client.
The various data related to the present application, unless specified in the plain text, may be stored either remotely in a server or in a local terminal device, as long as it is suitable for being invoked by the technical solution of the present application.
Those skilled in the art will appreciate that: although the various methods of the present application are described based on the same concepts so as to be common to each other, the methods may be performed independently of each other unless specifically indicated otherwise. Similarly, for the various embodiments disclosed herein, all concepts described herein are presented based on the same general inventive concept, and thus, concepts described herein with respect to the same general inventive concept, and concepts that are merely convenient and appropriately modified, although different, should be interpreted as equivalents.
The various embodiments of the present application to be disclosed herein, unless the plain text indicates a mutually exclusive relationship with each other, the technical features related to the various embodiments may be cross-combined to flexibly construct a new embodiment as long as such combination does not depart from the inventive spirit of the present application and can satisfy the needs in the art or solve the deficiencies in the prior art. This variant will be known to the person skilled in the art.
Referring to fig. 1, fig. 1 is a basic flow chart of a distributed monitoring method according to the present embodiment.
As shown in fig. 1, the distributed listening method includes:
s1100, acquiring a first lock acquisition request sent by a plurality of instance containers;
in this embodiment, an instance container for performing data monitoring is provided in the cloud computing architecture, where the instance container is distributed on each computing node in the cloud computing architecture in a distributed manner. When there is one and only one data monitoring mode in the cloud computing architecture, all the instance containers used for monitoring in the cloud computing are multiple instance containers referred to in this embodiment. When the cloud computing architecture has multiple data monitoring modes or can perform custom setting of the monitoring modes, all instance containers with the same monitoring mode in the cloud computing architecture are defined as multiple instance containers in this embodiment.
The execution entities of S1100-S1400 in this embodiment can be relay processors. Relay processors include (without limitation): the system comprises a cloud computing data center, a central server, a monitoring control node for monitoring management or a management container generated by lifting an instance container in a cloud computing framework. The execution subjects of S1100-S1400 are defined as relay processors.
The plurality of instance containers respectively send a first lock fetching request to the relay processor, wherein the first lock fetching request is used for requesting to acquire the set distributed lock.
S1200, determining any one of the plurality of instance containers as a first target instance container based on the first lock fetching request, and determining instance containers other than the first target instance container as a plurality of monitoring instance containers;
and the relay processor receives a first lock fetching request sent by the plurality of instance containers, and screens the plurality of instance containers according to the first lock fetching request to obtain a first target instance container.
The screening method for screening the first target instance container comprises the following steps: after receiving each first lock taking request, the relay processor records a time node for receiving each first lock taking request, and generates a time stamp corresponding to each first lock taking request according to the time node. The relay processor reads the time stamp of each first lock request when the first target instance container screening is performed. After the time stamp corresponding to each first lock taking request is obtained, the time stamps are arranged in ascending order according to the time node recorded in each time stamp, and the ascending order results are as follows: and arranging the timestamp with the earliest time in the timestamps in the first bit, and sequentially arranging the timestamps with the later and later acquisition time in sequence, wherein a list generated by arranging is a time sequence. After the time sequence is generated, determining an instance container corresponding to the timestamp positioned at the first position in the time sequence as a first target instance container, namely determining the instance container corresponding to the first lock taking request received by the relay processor as the first target instance container.
In some embodiments, a screening method for screening a first target instance container comprises: the relay processor is configured to: and only one first lock taking request is accepted, and after any one first lock taking request is received by the relay processor, confirmation information of successful access is sent to the corresponding instance container, and the instance container is determined to be the first target instance container. And after the other instance containers do not receive feedback information of successful access, the other instance containers are automatically confirmed to be monitoring instance containers.
In some embodiments, the screening method of screening the first target instance container can further be: screening was performed according to the load parameters of the example containers. Specifically, the first lock-fetching request sent by each instance container includes a load parameter corresponding to each instance container. Wherein the load parameters include (without limitation): at least one of parameters such as CPU usage, CPU load, memory usage, disk I/O, network traffic, system process number, etc. The instance container with the lowest load in the screening load parameters and the highest available load is the first target instance container. In some embodiments, for the case that the load types required by different monitoring tasks are different, an accessory weight weighting formula is correspondingly set for each monitoring mode or monitoring task, and the load types and the weights corresponding to the load types corresponding to the different monitoring tasks or monitoring modes are recorded in the weight weighting formula. And carrying out weighted calculation on the available load in the first lock taking requests according to the weight weights to obtain comprehensive load indexes corresponding to each first lock taking request, and selecting the comprehensive load index with the largest index value in the comprehensive load indexes as a first target instance container. The first target instance container is screened through the load parameters, so that the optimal processing capacity of the first target instance container can be ensured, and the monitoring efficiency is optimized.
After the screening to obtain the first target instance container, the remaining instance containers are defined as listening instance containers. The monitoring instance container is used for monitoring the state of the first target instance container or the state of the distributed lock.
In some embodiments, after the monitoring instance container monitors that the state of the first target instance container or the state of the distributed lock changes, the monitoring instance container continues to want the relay processor to send the second lock fetching request, and becomes a new execution container for replacing the first target instance container in a manner of competing again.
S1300, determining that the first target instance container successfully acquires a distributed lock;
after the relay processor obtains the first target instance container through screening, it needs to determine that the first target instance container obtains the distributed lock.
The ways to confirm that the first target instance container possesses the distributed lock include two ways: one active and the other passive.
Wherein, the active confirmation means: when the relay processor determines the first target instance container, actively feeding back a confirmation message to the first target instance container, and determining that the first target instance container has monitoring execution authority after obtaining the confirmation message. In the active validation mode, a distributed lock is issued by the relay processor to the first target instance container.
Passive validation refers to: the relay processor, unlike any instance container, sends acknowledgement information, ordering only the received first lock fetch requests, generating a time series. The instance container confirms whether a first lock taking request is before a corresponding first lock taking request or not by accessing the time sequence, if yes, the instance container is confirmed to be a monitoring instance container; if not, confirming that the object is the first object instance container. In passive mode, the first target instance container obtains the distributed lock by requesting it.
The distributed lock is used for confirming that one instance container obtains current monitoring authority among a plurality of instance containers, and because of the uniqueness of the distributed lock, the instance container of the distributed lock is defined as a first target instance container, and other instance containers lose the data monitoring authority of the current time, so that the instance container becomes a monitoring instance for monitoring the state of the first target instance container or the distributed lock.
S1400, configuring a preset monitoring environment for the first target instance container so that the first target instance container monitors the target data.
When the first target instance container is determined, the first target instance container has the right to monitor the current cloud computing system data.
In order to enable the first target instance container to meet the monitoring requirement, the working environment of the first target instance container needs to be configured, the working environment is a preset monitoring environment, the monitoring environment comprises application programs required by monitoring, and data types required to be monitored by the first target instance container, the configured first target instance container has data types of the application programs and monitoring data used by monitoring, and the application programs can monitor the corresponding data types in the cloud computing system by executing the application programs.
The target data refers to system operation data generated by operation in the cloud computing system, and can also be user data transmitted by a terminal and transmitted in the cloud computing system. The listening right acquired by the first target instance container refers to the listening right to the target data.
In the above embodiment, a plurality of instance containers with the same monitoring task are determined in the cloud link, the plurality of instance containers are distributed and configured into the cloud computing architecture, and the plurality of instance containers all send the first lock-getting request to make a competing for lock. Screening a first target instance container from a plurality of instance containers according to a first lock taking request, further determining that the first target instance container has the qualification of monitoring data, determining that the first target instance container successfully acquires the distributed lock, and stopping executing the data monitoring task by other instance containers after the first target instance container acquires the distributed lock, so as to turn into a monitoring instance container. Therefore, the monitoring task executed by the first target instance container in the cloud computing architecture has uniqueness, so that the calculation power loss caused by the fact that a plurality of instance containers execute the same monitoring task is avoided, and the monitoring efficiency is optimized.
In some implementations, the determination of the first target instance container needs to be made from the time stamp of each instance container. Specifically S1200 includes:
s1211, respectively acquiring time stamps of the received first lock fetching requests;
after receiving each first lock taking request, the relay processor records a time node for receiving each first lock taking request, and generates a time stamp corresponding to each first lock taking request according to the time node. The relay processor reads the time stamp of each first lock request when the first target instance container screening is performed.
S1212, the time stamps are arranged in an ascending order to generate a time sequence;
after the time stamp corresponding to each first lock taking request is obtained, the time stamps are arranged in ascending order according to the time node recorded in each time stamp, and the ascending order results are as follows: and arranging the timestamp with the earliest time in the timestamps in the first bit, and sequentially arranging the timestamps with the later and later acquisition time in sequence, wherein a list generated by arranging is a time sequence.
S1213, determining an instance container corresponding to the timestamp positioned at the first position in the time sequence as the first target instance container.
After the time sequence is generated, determining an instance container corresponding to the timestamp positioned at the first position in the time sequence as a first target instance container, namely determining the instance container corresponding to the first lock taking request received by the relay processor as the first target instance container.
In some implementations, after determining the first target instance container, the first target instance container listens for target data in the cloud computing system. In the data monitoring process, if the first target instance container is down due to operation errors or the first target instance container detects that the abnormal data needs to be further monitored in a refined mode, the system needs to re-determine a new first target instance container. Specifically S1400 includes, after:
s1511, after the state information of the first target instance container is updated, receiving second lock fetching requests sent by the plurality of monitoring instance containers;
when the first target instance container enters a monitoring state, the first target instance container needs to send the running state of the first target instance container or state information corresponding to the distributed lock to a distributed key value database, and the distributed key value database is built with a state container. A distributed key-value store is a key-value store database built by distribution, also known as a K/V store or key-value database, which is a non-relational database. Each value has a unique key association, i.e. a key-value pair, we speak of. After the first target instance container sends the state information to the distributed key value database, the distributed key value database constructs a state container for storing the state information.
After the state container acquires the initial state information of the first target instance container, the initial state information is stored in data, and after the state of the first target instance container or the distributed lock is updated, the first target instance container writes the updated state information into the state container again, and at this time, the initial state information in the state container is covered, namely, the state of the first target instance container or the distributed lock is changed.
When the state information of the first target instance container is updated, the state update information is monitored by a plurality of monitoring instance containers with changed monitoring state information, and after the state information is monitored to be changed, the plurality of monitoring instance containers compete again to elect itself as a new first target instance container. Thus, the plurality of snoop instance containers may again send a second lock request to the relay processor.
The contents of the second fetch request are generally the same as the contents of the first fetch request. However, in some embodiments, the second lock access request is different from the first lock access request, for example, the plurality of snoop instance containers snoop the busyness of the work of the relay processor while listening for the status information change, and when it is monitored that the work of the relay processor is not busy, send the second lock access request that needs the response of the relay processor. And when the relay processor is monitored to be in a busy working state, sending a second lock fetching request which does not need to be responded to the relay processor.
S1512, determining any one of the plurality of monitoring instance containers as a second target instance container according to the second lock fetching request, so that the second target instance container replaces the first target instance container.
After the relay processor obtains the plurality of second lock fetching requests, the steps S1211-S1213 are continuously adopted, and a new first target instance container is selected from the plurality of listening instance containers.
In some embodiments, when the working state of the relay processor is in a busy state, the relay processor only responds to the first second lock-taking request received by the relay processor after receiving the plurality of second lock-taking requests. After the second lock taking request is responded, no response and processing are carried out on other subsequent second lock taking requests, so that the consumption of calculation force of tasks corresponding to the second lock taking request is reduced, and the processing efficiency is improved.
And according to the new first target instance container generated by the second lock taking request, replacing the original first target instance container, and monitoring target data of the cloud computing system. And the rest of the plurality of monitoring instance containers continue to monitor the state information of the new first target instance container in the state container, and prepare to become the new first target instance container in the next competitive time.
Through monitoring and election, the problem that when a single first target instance container is down or a task changes, the monitoring work of the whole system is in a blank period can be avoided, the integrity of monitoring data can be well ensured, and the stability of the whole monitoring system is higher.
In some embodiments, after the state information of the first target instance container changes, the corresponding state information is written into the state container, so that the monitoring instance container monitors the working state of the first target instance container.
S1521, writing a state container into a preset distributed key value database;
when the first target instance container enters a monitoring state, the first target instance container needs to send the running state of the first target instance container or state information corresponding to the distributed lock to a distributed key value database, and the distributed key value database is built with a state container. A distributed key-value store is a key-value store database built by distribution, also known as a K/V store or key-value database, which is a non-relational database. Each value has a unique key association, i.e. a key-value pair, we speak of. After the first target instance container sends the state information to the distributed key value database, the distributed key value database constructs a state container for storing the state information.
S1522, in the data monitoring process, the state information is sent to the state container, so that the state container updates the state data according to the state information.
After the state container acquires the initial state information of the first target instance container, the initial state information is stored in data, and after the state of the first target instance container or the distributed lock is updated, the first target instance container writes the updated state information into the state container again, and at this time, the initial state information in the state container is covered, namely, the state of the first target instance container or the distributed lock is changed.
In some implementations, the state container also communicates events of the first target instance container state information change to the listening instance container by way of being listened to. So that the listening instance container can compete to become a new first target instance container after receiving the event of the status information update.
S1531, obtaining registration requests of the plurality of monitoring instance containers;
when the first target instance container is subjected to election, other instance containers which are not subjected to election are automatically confirmed to be monitoring instance containers.
When the self is confirmed as the monitoring instance container, the plurality of monitoring instance containers send registration requests to the state container. The registration request records the identity information of each monitoring instance container.
S1532, configuring the monitoring authorities of the monitoring instances according to the registration request.
After the state container receives the registration requests sent by the plurality of monitoring instance containers, the same monitoring authority is configured for each monitoring instance container according to the registration requests, so that each monitoring instance container has the authority of performing state monitoring in the instance container. And then, after the state of the first target instance container or the distributed lock is changed, timely competing to generate a new first target instance container.
By setting the state container, timeliness of monitoring state information can be avoided, and timeliness of generation of a new first target instance container is guaranteed. Meanwhile, the monitoring instance container is prevented from directly monitoring the state of the first target instance container, and a larger load is generated on the first target instance container.
In some implementations, the plurality of listening instances listens for the state of the first target instance container or the distributed lock. When the state of the first target instance container or the distributed lock is monitored to change, the plurality of monitoring instances need to race again to become a new first target instance container.
S1541, sending the registration request to the state container;
When the first target instance container is subjected to election, other instance containers which are not subjected to election are automatically confirmed to be monitoring instance containers.
When the self is confirmed as the monitoring instance container, the plurality of monitoring instance containers send registration requests to the state container. The registration request records the identity information of each monitoring instance container.
S1542, monitoring the state information in the state container according to the monitoring authority configured by the registration request;
after the state container receives the registration requests sent by the plurality of monitoring instance containers, the same monitoring authority is configured for each monitoring instance container according to the registration requests, so that each monitoring instance container has the authority of performing state monitoring in the instance container. And then, after the state of the first target instance container or the distributed lock is changed, timely competing to generate a new first target instance container.
After the state container confirms that the registration of each monitoring instance container is successful, each monitoring instance container monitors the state information in the state container.
S1543, when the state information is monitored to be updated, a preset second lock fetching request is sent.
After the state of the first target instance container or the distributed lock is changed, the state information after the change of the first target instance container is sent to the state container, and the state container updates data according to the state information. And when the monitoring instance container monitors to obtain the state information update, sending a second lock-taking request to the relay processor.
After the relay processor obtains the plurality of second lock fetching requests, the steps S1211-S1213 are continuously adopted, and a new first target instance container is selected from the plurality of listening instance containers.
In some embodiments, when the working state of the relay processor is in a busy state, the relay processor only responds to the first second lock-taking request received by the relay processor after receiving the plurality of second lock-taking requests. After the second lock taking request is responded, no response and processing are carried out on other subsequent second lock taking requests, so that the consumption of calculation force of tasks corresponding to the second lock taking request is reduced, and the processing efficiency is improved.
In some embodiments, when the first target instance container generates corresponding monitoring information by monitoring target data, the monitoring information needs to be classified, and then different data is classified and stored according to a classification result.
S1611, collecting monitoring information of the target data;
the first target instance container monitors target data and stores the monitored data to form monitoring information. In some implementations, the snoop information can be a snoop log. However, the data format of the listening information is not limited thereto, and in some embodiments, the listening information can be extracted text, image, or audio-video data.
S1612, dividing the monitoring information into hot data and cold data based on a preset classification strategy;
after monitoring information is obtained, the monitored information needs to be subjected to data classification, and the data classification mode is as follows: according to a preset classification strategy, the classification strategy is as follows: dividing the data types of the monitoring information, wherein the dividing standard is the use or access frequency of the data types in a set time, a corresponding access frequency threshold value is set, and when the access frequency of the data types represented by the monitoring information is greater than or equal to the access frequency threshold value, the type of the monitoring information is defined as hot data. Otherwise, the type of the interception information is defined as cold data.
In some embodiments, for sensitivity to nascent data, classification strategies are defined as: classifying the monitoring information, and defining the classification result represented by the monitoring information as hot data when the monitoring information is not in all known data classifications; conversely, when the monitored information is in the known data classification, the classification result characterized by the monitored information is defined as cold data.
S1613, the hot data are stored locally, and the cold data are sent to a preset remote storage space to be stored.
The monitoring information defined as the hot data is easy to be called by the system because of the higher information content, so that the hot data is stored in the current storage space of the server where the first target instance container is located when the hot data is stored. However, for the listening information defined as cold data, since the amount of information contained in the listening information is relatively small, the chance of being called up by the system is relatively small, and therefore, when the listening information is stored, the cold data needs to be sent to a preset remote storage space for storage. And the separate storage of the cold and hot data is beneficial to saving the local storage space and improving the response speed to the hot data in the subsequent retrieval.
In some embodiments, when the first target instance container monitors data, after an abnormal index appears in the target data, it needs to monitor the depth of the abnormal data represented by the abnormal index, so as to further obtain the root cause of the abnormal index through the depth monitoring.
S1711, acquiring abnormal indexes of the target data;
when the first target instance container monitors target data, corresponding conventional threshold intervals are set for monitored data in the target data, after the target data are obtained through reading, data information in the target data are compared with preset conventional threshold intervals, and abnormal indexes in the target data are determined through comparison.
The target data comprises a plurality of data types, so that corresponding normal threshold intervals are set for each different data type, and then each type of data is compared with the corresponding normal threshold intervals, so that corresponding abnormal indexes can be screened from the target data.
In some embodiments, the anomaly index can be anomaly data that is not recorded or can not be categorized in an existing database.
S1712, reading a depth monitoring strategy for performing depth monitoring on the abnormal index according to the abnormal index;
after the abnormal index is obtained through reading, the first target instance container needs to perform further depth monitoring on the abnormal data corresponding to the abnormal index. Specifically, the first target instance container reads the depth monitoring policy corresponding to the abnormal index.
Different depth monitoring strategies are set for different abnormal indexes, for example, when the number of accesses to a certain resource or a certain class of resources in a cloud computing system exceeds a threshold value, the corresponding depth monitoring strategies are as follows: and carrying out data monitoring on the access terminals of the type of data, and identifying each accessed terminal through the set abnormal terminal identification rule. The depth snoop policy is not limited thereto, and in some embodiments, when abnormal data that cannot be categorized is identified to occur in the target data, the depth snoop policy is: and tracking and recording the sending node, the path node or the receiving node of the abnormal data corresponding to the abnormal index. Therefore, the depth monitoring strategy can be set according to the specific scene of the abnormal index, and the purpose of the depth monitoring strategy is to analyze the source or root cause of the abnormal index through deeper data monitoring.
S1713, unlocking the distributed lock according to the depth monitoring strategy, and sending a depth monitoring lock request;
when the first target instance container reads the depth monitoring strategy corresponding to the abnormal data, the obtained distributed lock is unlocked, and when the first target instance container is unlocked, the running state of the first target instance container is changed, or the state of the distributed lock is changed. And when the first target instance container is unlocked, the new state information is sent to the state container, so that the state container updates the state information of the first target instance container, and further, the cloud computing system generates a new first target instance container in an competitive manner.
The first target instance container needs to send a deep snoop lock request to the relay processor while performing distributed unlocking operation to ensure uniqueness of the first target instance container on the deep snoop of the abnormal index, wherein the deep snoop lock request is used for the relay server not to issue the same deep snoop task of the abnormal index to the new first target instance container.
S1714, performing deep monitoring on the abnormal data represented by the abnormal index according to the locking result of the deep monitoring locking request.
And the first target instance container performs an abnormal state deep monitoring task to the relay processor according to the deep monitoring lock request to acquire the lock. After the relay processor reads the deep listening lock request, the relay processor confirms to the first target instance container that the relay processor acquires the data lock with the abnormal index deep listening. And after the first target instance container confirms to acquire the data lock, performing depth monitoring on the abnormal index according to a depth monitoring strategy. It should be noted that when the first target instance container is unlocked by the distributed lock, the authority for performing regular snooping on the target data is automatically lost, and the snooping task is accepted by the new first target instance container.
And the depth monitoring is carried out on the abnormal indexes, so that the rapid tracking processing capability of the cloud computing system on the abnormal data is facilitated, and the processing efficiency of the abnormal data is improved. Meanwhile, matching with the election rule of the first target instance container, the deep monitoring can be performed under the condition that the continuity of the conventional data monitoring task is not damaged, and the stability and layering of the cloud computing system on the data monitoring are well ensured. The cloud computing system operation safety is improved.
In order to solve the technical problems, the embodiment of the application also provides computer equipment. Referring specifically to fig. 2, fig. 2 is a basic structural block diagram of a computer device according to the present embodiment.
As shown in fig. 2, the internal structure of the computer device is schematically shown. The computer device includes a processor, a non-volatile storage medium, a memory, and a network interface connected by a system bus. The nonvolatile storage medium of the computer device stores an operating system, a database and computer readable instructions, the database can store a control information sequence, and the computer readable instructions can enable the processor to realize a distributed monitoring method when the computer readable instructions are executed by the processor. The processor of the computer device is used to provide computing and control capabilities, supporting the operation of the entire computer device. The memory of the computer device may have stored therein computer readable instructions that, when executed by the processor, cause the processor to perform a distributed snoop method. The network interface of the computer device is for communicating with a terminal connection. It will be appreciated by persons skilled in the art that the architecture shown in fig. 2 is merely a block diagram of some of the architecture relevant to the present inventive arrangements and is not limiting as to the computer device to which the present inventive arrangements are applicable, and that a particular computer device may include more or fewer components than shown, or may combine some of the components, or have a different arrangement of components.
In this embodiment, the processor is configured to perform a specific function of the distributed monitoring method, and the memory stores program codes and various data required for executing the distributed monitoring method. The network interface is used for data transmission between the user terminal or the server. The memory in this embodiment stores program codes and data required for executing all the sub-modules in the distributed monitoring apparatus, and the server can call the program codes and data of the server to execute the functions of all the sub-modules.
When the computer equipment performs text conversion, a plurality of instance containers with the same monitoring task are determined in a cloud link, the plurality of instance containers are distributed and configured into a cloud computing architecture, and the plurality of instance containers all send a first lock-taking request to compete for lock. Screening a first target instance container from a plurality of instance containers according to a first lock taking request, further determining that the first target instance container has the qualification of monitoring data, determining that the first target instance container successfully acquires the distributed lock, and stopping executing the data monitoring task by other instance containers after the first target instance container acquires the distributed lock, so as to turn into a monitoring instance container. Therefore, the monitoring task executed by the first target instance container in the cloud computing architecture has uniqueness, so that the calculation power loss caused by the fact that a plurality of instance containers execute the same monitoring task is avoided, and the monitoring efficiency is optimized.
The application also provides a storage medium storing computer readable instructions that, when executed by one or more processors, cause the one or more processors to perform the steps of any of the embodiments of the distributed listening method described above.
Those skilled in the art will appreciate that implementing all or part of the above-described methods in accordance with the embodiments may be accomplished by way of a computer program stored in a computer-readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. The storage medium may be a nonvolatile storage medium such as a magnetic disk, an optical disk, a Read-Only Memory (ROM), or a random access Memory (Random Access Memory, RAM).
Those of skill in the art will appreciate that the various operations, methods, steps in the flow, acts, schemes, and alternatives discussed in the present application may be alternated, altered, combined, or eliminated. Further, other steps, means, or steps in a process having various operations, methods, or procedures discussed herein may be alternated, altered, rearranged, disassembled, combined, or eliminated. Further, steps, measures, schemes in the prior art with various operations, methods, flows disclosed in the present application may also be alternated, altered, rearranged, decomposed, combined, or deleted.
The foregoing is only a partial embodiment of the present application, and it should be noted that it will be apparent to those skilled in the art that modifications and adaptations can be made without departing from the principles of the present application, and such modifications and adaptations are intended to be comprehended within the scope of the present application.
Claims (9)
1. A distributed listening method, comprising a relay processor configured to:
acquiring first lock fetching requests sent by a plurality of instance containers;
determining, based on the first lock fetch request, any one of the plurality of instance containers as a first target instance container, and determining instance containers other than the first target instance container as a plurality of listening instance containers;
determining that the first target instance container successfully acquired a distributed lock;
configuring a preset monitoring environment for the first target instance container so that the first target instance container monitors target data;
the first target instance container is further to:
acquiring an abnormal index of the target data, wherein the abnormal index is abnormal data which cannot be classified in the existing database;
according to the abnormal index, a depth monitoring strategy for performing depth monitoring on the abnormal index is read;
Unlocking the distributed lock according to the depth monitoring strategy, and sending a depth monitoring lock request;
and carrying out deep monitoring on the abnormal data represented by the abnormal index according to the locking result of the deep monitoring locking request.
2. The distributed snoop method of claim 1, wherein said determining, based on said first lock request, that any of said plurality of instance containers is a first target instance container comprises:
respectively acquiring time stamps of the received first lock fetching requests;
the time stamps are arranged in an ascending order to generate a time sequence;
and determining an instance container corresponding to the timestamp positioned at the first bit in the time sequence as the first target instance container.
3. The distributed listening method according to claim 1, wherein after the configuring the preset listening environment to the first target instance container, the method comprises:
after the state information of the first target instance container is updated, receiving second lock fetching requests sent by the plurality of monitoring instance containers;
and determining any one of the plurality of monitoring instance containers as a second target instance container according to the second lock fetching request so as to enable the second target instance container to replace the first target instance container.
4. The distributed listening method of claim 3, wherein the first target instance container is further for:
writing a state container into a preset distributed key value database;
and in the data monitoring process, the state information is sent to the state container, so that the state container updates the state data according to the state information.
5. The distributed listening method of claim 4, wherein the status container is further configured to:
acquiring registration requests of the plurality of monitoring instance containers;
and configuring the monitoring authorities of the plurality of monitoring instances according to the registration request.
6. The distributed listening method of claim 5, wherein the plurality of listening instances are further for:
sending the registration request to the status container;
monitoring state information in the state container according to the monitoring authority configured by the registration request;
and when the state information is monitored to be updated, sending a preset second lock taking request.
7. The distributed listening method of claim 1, wherein the first target instance container is further for:
Collecting monitoring information of the target data;
dividing the monitoring information into hot data and cold data based on a preset classification strategy;
and locally storing the hot data, and sending the cold data to a preset remote storage space for storage.
8. A computer device, the computer device comprising a memory and a processor;
the memory is used for storing a computer program;
the processor is configured to execute the computer program and implement when executing the computer program:
a distributed listening method as claimed in any one of claims 1 to 7.
9. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program which, when executed by a processor, causes the processor to implement the distributed listening method as claimed in any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310679824.5A CN116405509B (en) | 2023-06-09 | 2023-06-09 | Distributed monitoring method, computer equipment and storage medium thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310679824.5A CN116405509B (en) | 2023-06-09 | 2023-06-09 | Distributed monitoring method, computer equipment and storage medium thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116405509A CN116405509A (en) | 2023-07-07 |
| CN116405509B true CN116405509B (en) | 2023-09-01 |
Family
ID=87014690
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310679824.5A Active CN116405509B (en) | 2023-06-09 | 2023-06-09 | Distributed monitoring method, computer equipment and storage medium thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116405509B (en) |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107391276A (en) * | 2017-07-05 | 2017-11-24 | 腾讯科技（深圳）有限公司 | Distributed monitor method, interception control device and system |
| CN110290180A (en) * | 2019-05-31 | 2019-09-27 | 北京大米科技有限公司 | Distributed task dispatching method, apparatus, computer equipment and storage medium |
| CN110688206A (en) * | 2019-09-05 | 2020-01-14 | 平安科技（深圳）有限公司 | Timing task scheduling method and device, computer equipment and storage medium |
| CN111163140A (en) * | 2019-12-20 | 2020-05-15 | 深圳市中农易讯信息技术有限公司 | Method, apparatus and computer readable storage medium for resource acquisition and allocation |
| CN111459954A (en) * | 2020-03-04 | 2020-07-28 | 深圳壹账通智能科技有限公司 | Distributed data synchronization method, device, equipment and medium |
| CN111970148A (en) * | 2020-08-14 | 2020-11-20 | 北京金山云网络技术有限公司 | Distributed task scheduling method and system |
| CN113553370A (en) * | 2021-07-27 | 2021-10-26 | 百度在线网络技术（北京）有限公司 | Abnormality detection method, abnormality detection device, electronic device, and readable storage medium |
| CN113949691A (en) * | 2021-10-15 | 2022-01-18 | 湖南麒麟信安科技股份有限公司 | ETCD-based virtual network address high-availability implementation method and system |
| CN114035969A (en) * | 2021-10-29 | 2022-02-11 | 济南浪潮数据技术有限公司 | Method, system and equipment for realizing distributed block storage multi-path ISCSI lock |
| CN114297241A (en) * | 2021-12-29 | 2022-04-08 | 北京人大金仓信息技术股份有限公司 | Resource locking method, device, equipment and medium |
| CN114900449A (en) * | 2022-03-30 | 2022-08-12 | 网宿科技股份有限公司 | Resource information management method, system and device |
| CN115231345A (en) * | 2022-05-28 | 2022-10-25 | 聚时科技(上海)有限公司 | Intelligent control method and system for lock dismounting and mounting process |
-
2023
- 2023-06-09 CN CN202310679824.5A patent/CN116405509B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107391276A (en) * | 2017-07-05 | 2017-11-24 | 腾讯科技（深圳）有限公司 | Distributed monitor method, interception control device and system |
| CN110290180A (en) * | 2019-05-31 | 2019-09-27 | 北京大米科技有限公司 | Distributed task dispatching method, apparatus, computer equipment and storage medium |
| CN110688206A (en) * | 2019-09-05 | 2020-01-14 | 平安科技（深圳）有限公司 | Timing task scheduling method and device, computer equipment and storage medium |
| CN111163140A (en) * | 2019-12-20 | 2020-05-15 | 深圳市中农易讯信息技术有限公司 | Method, apparatus and computer readable storage medium for resource acquisition and allocation |
| CN111459954A (en) * | 2020-03-04 | 2020-07-28 | 深圳壹账通智能科技有限公司 | Distributed data synchronization method, device, equipment and medium |
| CN111970148A (en) * | 2020-08-14 | 2020-11-20 | 北京金山云网络技术有限公司 | Distributed task scheduling method and system |
| CN113553370A (en) * | 2021-07-27 | 2021-10-26 | 百度在线网络技术（北京）有限公司 | Abnormality detection method, abnormality detection device, electronic device, and readable storage medium |
| CN113949691A (en) * | 2021-10-15 | 2022-01-18 | 湖南麒麟信安科技股份有限公司 | ETCD-based virtual network address high-availability implementation method and system |
| CN114035969A (en) * | 2021-10-29 | 2022-02-11 | 济南浪潮数据技术有限公司 | Method, system and equipment for realizing distributed block storage multi-path ISCSI lock |
| CN114297241A (en) * | 2021-12-29 | 2022-04-08 | 北京人大金仓信息技术股份有限公司 | Resource locking method, device, equipment and medium |
| CN114900449A (en) * | 2022-03-30 | 2022-08-12 | 网宿科技股份有限公司 | Resource information management method, system and device |
| CN115231345A (en) * | 2022-05-28 | 2022-10-25 | 聚时科技(上海)有限公司 | Intelligent control method and system for lock dismounting and mounting process |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116405509A (en) | 2023-07-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7617190B2 (en) | Data feeds for management systems | |
| US20190036901A1 (en) | Techniques for credential generation | |
| CN105247529B (en) | The synchronous voucher hash between directory service | |
| CN101981531B (en) | Aggregating recurrent schedules to optimize resource consumption | |
| US11411888B2 (en) | Distributed policy enforcement with optimizing policy transformations | |
| US20070299631A1 (en) | Logging user actions within activity context | |
| Khriji et al. | Design and implementation of a cloud-based event-driven architecture for real-time data processing in wireless sensor networks | |
| CN109684370A (en) | Daily record data processing method, system, equipment and storage medium | |
| US9258312B1 (en) | Distributed policy enforcement with verification mode | |
| CN110515912A (en) | Log processing method, device, computer installation and computer readable storage medium | |
| CN101365119B (en) | Video recording balance equalizing method used for network video monitoring system | |
| CN102291446A (en) | Flexible architecture for notifying applications of state changes | |
| US20210383187A1 (en) | Decentralized machine learning system and a method to operate the same | |
| WO2013023095A2 (en) | Smart thin client server | |
| Alkhabbas et al. | Characterizing internet of things systems through taxonomies: A systematic mapping study | |
| CN104104702A (en) | Cloud computation architecture facing household internet of things | |
| CN108427619B (en) | Log management method and device, computing equipment and storage medium | |
| CN113010565A (en) | Server cluster-based server real-time data processing method and system | |
| CN115811546A (en) | System and method for realizing network cooperative distributed processing for scientific and technological service | |
| Li et al. | Granularity decision of microservice splitting in view of maintainability and its innovation effect in government data sharing | |
| CN116405509B (en) | Distributed monitoring method, computer equipment and storage medium thereof | |
| CN110061876A (en) | The optimization method and system of O&M auditing system | |
| US20210392135A1 (en) | Securing workload and application access from unauthorized entities | |
| CN116860707A (en) | Material genetic engineering big data safe sharing method and system based on block chain | |
| CN106484712A (en) | The date storage method of distributed file system and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |