CN112416385A - Acquisition component management method and system - Google Patents
Acquisition component management method and system Download PDFInfo
- Publication number
- CN112416385A CN112416385A CN202010814182.1A CN202010814182A CN112416385A CN 112416385 A CN112416385 A CN 112416385A CN 202010814182 A CN202010814182 A CN 202010814182A CN 112416385 A CN112416385 A CN 112416385A
- Authority
- CN
- China
- Prior art keywords
- acquisition
- acquisition component
- component
- components
- information
- 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.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 60
- 230000000712 assembly Effects 0.000 claims abstract description 14
- 238000000429 assembly Methods 0.000 claims abstract description 14
- 238000000034 method Methods 0.000 claims description 63
- 230000008569 process Effects 0.000 claims description 52
- 230000002159 abnormal effect Effects 0.000 claims description 29
- 238000012544 monitoring process Methods 0.000 claims description 24
- 238000004590 computer program Methods 0.000 claims description 10
- 238000001514 detection method Methods 0.000 claims description 9
- 230000002547 anomalous effect Effects 0.000 claims description 6
- 238000010586 diagram Methods 0.000 description 6
- 238000012986 modification Methods 0.000 description 5
- 230000004048 modification Effects 0.000 description 5
- 230000005856 abnormality Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000035899 viability Effects 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000009933 burial Methods 0.000 description 2
- 239000003795 chemical substances by application Substances 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008094 contradictory effect Effects 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000007613 environmental effect Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the application provides a collection component management method, which comprises the following steps: acquiring an acquisition component list, wherein the acquisition component list comprises a plurality of acquisition component information of a plurality of acquisition components, and each acquisition component information comprises one or more dimension information of the corresponding acquisition component; determining a plurality of acquisition components to be selected from the acquisition component list according to a preset dimension; selecting a plurality of acquisition components to be upgraded from the plurality of acquisition components to be selected according to a preset release ratio; and upgrading the acquisition assemblies to be upgraded to obtain a plurality of upgraded acquisition assemblies. According to the technical scheme, the plurality of acquisition assemblies can be managed through the acquisition assembly list, the plurality of acquisition assemblies to be upgraded are selected from the plurality of acquisition assembly information according to the dimension information and the release ratio to perform gray scale upgrading, and the management capacity and the upgrading efficiency of the acquisition assemblies are improved.
Description
Technical Field
The embodiment of the application relates to the technical field of computers, in particular to a method, a system and equipment for managing a collection assembly and a computer readable storage medium.
Background
With the rapid development of computer technology and network technology, user data is also rapidly increasing. To process massive user data, a server cluster consisting of a huge number of servers needs to be deployed. Each server is provided with a data acquisition assembly for data acquisition, analysis and transmission. At present, each acquisition component in a server is deployed as an independent individual, and after deployment is completed, no effective management method exists for the running state and subsequent upgrading of the acquisition component. Therefore, how to solve the management problem of a large number of acquisition components in a server cluster and improve the upgrading efficiency of the acquisition components becomes one of the technical problems to be solved at present.
Disclosure of Invention
An object of the embodiments of the present application is to provide a method, a system, a computer device, and a computer-readable storage medium for managing collection components, which are used to solve the technical problem of low efficiency in managing and upgrading collection components.
One aspect of the embodiments of the present application provides a collection component management method, including: acquiring an acquisition component list, wherein the acquisition component list comprises a plurality of acquisition component information of a plurality of acquisition components, and each acquisition component information comprises one or more dimension information of the corresponding acquisition component; determining a plurality of acquisition components to be selected from the acquisition component list according to a preset dimension; selecting a plurality of acquisition components to be upgraded from the plurality of acquisition components to be selected according to a preset release ratio; and upgrading the acquisition assemblies to be upgraded to obtain a plurality of upgraded acquisition assemblies.
Optionally, the method further includes: and generating the acquisition component list according to acquisition component information of a registration center, wherein the registration center is used for acquisition component registration and acquisition component information storage.
Optionally, the method further includes: acquiring acquisition component information corresponding to the plurality of updated acquisition components; and updating the acquisition component information corresponding to each updated acquisition component to the acquisition component list.
Optionally, the method further includes: performing survivability anomaly detection on each acquisition assembly to determine whether an anomalous acquisition assembly exists; and if the abnormal acquisition component exists, generating corresponding abnormal alarm information according to the abnormal acquisition component.
Optionally, the performing survivability abnormality detection on each collection assembly to determine whether there is an abnormal collection assembly includes: the detecting viability anomaly for each collection assembly to determine whether there is an anomalous collection assembly comprises: acquiring the process starting time of each acquisition assembly, the corresponding operating system starting time and the corresponding acquisition file deployment time; judging whether a first time interval between the process starting time of each acquisition assembly and the corresponding operating system starting time is greater than a first preset threshold value or not to obtain a first judgment result; judging whether a second time interval between the process starting time of each acquisition assembly and the corresponding acquisition file deployment is greater than a second preset threshold value or not to obtain a second judgment result; and determining that the survivability of the acquisition component is abnormal according to a first judgment result and/or a second judgment result, wherein the first judgment result indicates that the first time interval is greater than the first preset threshold, and the second judgment result indicates that the second time interval is greater than the second preset threshold.
Optionally, the method further includes: monitoring the operation process of each acquisition component; if an operation error occurs in the operation process of one acquisition component, determining an error code corresponding to the acquisition component according to the operation error; and reporting the error code to a monitoring system so that the monitoring system carries out alarm operation according to the error code.
Optionally, the method further includes the step of pre-configuring a plurality of error codes: acquiring a plurality of operation errors of the plurality of acquisition components in the operation process in advance; classifying the plurality of operating errors to obtain a plurality of error classifications; and configuring a corresponding error code for each error classification to obtain the plurality of error codes.
An aspect of an embodiment of the present application further provides an acquisition component management system, including: the acquisition module is used for acquiring an acquisition component list, wherein the acquisition component list comprises a plurality of acquisition component information of a plurality of acquisition components, and each acquisition component information comprises one or more dimension information of the corresponding acquisition component; the determining module is used for determining a plurality of acquisition components to be selected from the acquisition component list according to a preset dimension; the selection module is used for selecting a plurality of acquisition components to be upgraded from the plurality of acquisition components to be selected according to a preset release ratio; and the upgrading module is used for upgrading the acquisition components to be upgraded to obtain a plurality of upgraded acquisition components.
An aspect of the embodiments of the present application further provides a computer device, which includes a memory, a processor, and a computer program stored on the memory and executable on the processor, and when the processor executes the computer program, the computer program is used to implement the steps of the acquisition component management method described above.
An aspect of the embodiments of the present application further provides a computer-readable storage medium, in which a computer program is stored, the computer program being executable by at least one processor to cause the at least one processor to perform the steps of the acquisition component management method as described above.
According to the acquisition component management method, the acquisition component management system, the acquisition component management equipment and the computer-readable storage medium, the acquisition components are managed through the acquisition component list, and the acquisition components to be upgraded are selected from the acquisition component information according to the dimension information and the release ratio to perform gray scale upgrading, so that the acquisition component management capacity and the upgrading efficiency are improved.
Drawings
FIG. 1 schematically illustrates an environmental application diagram according to an embodiment of the present application;
FIG. 2 is a flow chart of a collection component management method according to a first embodiment of the present application;
FIG. 3 schematically shows a flow chart of a collection component management method according to a second embodiment of the present application;
FIG. 4 schematically shows another flowchart of a collection component management method according to a second embodiment of the present application;
FIG. 5 schematically shows another flow chart of a collection component management method according to a second embodiment of the present application;
FIG. 6 schematically shows another flow chart of a collection component management method according to an embodiment II of the present application;
FIG. 7 schematically shows another flow chart of a collection component management method according to a second embodiment of the present application;
FIG. 8 schematically shows an overall flowchart of a collection component management method according to a second embodiment of the present application;
fig. 9 schematically shows a block diagram of an acquisition component management system according to a third embodiment of the present application; and
fig. 10 schematically shows a hardware architecture diagram of a computer device suitable for implementing the acquisition component management method according to a fourth embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application more clearly understood, the embodiments of the present application are described in further detail below with reference to the accompanying drawings and the embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the embodiments of the application and are not intended to limit the embodiments of the application. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without any creative effort belong to the protection scope of the embodiments in the present application.
It should be noted that the description relating to "first", "second", etc. in the present invention is for descriptive purposes only and is not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In addition, technical solutions between various embodiments may be combined with each other, but must be realized by a person skilled in the art, and when the technical solutions are contradictory or cannot be realized, such a combination should not be considered to exist, and is not within the protection scope of the present invention.
The following is an explanation of some terms involved in the present application:
the collection assembly: the data collection, analysis and transmission method is operated in a server as an independent process and is used for collecting, analyzing and transmitting data on the server, such as an Agent.
And (3) collecting component management: and managing the running state of the collection component nodes, including version management, gray scale release, collection component survivability and error monitoring and the like.
Gray scale upgrading: namely, local upgrading, the effect caused by the upgraded program bug can be reduced to the maximum extent.
Fig. 1 schematically shows an environment diagram of an acquisition component management method according to the present application. The environment schematic includes a computer device 20 and a plurality of servers 40.
The computer device 20 is used to manage the acquisition components in the server 40, such as: (1) managing an acquisition component list to obtain which servers are deployed with acquisition components and acquisition component versions in real time; (2) upgrade of acquisition components (e.g., grayscale upgrade); (3) managing the running state of the acquisition assembly: and acquiring whether the operation of the component has errors and whether the process is alive. The computer device 20 may be a single server or a cluster of servers.
A server 40 for installing one or more acquisition components for acquiring and processing user data by the one or more acquisition components.
The management functions of the computer device 20 will be described below by way of several embodiments.
Example one
Fig. 2 schematically shows a flowchart of a collection component management method according to a first embodiment of the present application. The present embodiment may be implemented in a computer device 20. It is to be understood that the flow charts in the embodiments of the present method are not intended to limit the order in which the steps are performed.
As shown in fig. 2, the collection component management method may include steps S200 to S204, in which:
step S200, acquiring an acquisition component list, wherein the acquisition component list comprises a plurality of acquisition component information of a plurality of acquisition components, and each acquisition component information comprises one or more dimension information of the corresponding acquisition component.
The computer device 20 may obtain the collection component list from a registry. The registry can receive a plurality of registration requests sent by a plurality of acquisition components. Each acquisition component (Agent) corresponds to a registration request, and each registration request carries corresponding acquisition component information. After the registration center receives the registration requests, the registration center can analyze one corresponding acquisition component information from each registration request to obtain a plurality of acquisition component information, and can generate the acquisition component list according to the acquisition component information. It should be understood that the registry may be located in the computer device 20 or may be located in a device other than the computer device 20.
Each collection component information may include: the IP address information, host name information, version information, and process number information of the physical machine (server 40) where the component is located are collected accordingly. Each acquisition component information comprises one or more dimension information of the corresponding acquisition component; taking the IP address information as an example, each acquisition component corresponds to one IP address, that is, the IP address can be used as one dimension information.
Step S202, according to preset dimensions, determining a plurality of acquisition components to be selected from the acquisition component list.
The preset dimension may be one or more dimensions. The one or more dimensions may be IP address-based dimensions, version number-based dimensions, machine room-based dimensions, and/or other information-based dimensions. Taking the dimension based on the IP address as an example, the computer device 2 may determine an IP address field in advance, and filter out all the collection components belonging to the IP address of the IP address field from the collection component list.
And step S204, selecting a plurality of acquisition components to be upgraded from the plurality of acquisition components to be selected according to a preset release ratio.
After obtaining the plurality of to-be-selected acquisition components, the computer device 20 may select a plurality of to-be-upgraded acquisition components from the plurality of to-be-selected acquisition components according to the preset distribution ratio. The preset issuing ratio may be a preset fixed value, such as 0.1, 0.2, 0.3, and the like, and the embodiment is not limited. Taking the number of the to-be-selected acquisition components as N, the number of the to-be-upgraded acquisition components as M, and the preset distribution ratio as 0.1 as an example, when the preset distribution ratio is 0.1, then M is 0.1 × N.
In some embodiments, the preset distribution ratio may be dynamically adjusted according to the number of the collection components to be selected. For example, when the number of the to-be-selected acquisition components is greater than a preset value, the preset distribution ratio may be dynamically adjusted to 0.1, and when the number of the to-be-selected acquisition components is less than or equal to the preset value, the preset distribution ratio may be dynamically adjusted to 0.2.
It should be noted that N is a positive integer > 1, N > M > 1, and M is a positive integer.
And step S206, upgrading the acquisition components to be upgraded to obtain a plurality of upgraded acquisition components.
The computer device 20 may obtain the acquisition component information corresponding to the plurality of upgraded acquisition components, so as to update the acquisition component information corresponding to each upgraded acquisition component to the acquisition component list, and delete the acquisition component information of each upgraded acquisition component before upgrading. After an acquisition component is upgraded, version information corresponding to the acquisition component is changed inevitably; if the acquisition component information corresponding to the acquisition component in the acquisition component list is not updated after the acquisition component is upgraded, the acquisition component may be repeatedly updated in the next update, which increases unnecessary resource consumption. Therefore, in order to avoid the problem of repeated updating, the computer device 20 may update the acquisition component information corresponding to the updated acquisition component to the acquisition component list after an acquisition component is updated.
In this embodiment, the computer device 20 implements management capability of the plurality of acquisition components through the acquisition component list, and selects a plurality of acquisition components to be upgraded from the plurality of acquisition component information according to the dimension information and the distribution ratio to perform gray scale upgrade, thereby improving management capability and upgrade efficiency of the acquisition components.
Example two
Fig. 3 schematically shows a flowchart of an acquisition component management method according to the second embodiment of the present application.
As shown in fig. 3, the collection component management method may include steps S300 to S312, in which:
and step S300, generating the acquisition component list according to acquisition component information of a registration center, wherein the registration center is used for acquisition component registration and acquisition component information storage.
The computer device 20 may generate the collection component list in advance from the collection component information of the registry. The collection component information includes IP address information, host name information, version information, and process number information. The registry can be based on component registration for collection and collection information storage.
After each server 40 starts an acquisition component, a corresponding registration request may be generated according to the respective started acquisition component, so as to register in the registry. The registration request may carry acquisition component information corresponding to the acquisition component. And the registry realizes the management of the acquisition components according to the acquisition component list generated by the acquisition component information corresponding to the acquisition components.
The registry can receive a plurality of registration requests corresponding to a plurality of acquisition components. After receiving a plurality of registration requests, the registration center may analyze each registration request to obtain acquisition component information corresponding to each registration request, and generate the acquisition component list according to the obtained acquisition component information. The registry may further store the information of the plurality of collection components in the collection component list, so that the computer device 20 obtains the information of the plurality of collection components corresponding to the plurality of collection components from the collection component list.
In this embodiment, the collection component may register the collection component information in a collection component list when the collection component is started, so as to manage the collection components through the collection component list, thereby improving the management capability of the computer device 20 on the collection components.
Step S302, an acquisition component list is obtained, wherein the acquisition component list comprises a plurality of acquisition component information of a plurality of acquisition components, and each acquisition component information comprises one or more dimension information of the corresponding acquisition component.
The computer device 20 may obtain the collection component list from the registry. And obtaining a plurality of acquisition component information of the plurality of acquisition components from the acquisition component list.
Step S304, determining a plurality of acquisition components to be selected from the acquisition component list according to a preset dimension.
And S306, selecting a plurality of acquisition components to be upgraded from the plurality of acquisition components to be selected according to a preset distribution ratio.
And step S308, upgrading the acquisition components to be upgraded to obtain a plurality of upgraded acquisition components.
Step S310, acquiring acquisition component information corresponding to the plurality of updated acquisition components.
Step S312, updating the acquisition component information corresponding to each updated acquisition component to the acquisition component list.
The acquisition component information corresponding to each upgraded acquisition component is updated to the acquisition component list, so that the problem of repeated updating can be avoided, and the upgrading efficiency of the acquisition components is improved.
As shown in fig. 4, the collection component management method may further include steps S400 to S402, where: step S400, carrying out survivability abnormity detection on each acquisition assembly to determine whether an abnormal acquisition assembly exists; and S402, if the abnormal acquisition component exists, generating corresponding abnormal alarm information according to the abnormal acquisition component. The computer device 20 may detect whether the survivability of the collecting component is abnormal, and if the survivability of the collecting component is abnormal, the monitoring system may alarm, so that the collecting component with abnormal problems may be handled in time, and the safety and the working efficiency of the collecting component are improved.
As shown in fig. 5, the step S400 may further include steps S500 to S508, where:
step S500, acquiring the process starting time of each acquisition assembly, the corresponding operating system starting time and the corresponding acquisition file deployment time.
The computer device 20 may monitor a plurality of collection components, and may obtain a process start time, a corresponding operating system start time, and a corresponding collection file deployment time of each collection component. The process starting time is the time of starting the process of the acquisition assembly; the starting time of the operating system is the starting time of the operating system corresponding to the acquisition assembly; the collection file deployment time is the generation time of the executable binary file corresponding to the collection component, wherein the collection file deployment time may be the last modification time of the executable binary file.
As a component for data acquisition, the acquisition component can execute a corresponding data acquisition task after being started. It should be understood that, when the operating system corresponding to the acquisition component is started, the acquisition component deployed in the operating system will follow the start.
However, the inventor finds that the first time interval from the start of the operating system corresponding to the collection component to the process start of the collection component and the time interval from the completion of the modification of the executable binary file of the collection component to the process start of the collection component, which do not have the potential safety hazard, do not generally exceed a corresponding threshold. If the time interval from the starting of the corresponding operating system of the acquisition component to the starting of the process of the acquisition component exceeds the corresponding threshold value, the acquisition component may have an exception, and if the time interval from the completion of the modification of the executable binary file of the acquisition component to the starting of the process of the acquisition component exceeds the corresponding threshold value, the acquisition component may have an exception.
Step S502, judging whether a first time interval between the process starting time of each acquisition assembly and the corresponding operating system starting time is greater than a first preset threshold value or not to obtain a first judgment result;
in an exemplary embodiment, the computer device 20 may preset the first preset threshold, where the first preset threshold may be obtained from a time interval between the start of the operating system corresponding to the acquisition component without the security risk and the start of the process of the acquisition component.
After obtaining the process starting time of each acquisition component and the corresponding operating system starting time, the computer device 20 may determine whether a first time interval between the process starting time of each acquisition component and the corresponding operating system starting time is greater than a first preset threshold.
If the first time interval corresponding to one of the acquisition assemblies is not greater than the first preset threshold, it can be determined that the acquisition assembly does not have the problem of survivability abnormality.
And if the first time interval corresponding to one of the acquisition assemblies is larger than the first preset threshold, generating a corresponding first judgment result. And may determine that the collection assembly may have a problem with viability anomaly for which the computer device 20 may need to perform further viability anomaly detection to determine whether the collection assembly is truly anomalous.
Step S504, determining whether a second time interval between the process start time of each acquisition component and the corresponding acquisition file deployment is greater than a second preset threshold, and obtaining a second determination result.
In an exemplary embodiment, the computer device 20 may preset the second preset threshold, where the second preset threshold may be obtained from a time interval between deployment time of an acquisition file corresponding to an acquisition component without a potential safety hazard and process start of the acquisition component.
And when the executable binary file of the acquisition component is modified, restarting the acquisition component, and if the time interval from the modification of the executable binary file of the acquisition component to the process starting of the acquisition component exceeds the threshold, generating a corresponding second judgment result and determining that the acquisition component possibly has an abnormality.
It should be noted that a second time interval between the collection file deployment time of the collection component and the process start time of the collection component is greater than the second preset threshold, which may be caused by an excessively long generation time of the executable file corresponding to the collection component. And under the normal condition, the second time interval is not larger than the second preset threshold value.
Step S506, determining an acquisition component with abnormal survivability according to a first determination result and a second determination result, where the first determination result indicates that the first time interval is greater than the first preset threshold, and the second determination result indicates that the second time interval is greater than the second preset threshold.
If the first time interval corresponding to one collection assembly is greater than the first preset threshold and the second time interval is greater than the second preset threshold, it can be determined that the collection assembly has a survivability abnormality. If it is determined that the survivability of the collecting component has an abnormal problem, the computer device 20 may generate corresponding abnormal information according to the collecting component, and report the abnormal information to the monitoring system, so that the monitoring system performs an alarm operation.
In this embodiment, the computer device 20 may determine which collecting assemblies may have a potential safety hazard by detecting whether the survivability of each collecting assembly is abnormal, and process the collecting assemblies that may have the potential safety hazard, so as to improve the safety and the working efficiency of the collecting assemblies.
As shown in fig. 6, the collection component management method may further include steps S600 to S604, where: s600, monitoring the operation process of each acquisition assembly; step S602, if an operation error of one of the acquisition components in the operation process is monitored, determining an error code corresponding to the acquisition component according to the operation error; and step S604, reporting the error code to a monitoring system so that the monitoring system performs alarm operation according to the error code. The error code may be pre-configured to instruct the monitoring system to perform a corresponding alarm operation.
In some embodiments, the computer device 20 may further record the obtained operation error in a log file, for example, in a code implementation, the computer device 20 may perform an error code burial point at a position where the operation error occurs, and record operation error information to the log file through the error log, where the operation error information includes the error code burial point information. The embodiment can also be used for collecting the uniform error code state summary according to the acquisition component error code library, and reporting the error code to the monitoring system for alarming.
The computer device 20 can process and alarm the operation error in time by monitoring the operation process of the acquisition assembly, thereby improving the safety and the working efficiency.
As shown in fig. 7, the collection component management method may further include steps S700 to S704 of configuring a plurality of error codes in advance, where: step S700, acquiring a plurality of operation errors of the plurality of acquisition components in the operation process in advance; step S702, classifying the operation errors to obtain a plurality of error classifications; and step S704, configuring a corresponding error code for each error classification to obtain the plurality of error codes.
The computer device 20 may be preconfigured with a plurality of error codes. And informing the corresponding monitoring system to perform corresponding alarm operation through the error code.
For easy understanding, as shown in fig. 8, the present embodiment also provides an overall flowchart of the second embodiment. The method comprises the following specific steps.
Step S1, the server 40 starts the acquisition component;
step S2, the server 40 acquires the collection component information of the collection component and sends the collection component information to the registration center;
step S3, the computer device 20 receives a plurality of pieces of acquisition component information, and generates an acquisition component list according to the plurality of pieces of acquisition component information;
step S4, computer device 20 obtains a collection component list;
step S5, the computer device 20 determines a plurality of to-be-selected collection components from the collection component list according to preset dimension information;
step S6, the computer device 20 selects a plurality of to-be-upgraded acquisition components from the plurality of to-be-selected acquisition components according to a preset distribution ratio;
step S7, the computer device 20 upgrades the plurality of acquisition components to be upgraded to obtain a plurality of upgraded acquisition components;
step S8, the computer device 20 acquires acquisition component information corresponding to the plurality of updated acquisition components;
step S9, the computer device 20 acquires acquisition component information corresponding to the plurality of updated acquisition components;
step S10, the computer device 20 testing the viability of the collection assembly;
step S11, judging whether a first time interval between the process starting time of each acquisition assembly and the corresponding operating system starting time is larger than a first preset threshold value or not, and obtaining a first judgment result; judging whether a second time interval between the process starting time of each acquisition assembly and the corresponding acquisition file deployment is greater than a second preset threshold value or not to obtain a second judgment result;
step S12, if the first time interval is greater than the first preset threshold and the second time interval is greater than the second preset threshold, generating abnormal information;
step S13, the abnormal information is uploaded to the monitoring system, so that the monitoring system can perform alarm operation according to the abnormal information or the error code;
step S14, the computer device 20 monitors the operation process of the acquisition component;
step S15, judging whether the operation process of the acquisition assembly is wrong in trip operation;
step S16, if the operation process of the acquisition assembly is wrong, writing an error code into a log file, and generating a corresponding error code;
step S17, uploading the error code to the monitoring system;
and step S18, making the monitoring system perform alarm operation according to the abnormal information or the error code.
EXAMPLE III
Fig. 9 schematically illustrates a block diagram of an acquisition component management system according to a third embodiment of the present application, which may be partitioned into one or more program modules, stored in a storage medium, and executed by one or more processors to implement the third embodiment of the present application. The program modules referred to in the embodiments of the present application refer to a series of computer program instruction segments capable of performing specific functions, and the following description will specifically describe the functions of each program module in the embodiments.
As shown in fig. 9, the collection component management system 200 may include an acquisition module 910, a determination module 920, a selection module 930, and an upgrade module 940, wherein:
the obtaining module 910 is configured to obtain a collection component list, where the collection component list includes multiple collection component information of multiple collection components, and each collection component information includes one or more dimension information of a corresponding collection component.
A determining module 920, configured to determine, according to a preset dimension, a plurality of to-be-selected acquisition components from the acquisition component list.
A selecting module 930, configured to select, according to a preset distribution ratio, a plurality of to-be-upgraded acquisition components from the plurality of to-be-selected acquisition components.
And an upgrading module 940, configured to upgrade the multiple acquisition components to be upgraded to obtain multiple upgraded acquisition components.
In an exemplary embodiment, the collection component management system 200 may further include a generation module configured to: and generating the acquisition component list according to acquisition component information of a registration center, wherein the registration center is used for acquisition component registration and acquisition component information storage.
In an exemplary embodiment, the collection component management system 200 may further include an update module configured to: acquiring acquisition component information corresponding to the plurality of updated acquisition components; and updating the acquisition component information corresponding to each updated acquisition component to the acquisition component list.
In an exemplary embodiment, the collection component management system 200 may further include a detection module configured to: performing survivability anomaly detection on each acquisition assembly to determine whether an anomalous acquisition assembly exists; and if the abnormal acquisition component exists, generating corresponding abnormal alarm information according to the abnormal acquisition component.
In an exemplary embodiment, the detection module is further configured to: acquiring the process starting time of each acquisition assembly, the corresponding operating system starting time and the corresponding acquisition file deployment time; judging whether a first time interval between the process starting time of each acquisition assembly and the corresponding operating system starting time is greater than a first preset threshold value or not to obtain a first judgment result; judging whether a second time interval between the process starting time of each acquisition assembly and the corresponding acquisition file deployment is greater than a second preset threshold value or not to obtain a second judgment result; and determining that the survivability of the acquisition component is abnormal according to a first judgment result and/or a second judgment result, wherein the first judgment result indicates that the first time interval is greater than the first preset threshold, and the second judgment result indicates that the second time interval is greater than the second preset threshold.
In an exemplary embodiment, the collection component management system 200 may further include a listening module configured to: monitoring the operation process of each acquisition component; if an operation error occurs in the operation process of one acquisition component, determining an error code corresponding to the acquisition component according to the operation error; and reporting the error code to a monitoring system so that the monitoring system carries out alarm operation according to the error code.
In an exemplary embodiment, the collection component management system 200 may further include a configuration module configured to: acquiring a plurality of operation errors of the plurality of acquisition components in the operation process in advance; classifying the plurality of operating errors to obtain a plurality of error classifications; and configuring a corresponding error code for each error classification to obtain the plurality of error codes.
Example four
Fig. 10 schematically shows a hardware architecture diagram of a computer device suitable for implementing the acquisition component management method according to a fourth embodiment of the present application. In the present embodiment, the computer device 20 is a device capable of automatically performing numerical calculation and/or information processing in accordance with a command set or stored in advance. For example, the server may be a workstation, a rack server, a blade server, a tower server, or a rack server (including an independent server or a server cluster composed of a plurality of servers). As shown in fig. 10, the computer device 20 includes at least, but is not limited to: the memory 1010, processor 1020, and network interface 1030 may be communicatively linked to each other via a system bus. Wherein:
the memory 1010 includes at least one type of computer-readable storage medium including flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), Static Random Access Memory (SRAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), Programmable Read Only Memory (PROM), magnetic memory, a magnetic disk, an optical disk, etc. In some embodiments, the storage 1010 may be an internal storage module of the computer device 20, such as a hard disk or a memory of the computer device 20. In other embodiments, the memory 1010 may be an external storage device of the computer device 20, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), or the like, provided on the computer device 20. Of course, memory 1010 may also include both internal and external memory modules of computer device 20. In this embodiment, the memory 1010 is generally used for storing an operating system and various application software installed in the computer device 20, such as program codes of the collection component management method. In addition, the memory 1010 may also be used to temporarily store various types of data that have been output or are to be output.
Processor 1020 may be, in some embodiments, a Central Processing Unit (CPU), a controller, a microcontroller, a microprocessor, or other data Processing chip. The processor 1020 is generally configured to control the overall operation of the computer device 20, such as performing control and processing related to data interaction or communication with the computer device 20. In this embodiment, the processor 1020 is configured to execute program codes stored in the memory 1010 or process data.
The network interface 1030 may comprise a wireless network interface or a wired network interface, with the network interface 1030 typically being used to establish communications links between the computer device 20 and other computer devices. For example, the network interface 1030 is used to connect the computer device 20 with an external terminal via a network, establish a data transmission channel and a communication link between the computer device 20 and the external terminal, and the like. The network may be a wireless or wired network such as an Intranet (Intranet), the Internet (Internet), a Global System of Mobile communication (GSM), Wideband Code Division Multiple Access (WCDMA), a 4G network, a 5G network, Bluetooth (Bluetooth), or Wi-Fi.
It should be noted that FIG. 10 only shows a computer device having components 1010 and 1030, but it should be understood that not all of the shown components are required and that more or fewer components may be implemented instead.
In this embodiment, the collection component management method stored in the memory 1010 may be further divided into one or more program modules and executed by one or more processors (in this embodiment, the processor 1020) to complete the present invention.
EXAMPLE five
The present embodiment also provides a computer-readable storage medium having stored thereon a computer program, which when executed by a processor, implements the steps of the acquisition component management method in the embodiments.
In this embodiment, the computer-readable storage medium includes a flash memory, a hard disk, a multimedia card, a card type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Programmable Read Only Memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. In some embodiments, the computer readable storage medium may be an internal storage unit of the computer device, such as a hard disk or a memory of the computer device. In other embodiments, the computer readable storage medium may be an external storage device of the computer device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like provided on the computer device. Of course, the computer-readable storage medium may also include both internal and external storage devices of the computer device. In this embodiment, the computer-readable storage medium is generally used for storing an operating system and various types of application software installed in the computer device, for example, the program code of the acquisition component management method in the embodiment, and the like. Further, the computer-readable storage medium may also be used to temporarily store various types of data that have been output or are to be output.
It will be apparent to those skilled in the art that the modules or steps of the embodiments of the present invention described above may be implemented by a general purpose computing device, may be integrated into a single computing device or distributed across a network of multiple computing devices, and may alternatively be implemented by program code executable by a computing device, such that the steps shown or described may be executed by a computing device stored in a storage device and, in some cases, may be executed out of order from that shown or described, or separately fabricated into individual circuit modules, or fabricated into a single circuit module from multiple modules or steps of the same. Thus, embodiments of the invention are not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. An acquisition component management method, the method comprising:
acquiring an acquisition component list, wherein the acquisition component list comprises a plurality of acquisition component information of a plurality of acquisition components, and each acquisition component information comprises one or more dimension information of the corresponding acquisition component;
determining a plurality of acquisition components to be selected from the acquisition component list according to a preset dimension;
selecting a plurality of acquisition components to be upgraded from the plurality of acquisition components to be selected according to a preset release ratio; and
and upgrading the acquisition assemblies to be upgraded to obtain a plurality of upgraded acquisition assemblies.
2. The acquisition component management method according to claim 1, further comprising:
and generating the acquisition component list according to acquisition component information of a registration center, wherein the registration center is used for acquisition component registration and acquisition component information storage.
3. The acquisition component management method according to claim 1, further comprising:
acquiring acquisition component information corresponding to the plurality of updated acquisition components; and
and updating the acquisition component information corresponding to each updated acquisition component to the acquisition component list.
4. The acquisition component management method according to claim 1, further comprising:
performing survivability anomaly detection on each acquisition assembly to determine whether an anomalous acquisition assembly exists; and
and if the abnormal acquisition component exists, generating corresponding abnormal alarm information according to the abnormal acquisition component.
5. The collection component management method of claim 4, wherein the performing survivability anomaly detection on each collection component to determine whether there is an anomalous collection component comprises:
acquiring the process starting time of each acquisition assembly, the corresponding operating system starting time and the corresponding acquisition file deployment time;
judging whether a first time interval between the process starting time of each acquisition assembly and the corresponding operating system starting time is greater than a first preset threshold value or not to obtain a first judgment result;
judging whether a second time interval between the process starting time of each acquisition assembly and the corresponding acquisition file deployment is greater than a second preset threshold value or not to obtain a second judgment result; and
and determining the acquisition assembly with abnormal survivability according to a first judgment result and/or a second judgment result, wherein the first judgment result indicates that the first time interval is greater than the first preset threshold, and the second judgment result indicates that the second time interval is greater than the second preset threshold.
6. The collection component management method according to any one of claims 1 to 4, further comprising:
monitoring the operation process of each acquisition component;
if an operation error occurs in the operation process of one acquisition component, determining an error code corresponding to the acquisition component according to the operation error; and
and reporting the error code to a monitoring system so that the monitoring system carries out alarm operation according to the error code.
7. The acquisition component management method according to claim 6, further comprising the step of pre-configuring a plurality of error codes:
acquiring a plurality of operation errors of the plurality of acquisition components in the operation process in advance;
classifying the plurality of operating errors to obtain a plurality of error classifications; and
configuring a corresponding error code for each error classification to obtain the plurality of error codes.
8. An acquisition component management system, comprising:
the acquisition module is used for acquiring an acquisition component list, wherein the acquisition component list comprises a plurality of acquisition component information of a plurality of acquisition components, and each acquisition component information comprises one or more dimension information of the corresponding acquisition component;
the determining module is used for determining a plurality of acquisition components to be selected from the acquisition component list according to a preset dimension;
the selection module is used for selecting a plurality of acquisition components to be upgraded from the plurality of acquisition components to be selected according to a preset release ratio; and
and the upgrading module is used for upgrading the acquisition components to be upgraded to obtain a plurality of upgraded acquisition components.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor, when executing the computer program, is adapted to carry out the steps of the acquisition component management method according to any one of claims 1 to 7.
10. A computer-readable storage medium, in which a computer program is stored which is executable by at least one processor for causing the at least one processor to carry out the steps of the acquisition component management method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010814182.1A CN112416385A (en) | 2020-08-13 | 2020-08-13 | Acquisition component management method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010814182.1A CN112416385A (en) | 2020-08-13 | 2020-08-13 | Acquisition component management method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112416385A true CN112416385A (en) | 2021-02-26 |
Family
ID=74853942
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010814182.1A Pending CN112416385A (en) | 2020-08-13 | 2020-08-13 | Acquisition component management method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112416385A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113326052A (en) * | 2021-05-11 | 2021-08-31 | 华锐分布式(北京)技术有限公司 | Method and device for upgrading service component, computer equipment and storage medium |
| CN116302847A (en) * | 2023-05-19 | 2023-06-23 | 智慧眼科技股份有限公司 | Dynamic acquisition method and device of abnormal information, computer equipment and medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105376085A (en) * | 2014-08-27 | 2016-03-02 | 中兴通讯股份有限公司 | Method, device and system for upgrading data collection agent |
| US20160364456A1 (en) * | 2015-06-09 | 2016-12-15 | Honeywell International Inc. | Computerized process safety management system |
| CN106776212A (en) * | 2016-12-09 | 2017-05-31 | 中电科华云信息技术有限公司 | The supervisory systems and method of container clustered deploy(ment) multi-process application |
| CN106776243A (en) * | 2016-12-30 | 2017-05-31 | 中国银联股份有限公司 | A kind of monitoring method and device for monitoring software |
| CN107659458A (en) * | 2017-11-02 | 2018-02-02 | 广东亿迅科技有限公司 | Agent deployment upgrade methods and system based on git Version Controls |
| CN109739527A (en) * | 2018-11-20 | 2019-05-10 | 北京奇艺世纪科技有限公司 | A kind of method, apparatus, server and the storage medium of the publication of client gray scale |
| CN111355795A (en) * | 2020-02-26 | 2020-06-30 | 北京思特奇信息技术股份有限公司 | Method, system, medium and equipment for remotely acquiring Linux host data |
-
2020
- 2020-08-13 CN CN202010814182.1A patent/CN112416385A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105376085A (en) * | 2014-08-27 | 2016-03-02 | 中兴通讯股份有限公司 | Method, device and system for upgrading data collection agent |
| US20160364456A1 (en) * | 2015-06-09 | 2016-12-15 | Honeywell International Inc. | Computerized process safety management system |
| CN106776212A (en) * | 2016-12-09 | 2017-05-31 | 中电科华云信息技术有限公司 | The supervisory systems and method of container clustered deploy(ment) multi-process application |
| CN106776243A (en) * | 2016-12-30 | 2017-05-31 | 中国银联股份有限公司 | A kind of monitoring method and device for monitoring software |
| CN107659458A (en) * | 2017-11-02 | 2018-02-02 | 广东亿迅科技有限公司 | Agent deployment upgrade methods and system based on git Version Controls |
| CN109739527A (en) * | 2018-11-20 | 2019-05-10 | 北京奇艺世纪科技有限公司 | A kind of method, apparatus, server and the storage medium of the publication of client gray scale |
| CN111355795A (en) * | 2020-02-26 | 2020-06-30 | 北京思特奇信息技术股份有限公司 | Method, system, medium and equipment for remotely acquiring Linux host data |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113326052A (en) * | 2021-05-11 | 2021-08-31 | 华锐分布式(北京)技术有限公司 | Method and device for upgrading service component, computer equipment and storage medium |
| CN116302847A (en) * | 2023-05-19 | 2023-06-23 | 智慧眼科技股份有限公司 | Dynamic acquisition method and device of abnormal information, computer equipment and medium |
| CN116302847B (en) * | 2023-05-19 | 2023-08-04 | 智慧眼科技股份有限公司 | Dynamic acquisition method and device of abnormal information, computer equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109032824B (en) | Database verification method, database verification device, computer equipment and storage medium | |
| CN111831548B (en) | Dependency relationship topological graph drawing method and device | |
| CN112039900B (en) | Network security risk detection method, system, computer device and storage medium | |
| CN110222535B (en) | Processing device, method and storage medium for block chain configuration file | |
| CN112506755B (en) | Log acquisition method, device, computer equipment and storage medium | |
| CN111343267B (en) | Configuration management method and system | |
| CN112380170B (en) | File updating operation association method and device and computer equipment | |
| CN112416385A (en) | Acquisition component management method and system | |
| CN115543429A (en) | Project environment building method, electronic equipment and computer readable storage medium | |
| CN112685275B (en) | Algorithm policy search method and device, electronic equipment and storage medium | |
| CN106855888B (en) | Log monitoring system based on Logstash distributed system | |
| CN110069382B (en) | Software monitoring method, server, terminal device, computer device and medium | |
| CN116149941A (en) | Monitoring method and device of server component, server and storage medium | |
| CN113760608B (en) | Data recovery method and device, electronic equipment and storage medium | |
| CN113297583B (en) | Vulnerability risk analysis method, device, equipment and storage medium | |
| CN109814911A (en) | Method, apparatus, computer equipment and storage medium for Manage Scripts program | |
| CN112583825B (en) | Method and device for detecting abnormality of industrial system | |
| CN112527780B (en) | Redis cluster creation and management method, system, computer equipment and storage medium | |
| CN112416698B (en) | Expansion method and device of monitoring system, storage medium and electronic equipment | |
| CN113656378A (en) | Server management method, device and medium | |
| CN114650218A (en) | Data acquisition method, equipment, system and storage medium | |
| CN112882856A (en) | System maintenance method, apparatus and computer-readable storage medium | |
| CN111984484A (en) | Non-invasive micro-service access method and system | |
| CN111274219A (en) | Data storage method and device, storage medium and electronic device | |
| CN110825406A (en) | Software upgrading method and related equipment |
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 |