WO2019237538A1 - 一种监控实例的配置方法、服务器及计算机可读存储介质 - Google Patents

一种监控实例的配置方法、服务器及计算机可读存储介质 Download PDF

Info

Publication number
WO2019237538A1
WO2019237538A1 PCT/CN2018/105528 CN2018105528W WO2019237538A1 WO 2019237538 A1 WO2019237538 A1 WO 2019237538A1 CN 2018105528 W CN2018105528 W CN 2018105528W WO 2019237538 A1 WO2019237538 A1 WO 2019237538A1
Authority
WO
WIPO (PCT)
Prior art keywords
configuration content
item
terminal
monitoring instance
original configuration
Prior art date
Application number
PCT/CN2018/105528
Other languages
English (en)
French (fr)
Inventor
林水明
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2019237538A1 publication Critical patent/WO2019237538A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3438—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment monitoring of user actions

Definitions

  • the present application belongs to the field of computer technology, and in particular, relates to a method for configuring a monitoring instance, a server, and a computer-readable storage medium.
  • the monitoring system is the most important part of the entire operation and maintenance link, and even the entire product life cycle. It can comprehensively monitor objects such as servers, databases, applications, etc., and can provide early warning and fault detection in advance, and provide detailed monitoring data afterwards. To track down problems.
  • a monitoring instance corresponding to the monitoring object needs to be created and configured in the monitoring system.
  • the monitoring system requires that the configuration content of certain items to be configured in the monitoring instance must be globally unique, such as monitoring Instance name, alarm contact name, etc.
  • the existing monitoring system cannot distinguish the configuration content set by different users for these items to be configured.
  • multiple users will restrict each other on the settings of these items to be configured For example, if a user sets the alarm contact name of a monitoring instance to Zhang San, other users can no longer use the name of Zhang San as the alarm contact name, which will narrow the setting range of the configuration content of the item to be configured, and give Great user inconvenience.
  • the embodiments of the present application provide a configuration method, server, and computer-readable storage medium for a monitoring instance, so as to solve the existing monitoring system that will cause different users to restrict each other on the settings of the same items to be configured, and reduce the configuration to be
  • the setting range of the configuration content of the item brings great inconvenience to the user.
  • a first aspect of the embodiments of the present application provides a method for configuring a monitoring instance, including:
  • the original configuration content of the to-be-configured item is identified based on the unique identification, and the original configuration content after the identity tag is determined as the final configuration content of the to-be-configured item.
  • a second aspect of the embodiments of the present application provides a server including a memory, a processor, and computer-readable instructions stored in the memory and executable on the processor, where the processor executes the computer-readable The following steps are implemented when the instruction is read:
  • the original configuration content of the to-be-configured item is identified based on the unique identification, and the original configuration content after the identity tag is determined as the final configuration content of the to-be-configured item.
  • a third aspect of the embodiments of the present application provides a computer-readable storage medium.
  • the computer-readable storage medium stores computer-readable instructions. When the computer-readable instructions are executed by a processor, the following steps are implemented:
  • the original configuration content of the to-be-configured item is identified based on the unique identification, and the original configuration content after the identity tag is determined as the final configuration content of the to-be-configured item.
  • the configuration content set by the user for the item to be configured of the monitoring instance is identified, so that The unique identity of the user, which distinguishes the configuration content set by different users for the same to-be-configured item, so that different users will not restrict each other in the setting of the configuration content of the same to-be-configured item, that is, different users will configure the same to-be-configured item.
  • the configuration content set by the items can be the same, which expands the setting range of the configuration content of the item to be configured.
  • FIG. 1 is an implementation flowchart of a method for configuring a monitoring instance according to an embodiment of the present application
  • FIG. 2 is a flowchart of implementing S12 in a method for configuring a monitoring instance according to an embodiment of the present application
  • FIG. 3 is a flowchart of implementing S15 in a method for configuring a monitoring instance according to an embodiment of the present application
  • FIG. 4 is a structural block diagram of a server according to an embodiment of the present application.
  • FIG. 5 is a structural block diagram of a server according to another embodiment of the present application.
  • FIG. 1 is an implementation flowchart of a method for configuring a monitoring instance according to an embodiment of the present application.
  • the execution subject of the configuration method of the monitoring instance is a server in the monitoring system.
  • the monitoring system also includes a monitoring program (ie, a client) deployed on the user terminal.
  • the monitoring program is used to monitor the monitoring object and feedback the monitoring data to the server.
  • the monitoring object is an objective physical object, including, but not limited to, a terminal, a database, and an application program. Terminals include, but are not limited to, computers and mobile phones.
  • the configuration method of the monitoring instance shown in FIG. 1 includes the following steps:
  • the terminal may be any terminal of any user authorized to use the monitoring system.
  • users when users use the monitoring system, they need to apply to the server in the monitoring system to register a user account.
  • the user can enter the account registration interface of the monitoring system through the terminal to perform account registration.
  • the server will verify the identity of the user based on the basic information filled in by the user to check whether it can be authorized to use the monitoring system. For example, the server can check whether the user is a paid user based on the company name filled in by the user, and if so, determine that it can be authorized to use the monitoring system.
  • the server assigns a user account to the user and the user is authorized to use the monitoring system.
  • the server will also assign a unique identity to the user. The unique identity is globally unique in the entire monitoring system, that is, the unique identity assigned by the server to different users is different.
  • the monitoring instance refers to a virtual instance created in the monitoring system for identifying a monitoring object.
  • the type identifier of the monitoring instance may be a type name of the monitoring instance.
  • the server can use its name "database" as its monitoring instance type identifier.
  • the server may number the types of the monitoring instances it defines, and use the type numbers of the monitoring instances as the type identifiers of the monitoring instances.
  • the terminal generates a monitoring instance creation request based on the monitoring instance type selected by the user, and sends the monitoring instance creation request to the server.
  • the monitoring instance creation request carries a monitoring instance type identifier.
  • the server When the server receives the monitoring instance creation request sent by the terminal, it extracts the monitoring instance type identifier from the monitoring instance creation request.
  • S12 Determine the unique identity of the user to which the terminal belongs.
  • the server when the server receives the monitoring instance creation request sent by a terminal, it also determines the unique identity of the user to which the terminal that sent the monitoring instance creation request belongs.
  • the terminal can send a monitoring instance creation request to the server through the terminal.
  • a monitoring instance creation request to the server through the terminal.
  • users can log in to their registered accounts through multiple different terminals to enter the monitoring system, and then send monitoring instance creation requests to the server through different terminals.
  • the user after the user selects the type of monitoring instance that he wants to create in the monitoring instance creation request interface, the user also needs to enter a unique identity assigned by the server, and the terminal recognizes the unique identity entered by the user as belonging to the user. The user's unique identity.
  • the terminal generates a monitoring instance creation request based on the type of monitoring instance selected by the user and the unique identity of the user to which the terminal belongs.
  • the monitoring instance creation request carries the monitoring instance type identifier and the unique identity of the user to which the terminal that sent the monitoring instance creation request belongs. Based on this, S12 may specifically include the following steps:
  • the server when the server receives a monitoring instance creation request sent by a terminal, it also extracts the user ’s unique identity from the monitoring instance creation request, and determines the extracted unique identity as the one carried in the monitoring instance creation request. The unique identity of the user to which the terminal belongs.
  • the server determines the terminal as a terminal belonging to the user, assigns a terminal identifier to the terminal, and assigns the terminal to the terminal.
  • the identification is sent to the terminal so that the terminal stores the terminal identification assigned to it.
  • the server establishes a correspondence between the terminal identity of the terminal and the unique identity of the user to which the terminal belongs. It should be noted that the terminal identifiers assigned by the server to different terminals of different users are different, that is, the terminal identifier of each terminal is also globally unique in the entire monitoring system.
  • the terminal identifier can be a universally unique identifier (Universally Unique Identifier (UUID). It can be understood that, since a user will log in to his registered user account on at least one terminal, the unique identity of each user corresponds to at least one terminal identity.
  • UUID Universally Unique Identifier
  • the terminal After the user selects the type of monitoring instance he wants to create on the monitoring instance creation request interface, the terminal generates a monitoring instance creation request based on the type of monitoring instance selected by the user and the terminal identifier.
  • the monitoring instance creation request carries a monitoring instance type identifier and a terminal identifier.
  • S12 can be specifically implemented through S121 ⁇ S123 as shown in Figure 2, as follows:
  • S122 Determine the unique identity of the user corresponding to the terminal identity based on a preset correspondence between the terminal identity and the unique identity of the user.
  • S123 Determine the unique identity of the user corresponding to the terminal identity as the unique identity of the user to which the terminal belongs.
  • the server when the server receives the monitoring instance creation request sent by the terminal, the server also extracts the terminal identifier from the monitoring instance creation request, and determines the extraction based on the preset correspondence between the terminal identifier and the user's unique identity.
  • the unique identity of the user corresponding to the terminal identity of the user, and the unique identity of the user corresponding to the extracted terminal identity is determined as the unique identity of the user to which the terminal carried in the monitoring instance creation request is sent.
  • S13 Create a monitoring instance based on the monitoring instance template corresponding to the monitoring instance type identifier, and send the items to be configured in the monitoring instance to the terminal, so that the terminal obtains and returns the user to the items to be configured Set the original configuration content.
  • the developer after defining a plurality of different types of monitoring instances, the developer also configures a monitoring instance template for each type of monitoring instance, and the monitoring instance template defines some to-be-configured items of the monitoring instance.
  • Items to be configured for a monitoring instance refer to some basic information items that need to be configured after the monitoring instance is created.
  • the items to be configured for a monitoring instance can include but are not limited to the monitoring instance name, alarm contact name, alarm contact group name, alarm template, etc.
  • the monitoring instance templates for different types of monitoring instances can be the same or different, depending on the actual situation. Requirement setting, there is no restriction here.
  • the server establishes a correspondence between the monitoring instance type identifier and the monitoring instance template of each type of monitoring instance.
  • the server After the server extracts the monitoring instance type identifier from the monitoring instance creation request, it determines the monitoring instance template corresponding to the extracted monitoring instance type identifier based on the preset correspondence between the monitoring instance type identifier and the monitoring instance template, and based on the monitoring The instance template creates a monitoring instance. For example, if the monitoring instance type identifier extracted by the server from the monitoring instance creation request is used to identify the monitoring instance of the database type, the server creates a monitoring instance based on the monitoring instance template corresponding to the monitoring instance of the database type, that is, the newly created
  • the monitoring object corresponding to the monitoring instance is a database.
  • the newly created monitoring instance includes at least one item to be configured that requires users to set configuration content.
  • the server sends the items to be configured in the newly created monitoring instance to the terminal.
  • the terminal displays the configuration to be configured in the newly created monitoring instance, so that the user can set the configuration content for each configuration item to be configured.
  • the terminal obtains the original configuration content set by the user for each item to be configured, and sends the original configuration content set by the user for each item to be configured to the server.
  • the server receives the original configuration content set by the user for each item to be configured in the newly created monitoring instance.
  • the original configuration content set by the user for each item to be configured refers to the content entered by the user for each item to be configured. For example, if the content entered by the user for the to-be-configured item of the monitoring instance name is "first database", the terminal recognizes the "first database" as the original configuration content set by the user for the to-be-configured item of the monitoring instance name.
  • S15 Mark the original configuration content of the item to be configured based on the unique identification, and determine the original configuration content after the identity marking as the final configuration content of the item to be configured.
  • the server after the server obtains the original configuration content set by the user for the item to be configured in the newly created monitoring instance, based on the user's unique identity, the server initially configures the item to be configured in the newly created monitoring instance.
  • the content is identity-labeled, and the original configuration content of the to-be-configured item after the identity-tag is determined as the final configuration content of the corresponding to-be-configured item.
  • S15 may specifically include the following steps:
  • the unique identification is combined with the original configuration content of the item to be configured to obtain the final configuration content of the item to be configured.
  • the server may combine the unique identification of the user with the original configuration content of the item to be configured based on a preset string combination manner, and determine the combined content as the final configuration content of the item to be configured.
  • the preset combination of strings can be set according to actual requirements, and there is no limitation here.
  • the preset combination of strings may be: adding the unique identity of the user before the original configuration content of the item to be configured to obtain the combined content.
  • the server adds "abdae” before “Zhang San” and obtains " “abdae Zhang San”, with "abdae Zhang San” as the final configuration content of the alarm contact name to be configured.
  • the method for configuring a monitoring instance determines the unique identity of the user to which the terminal that sent the monitoring instance creation request belongs, and based on the user's unique identity, The configured configuration content is identified.
  • the server can be based on the user ’s Unique identification, distinguishing the configuration content set by different users for the same to-be-configured item in the same type of monitoring instance, so that different users will not restrict each other in the setting of the configuration content of the same to-be-configured item, that is, different
  • the configuration content set by the user for the same to-be-configured item can be the same, which expands the setting range of the configuration content of the to-be-configured item.
  • FIG. 3 is a flowchart of a specific implementation of S15 in a method for configuring a monitoring instance provided by an embodiment of the present application.
  • S15 specifically includes S151 to S153, which are detailed as follows:
  • the developer after the developer defines the items to be configured for each monitoring instance template, the developer also needs to add attribute information for each item to be configured.
  • the server may store attribute information of all items to be configured in each monitoring instance template in an attribute information table of the monitoring instance template.
  • the attribute information of the item to be configured is used to identify whether the configuration content of the item to be configured is globally unique. Globally unique means unique in the entire monitoring system.
  • the attribute information of the item to be configured may be represented by “0” or “1”, where “0” indicates that the configuration content of the item to be configured does not have global uniqueness, and “1” indicates that the configuration content of the item to be configured has Global uniqueness.
  • the developer can set their attribute information to "1"
  • the developer can set its attribute information to "0".
  • the server may obtain attribute information of each item to be configured in the newly created monitoring instance from the attribute information table of the monitoring instance template corresponding to the extracted monitoring instance type identifier.
  • S152 Determine a target to-be-configured item from the to-be-configured items based on the attribute information of the to-be-configured items.
  • the server determines a target to-be-configured item from each to-be-configured item in the newly-created monitoring instance based on attribute information of each to-be-configured item in the newly-created monitoring instance.
  • the attribute information of the target item to be configured is used to identify that the configuration content of the target item to be configured is globally unique.
  • the server determines the target to-be-configured item from each to-be-configured item in the newly-created monitoring instance based on the property information of each to-be-configured item in the newly-created monitoring instance, which may specifically include: the server detects the property information of each to-be-configured item If the attribute information of a to-be-configured item is detected to identify that the configuration content of the to-be-configured item is globally unique, the to-be-configured item is determined as the target to-be-configured item.
  • the server determines the to-be-configured item as the target to-be-configured item.
  • S153 Mark the original configuration content of the target to be configured based on the unique identification, and determine the original configuration content after the identification is the final configuration content of the target configuration item.
  • the server marks the original configuration content of the target to-be-configured item based on the user's unique identification, and determines the original configuration content of the target to-be-configured item after identity identification as Its final configuration content.
  • the method for configuring a monitoring instance may further include the following steps:
  • the original configuration content of the remaining to-be-configured items except the target to-be-configured item among the to-be-configured items is determined as its final configuration content.
  • the server does not process the original configuration content of the remaining to-be-configured items except the target to-be-configured items in the newly created monitoring instance to-be-configured items, and directly
  • the original configuration content of the item to be configured is determined as the final configuration content of the corresponding item to be configured.
  • the configuration method of a monitoring instance only identifies the original configuration content of the target to-be-configured item that requires global uniqueness of the configuration content, but not the configuration content that does not require global uniqueness.
  • the original configuration content of the items to be configured is not processed, thereby improving the configuration efficiency of the monitoring instance.
  • FIG. 4 is a structural block diagram of a server according to an embodiment of the present application, and each unit included in the server is configured to execute steps in the embodiments corresponding to FIG. 1 to FIG. 3.
  • the server 400 includes: a first extraction unit 41, a first determination unit 42, a sending unit 43, a receiving unit 44, and a marking unit 45. among them:
  • the first extraction unit 41 is configured to, if a monitoring instance creation request sent by the terminal is received, extract a monitoring instance type identifier carried in the monitoring instance creation request.
  • the first determining unit 42 is configured to determine a unique identity of a user to which the terminal belongs.
  • the sending unit 43 is configured to create a monitoring instance based on a monitoring instance template corresponding to the monitoring instance type identifier, and send a to-be-configured item in the monitoring instance to the terminal, so that the terminal acquires and returns a user to the target The original configuration content of the item to be configured.
  • the receiving unit 44 is configured to receive the original configuration content of the item to be configured returned by the terminal.
  • the marking unit 45 is configured to mark the original configuration content of the item to be configured based on the unique identification, and determine the original configuration content after the identification mark as the final configuration content of the item to be configured.
  • the marking unit 45 is specifically configured to:
  • the unique identification is combined with the original configuration content of the item to be configured to obtain the final configuration content of the item to be configured.
  • the marking unit 45 includes a first obtaining unit, a second determining unit, and a third determining unit. among them:
  • the first obtaining unit is configured to obtain attribute information of the item to be configured.
  • the second determining unit is configured to determine a target to-be-configured item from the to-be-configured items based on the attribute information of the to-be-configured items.
  • the determining unit is configured to mark the original configuration content of the target to be configured based on the unique identification, and determine the original configuration content after the identification is marked as the final configuration content of the target configuration item.
  • the server 400 further includes a fourth determining unit.
  • the fourth determining unit is configured to determine the original configuration content of the remaining items to be configured except the target item to be configured as its final configuration content.
  • the first determination unit 42 includes: a second extraction unit, a fifth determination unit, and a sixth determination unit. among them:
  • the second extraction unit is configured to extract a terminal identifier carried in the monitoring instance creation request.
  • the fifth determining unit is configured to determine a unique identity of the user corresponding to the terminal identity based on a preset correspondence between the terminal identity and the unique identity of the user.
  • the sixth determining unit is configured to determine a unique identity of a user corresponding to the terminal identity as a unique identity of a user to which the terminal belongs.
  • the server determines the configuration content set by the user for the items to be configured for the monitoring instance based on the unique identification of the user to which the terminal that sent the monitoring instance creation request belongs. Mark the identity so that even if different users set the same original configuration content for the same to-be-configured item in the same type of monitoring instance, the unique identity of different users is different, so that the server can be based on the unique identity of the user.
  • the configuration content set by the configuration item can be the same, which expands the setting range of the configuration content of the item to be configured.
  • FIG. 5 is a structural block diagram of a server according to another embodiment of the present application.
  • the server 5 of this embodiment includes a processor 50, a memory 51, and computer-readable instructions 52 stored in the memory 51 and executable on the processor 50, such as the configuration of a monitoring instance. Method of Procedure.
  • the processor 50 executes the computer-readable instructions 52, the steps in the embodiments of the configuration method of the foregoing monitoring instances are implemented, such as S11 to S15 shown in FIG. 1.
  • the processor 50 executes the computer-readable instructions 52
  • the functions of the units in the embodiment corresponding to FIG. 4 are implemented, for example, the functions of units 51 to 55 shown in FIG. 4 are described in detail. The related description in the embodiment is not repeated here.
  • the computer-readable instructions 52 may be divided into one or more units, and the one or more units are stored in the memory 51 and executed by the processor 50 to complete the present application.
  • the one or more units may be a series of computer-readable instruction instruction segments capable of performing specific functions, and the instruction segments are used to describe the execution process of the computer-readable instructions 52 in the server 5.
  • the computer-readable instructions 52 may be divided into a first extraction unit, a first determination unit, a sending unit, a receiving unit, and a marking unit, and the specific functions of each unit are as described above.
  • the server may include, but is not limited to, a processor 50 and a memory 51.
  • FIG. 5 is only an example of the server 5 and does not constitute a limitation on the server 5. It may include more or fewer components than shown in the figure, or combine some components, or different components, such as
  • the server may further include an input-output device, a network access device, a bus, and the like.
  • the processor 50 may be a central processing unit (Central Processing Unit (CPU), or other general-purpose processors, Digital Signal Processors (DSPs), and application-specific integrated circuits (Applications) Specific Integrated Circuit (ASIC), off-the-shelf Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • CPU Central Processing Unit
  • DSP Digital Signal Processor
  • ASIC Applications
  • FPGA off-the-shelf Programmable Gate Array
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the memory 51 may be an internal storage unit of the server 5, such as a hard disk or a memory of the server 5.
  • the memory 51 may also be an external storage device of the server 5, such as a plug-in hard disk, a Smart Media Card (SMC), and a Secure Digital (SD) card provided on the server 5. Flash card, etc.
  • the memory 51 may further include both an internal storage unit of the server 5 and an external storage device.
  • the memory 51 is configured to store the computer-readable instructions and other programs and data required by the server.
  • the memory 51 may also be used to temporarily store data that has been output or is to be output.

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer And Data Communications (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

一种监控实例的配置方法、服务器及计算机可读存储介质，适用于计算机技术领域，所述方法包括：若接收到终端发送的监控实例创建请求，则提取所述监控实例创建请求携带的监控实例类型标识（S11）；确定所述终端所属用户的唯一身份标识（S12）；基于与所述监控实例类型标识对应的监控实例模板创建监控实例，并将所述监控实例中的待配置项发送至所述终端（S13）；接收所述终端返回的所述待配置项的原始配置内容（S14）；基于所述唯一身份标识对所述待配置项的原始配置内容进行身份标记，将身份标记后的所述原始配置内容确定为所述待配置项的最终配置内容（S15）。本方法能够避免不同用户在同一待配置项的配置内容的设置上对彼此造成约束，扩大了待配置项的配置内容的设置范围。

Description

一种监控实例的配置方法、服务器及计算机可读存储介质
本申请申明享有2018年6月11日递交的申请号为201810592825.5、名称为“一种监控实例的配置方法、服务器及计算机可读存储介质”中国专利申请的优先权，该中国专利申请的整体内容以参考的方式结合在本申请中。
技术领域
本申请属于计算机技术领域，尤其涉及一种监控实例的配置方法、服务器及计算机可读存储介质。
 背景技术
监控系统是整个运维环节，乃至整个产品生命周期中最重要的一环，其可以对服务器、数据库、应用程序等对象进行全面的监控，可以在事前及时预警发现故障，事后提供详细的监控数据以追查定位问题。
通常，在需要对某监控对象进行监控时，需要在监控系统中创建并配置该监控对象对应的监控实例，监控系统要求监控实例的某些待配置项的配置内容必须是全局唯一的，如监控实例名称、告警联系人名称等。现有的监控系统无法对不同用户针对这些待配置项所设置的配置内容进行区分，这样，当多个用户共用该监控系统时，多个用户在这些待配置项的设置上会对彼此造成约束，例如，若某用户将某监控实例的告警联系人名称设置为张三，则其他用户无法再使用张三这个名字作为告警联系人名称，这样会缩小待配置项的配置内容的设置范围，给用户带来极大不便。
 技术问题
本申请实施例提供了一种监控实例的配置方法、服务器及计算机可读存储介质，以解决现有的监控系统会导致不同用户在相同待配置项的设置上对彼此造成约束，缩小了待配置项的配置内容的设置范围，给用户带来极大不便的问题。
 技术解决方案
本申请实施例的第一方面提供了一种监控实例的配置方法，包括：
若接收到终端发送的监控实例创建请求，则提取所述监控实例创建请求携带的监控实例类型标识；
确定所述终端所属用户的唯一身份标识；
基于与所述监控实例类型标识对应的监控实例模板创建监控实例，并将所述监控实例中的待配置项发送至所述终端，使所述终端获取并返回用户针对所述待配置项设置的原始配置内容；
接收所述终端返回的所述待配置项的原始配置内容；
基于所述唯一身份标识对所述待配置项的原始配置内容进行身份标记，将身份标记后的所述原始配置内容确定为所述待配置项的最终配置内容。
本申请实施例的第二方面提供了一种服务器，包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机可读指令，所述处理器执行所述计算机可读指令时实现以下各步骤：
若接收到终端发送的监控实例创建请求，则提取所述监控实例创建请求携带的监控实例类型标识；
确定所述终端所属用户的唯一身份标识；
基于与所述监控实例类型标识对应的监控实例模板创建监控实例，并将所述监控实例中的待配置项发送至所述终端，使所述终端获取并返回用户针对所述待配置项设置的原始配置内容；
接收所述终端返回的所述待配置项的原始配置内容；
基于所述唯一身份标识对所述待配置项的原始配置内容进行身份标记，将身份标记后的所述原始配置内容确定为所述待配置项的最终配置内容。
本申请实施例的第三方面提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机可读指令，所述计算机可读指令被处理器执行时实现以下各步骤：
若接收到终端发送的监控实例创建请求，则提取所述监控实例创建请求携带的监控实例类型标识；
确定所述终端所属用户的唯一身份标识；
基于与所述监控实例类型标识对应的监控实例模板创建监控实例，并将所述监控实例中的待配置项发送至所述终端，使所述终端获取并返回用户针对所述待配置项设置的原始配置内容；
接收所述终端返回的所述待配置项的原始配置内容；
基于所述唯一身份标识对所述待配置项的原始配置内容进行身份标记，将身份标记后的所述原始配置内容确定为所述待配置项的最终配置内容。
 有益效果
本申请实施例中，通过确定发送监控实例创建请求的终端所属用户的唯一身份标识，基于用户的唯一身份标识，对用户针对监控实例的待配置项所设置的配置内容进行身份标记，从而能够基于用户的唯一身份标识，对不同用户针对同一待配置项所设置的配置内容进行区分，使得不同用户在同一待配置项的配置内容的设置上不会对彼此造成约束，即不同用户对同一待配置项所设置的配置内容可以相同，扩大了待配置项的配置内容的设置范围。
 附图说明
图1是本申请实施例提供的一种监控实例的配置方法的实现流程图；
图2是本申请实施例提供的一种监控实例的配置方法中S12的实现流程图；
图3是本申请实施例提供的一种监控实例的配置方法中S15的实现流程图；
图4是本申请实施例提供的一种服务器的结构框图；
图5是本申请另一实施例提供的一种服务器的结构框图。
 本发明的实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
请参阅图1，图1是本申请实施例提供的一种监控实例的配置方法的实现流程图。本实施例中，监控实例的配置方法的执行主体为监控系统中的服务器。需要说明的是，监控系统除了包括服务器外，还包括部署于用户终端上的监控程序（即客户端）。监控程序用于对监控对象进行监控，并将监控数据反馈给服务器。其中，监控对象是客观存在的实体对象，包括但不限于终端、数据库、应用程序等。终端包括但不限于电脑、手机等。
如图1所示的监控实例的配置方法包括以下步骤：
S11：若接收到终端发送的监控实例创建请求，则提取所述监控实例创建请求携带的监控实例类型标识。
在本实施例中，终端可以是任一被授权使用监控系统的用户的任一终端。在实际应用中，用户在使用监控系统时，需要先向监控系统中的服务器申请注册用户账号。具体的，用户可以通过终端进入监控系统的账号注册界面进行账号注册，在注册用户账号时，服务器会根据用户填写的基本信息对用户进行身份校验，以检验其是否能够被授权使用监控系统。例如，服务器可以根据用户填写的公司名称检验其是否是已付费用户，若是，则确定其能够被授权使用监控系统，此时，服务器为用户分配用户账号，该用户即被授权使用监控系统。需要说明的是，在账号注册成功后，服务器还会为用户分配一个唯一身份标识，该唯一身份标识在整个监控系统中是全局唯一的，即服务器为不同用户分配的唯一身份标识不同。
当用户想要对某一监控对象进行监控时，需要在监控系统中创建该监控对象对应的监控实例。其中，监控实例指在监控系统中创建的用于对监控对象进行标识的虚拟实例。可以理解的是，开发人员可以在服务器中预先定义多种不同类型的监控实例，并为每种类型的监控实例配置监控实例类型标识。作为本申请一实施例，监控实例类型标识可以是监控实例的类型名称。例如，对于数据库这一类型的监控实例，服务器可以将其名称“数据库”作为其监控实例类型标识。作为本申请另一实施例，服务器可以对其定义的监控实例的类型进行编号，并将监控实例的类型编号作为监控实例类型标识。
用户可以在监控对象所在的终端上登录其注册的用户账号，进而进入监控系统，并在监控系统的监控实例创建请求界面选择其想要创建的监控实例类型。终端基于用户选择的监控实例类型生成监控实例创建请求，并将该监控实例创建请求发送至服务器。其中，监控实例创建请求中携带监控实例类型标识。
服务器接收到终端发送的监控实例创建请求时，从监控实例创建请求中提取监控实例类型标识。
S12：确定所述终端所属用户的唯一身份标识。
在本实施例中，服务器接收到某终端发送的监控实例创建请求时，还确定发送监控实例创建请求的终端所属用户的唯一身份标识。
在实际应用中，当用户想要对某终端或部署于某终端上的数据库、应用程序等监控对象进行监控时，可以通过该终端向服务器发送监控实例创建请求。可以理解的是，当监控对象部署在多个不同终端上时，用户可以分别通过多个不同的终端登录其注册的帐号进入监控系统，进而通过不同的终端分别向服务器发送监控实例创建请求。
作为本申请一实施例，用户在监控实例创建请求界面选择了其想要创建的监控实例类型后，还需要输入服务器为其分配的唯一身份标识，终端将用户输入的唯一身份标识识别为其所属用户的唯一身份标识。终端基于用户选择的监控实例类型及终端所属用户的唯一身份标识生成监控实例创建请求。其中，该监控实例创建请求中携带监控实例类型标识和发送该监控实例创建请求的终端所属用户的唯一身份标识。基于此，S12具体可以包括以下步骤：
提取所述监控实例创建请求携带的用户的唯一身份标识，将提取出的所述唯一身份标识确定为所述终端所属用户的唯一身份标识。
在本实施例中，服务器接收到某终端发送的监控实例创建请求时，还从监控实例创建请求中提取用户的唯一身份标识，并将提取出的唯一身份标识确定为发送监控实例创建请求携带的终端所属用户的唯一身份标识。
作为本申请另一实施例，当用户在某终端上首次登录其注册的用户帐号进入监控系统时，服务器会将该终端确定为属于该用户的终端，并为该终端分配终端标识，且将终端标识发送至该终端，以使该终端对为其分配的终端标识进行存储。同时，服务器将该终端的终端标识与该终端所属用户的唯一身份标识建立对应关系。需要说明的是，服务器为不同用户的不同终端所分配的终端标识不同，即每个终端的终端标识在整个监控系统中也是全局唯一的。在实际应用中，终端标识可以是通用唯一识别码（Universally Unique Identifier，UUID）。可以理解的是，由于一个用户会在至少一个终端上登录其注册的用户帐号，因此，每一用户的唯一身份标识均对应至少一个终端标识。
在本实施例中，用户在监控实例创建请求界面选择了其想要创建的监控实例类型后，终端基于用户选择的监控实例类型及终端标识生成监控实例创建请求。其中，该监控实例创建请求中携带监控实例类型标识和终端标识。基于此，S12具体可以通过如图2所示的S121~S123实现，详述如下：
S121：提取所述监控实例创建请求携带的终端标识。
S122：基于终端标识与用户的唯一身份标识之间的预设对应关系，确定所述终端标识对应的用户的唯一身份标识。
S123：将所述终端标识对应的用户的唯一身份标识确定为所述终端所属用户的唯一身份标识。
在本实施例中，服务器接收到终端发送的监控实例创建请求时，还从监控实例创建请求中提取终端标识，并基于终端标识与用户的唯一身份标识之间的预设对应关系，确定提取出的终端标识对应的用户的唯一身份标识，将提取出的终端标识对应的用户的唯一身份标识确定为发送监控实例创建请求携带的终端所属用户的唯一身份标识。
S13：基于与所述监控实例类型标识对应的监控实例模板创建监控实例，并将所述监控实例中的待配置项发送至所述终端，使所述终端获取并返回用户针对所述待配置项设置的原始配置内容。
在本实施例中，开发人员在定义了多种不同类型的监控实例后，还为每种类型的监控实例配置监控实例模板，监控实例模板中定义了监控实例的一些待配置项。监控实例的待配置项指监控实例在创建后需要配置的一些基础信息项。如监控实例的待配置项可以包括但不限于监控实例名称、告警联系人名称、告警联系人组名称、告警模板等，不同类型的监控实例的监控实例模板可以相同，也可以不同，具体根据实际需求设置，此处不做限制。服务器将每种类型的监控实例的监控实例类型标识和监控实例模板建立对应关系。
服务器从监控实例创建请求中提取出监控实例类型标识后，基于监控实例类型标识与监控实例模板之间的预设对应关系，确定提取出的监控实例类型标识对应的监控实例模板，并基于该监控实例模板创建监控实例。例如，若服务器从监控实例创建请求中提取出的监控实例类型标识用于标识数据库类型的监控实例，则服务器基于数据库类型的监控实例对应的监控实例模板创建监控实例，也就是说，新创建的监控实例对应的监控对象为数据库。
由于监控实例模板中定义了至少一个待配置项，因此，新创建的监控实例中包括至少一个需要用户设置配置内容的待配置项。服务器将新创建的监控实例中的待配置项发送至终端。终端将新创建的监控实例中的待配置进行显示，以使用户针对每一待配置项设置配置内容。终端获取用户针对每一待配置项设置的原始配置内容，并将用户针对每一待配置项设置的原始配置内容发送至服务器。
S14：接收所述终端返回的所述待配置项的原始配置内容。
在本实施例中，服务器将新创建的监控实例中的待配置项发送至终端后，接收终端返回的用户针对新创建的监控实例中的每一待配置项所设置的原始配置内容。其中，用户针对每一待配置项所设置的原始配置内容指用户针对每一待配置项所输入的内容。例如，若用户针对监控实例名称这一待配置项输入的内容为“第一数据库”，则终端将“第一数据库”识别为用户针对对监控实例名称这一待配置项设置的原始配置内容。
S15：基于所述唯一身份标识对所述待配置项的原始配置内容进行身份标记，将身份标记后的所述原始配置内容确定为所述待配置项的最终配置内容。
在本实施例中，服务器获取到用户针对新创建的监控实例中的待配置项所设置的原始配置内容后，基于用户的唯一身份标识，对新创建的监控实例中的待配置项的原始配置内容进行身份标记，并将身份标记后的待配置项的原始配置内容确定为相应待配置项的最终配置内容。
作为本申请一实施例，S15具体可以包括以下步骤：
基于预设的字符串组合方式，将所述唯一身份标识与所述待配置项的原始配置内容进行组合，得到所述待配置项的最终配置内容。
在本实施例中，服务器可以基于预设的字符串组合方式，将用户的唯一身份标识与待配置项的原始配置内容进行组合，将组合后的内容确定为待配置项的最终配置内容。其中，预设的字符串组合方式可以根据实际需求设置，此处不做限制。例如，预设的字符串组合方式可以为：将用户的唯一身份标识添加在待配置项的原始配置内容之前，得到组合内容。示例性的，若用户的唯一身份标识为“abdae”，告警联系人名称这一待配置项的原始配置内容为“张三”，则服务器将“abdae”添加在“张三”之前，得到“abdae张三”，将“abdae张三”作为告警联系人名称这一待配置项的最终配置内容。
以上可以看出，本实施例提供的一种监控实例的配置方法通过确定发送监控实例创建请求的终端所属用户的唯一身份标识，基于用户的唯一身份标识，对用户针对监控实例的待配置项所设置的配置内容进行身份标记，这样，即使不同用户针对同一类型的监控实例中的相同待配置项所设置的原始配置内容相同，但由于不同用户的唯一身份标识不同，从而使得服务器可以基于用户的唯一身份标识，对不同用户针对同一类型的监控实例中的相同待配置项所设置的配置内容进行区分，使得不同用户在同一待配置项的配置内容的设置上不会对彼此造成约束，即不同用户对同一待配置项所设置的配置内容可以相同，扩大了待配置项的配置内容的设置范围。
请参阅图3，图3是本申请实施例提供的一种监控实例的配置方法中S15的具体实现流程图。相对于图1对应的实施例，本实施例提供的一种监控实例的配置方法中S15具体包括S151~S153，详述如下：
S151：获取所述待配置项的属性信息。
在本实施例中，开发人员在定义了每个监控实例模板的待配置项后，还需为每个待配置项添加属性信息。服务器可以将每一监控实例模板中所有待配置项的属性信息存储在该监控实例模板的属性信息表中。其中，待配置项的属性信息用于标识该待配置项的配置内容是否具有全局唯一性。全局唯一指在整个监控系统中是独一无二的。
示例性的，待配置项的属性信息可以通过“0”或“1”表示，其中，“0”表示待配置项的配置内容不具有全局唯一性，“1”标识待配置项的配置内容具有全局唯一性。例如，对于监控实例名称、告警联系人名称、告警联系人组名称等这些要求配置内容具有全局唯一性的待配置项，开发人员可以将其属性信息均设置为“1”，而对于其他待配置项，开发人员可以将其属性信息设置为“0”。
在本实施例中，服务器可以从与提取出的监控实例类型标识对应的监控实例模板的属性信息表中获取新创建的监控实例中的各个待配置项的属性信息。
S152：基于所述待配置项的属性信息，从所述待配置项中确定目标待配置项。
服务器基于新创建的监控实例中的各个待配置项的属性信息，从新创建的监控实例中的各个待配置项中确定目标待配置项。其中，目标待配置项的属性信息用于标识目标待配置项的配置内容具有全局唯一性。
服务器基于新创建的监控实例中的各个待配置项的属性信息，从新创建的监控实例中的各个待配置项中确定目标待配置项，具体可以包括：服务器对各个待配置项的属性信息进行检测，若检测到某一待配置项的属性信息用于标识该待配置项的配置内容具有全局唯一性，则将该待配置项确定为目标待配置项。例如，若某待配置项的属性信息为“1”，由于“1”表示待配置项的配置内容具有全局唯一性，因此，服务器将该待配置项确定为目标待配置项。
S153：基于所述唯一身份标识对所述目标待配置的原始配置内容进行身份标记，将身份标记后的所述原始配置内容确定为所述目标待配置项的最终配置内容。
在本实施例中，在确定了目标待配置项后，服务器基于用户的唯一身份标识对目标待配置项的原始配置内容进行身份标记，将身份标记后的目标待配置项的原始配置内容确定为其最终配置内容。
作为本申请一实施例，监控实例的配置方法还可以包括以下步骤：
将所述待配置项中除所述目标待配置项之外的其余待配置项的原始配置内容确定为其最终配置内容。
在本实施例中，服务器对新创建的监控实例的待配置项中除目标待配置项之外的其余待配置项的原始配置内容不做任何处理，直接将除目标待配置项之外的其余待配置项的原始配置内容确定为相应待配置项的最终配置内容。
以上可以看出，本实施例提供的一种监控实例的配置方法仅对要求配置内容具有全局唯一性的目标待配置项的原始配置内容进行身份标记，而对未要求配置内容具有全局唯一性的待配置项的原始配置内容不做任何处理，从而提高了监控实例的配置效率。
图4示是本申请实施例提供的一种服务器的结构框图，该服务器包括的各单元用于执行图1至图3对应的实施例中的各步骤。具体请参阅图1至图3以及图1至图3所对应的实施例中的相关描述。为了便于说明，仅示出了与本实施例相关的部分。参见图3，所述服务器400包括：第一提取单元41、第一确定单元42、发送单元43、接收单元44及标记单元45。其中：
第一提取单元41用于若接收到终端发送的监控实例创建请求，则提取所述监控实例创建请求携带的监控实例类型标识。
第一确定单元42用于确定所述终端所属用户的唯一身份标识。
发送单元43用于基于与所述监控实例类型标识对应的监控实例模板创建监控实例，并将所述监控实例中的待配置项发送至所述终端，使所述终端获取并返回用户针对所述待配置项设置的原始配置内容。
接收单元44用于接收所述终端返回的所述待配置项的原始配置内容。
标记单元45用于基于所述唯一身份标识对所述待配置项的原始配置内容进行身份标记，将身份标记后的所述原始配置内容确定为所述待配置项的最终配置内容。
作为本申请一实施例，标记单元45具体用于：
基于预设的字符串组合方式，将所述唯一身份标识与所述待配置项的原始配置内容进行组合，得到所述待配置项的最终配置内容。
作为本申请一实施例，标记单元45包括：第一获取单元、第二确定单元及第三确定单元。其中：
第一获取单元用于获取所述待配置项的属性信息。
第二确定单元用于基于所述待配置项的属性信息，从所述待配置项中确定目标待配置项。
确定单元用于基于所述唯一身份标识对所述目标待配置的原始配置内容进行身份标记，将身份标记后的所述原始配置内容确定为所述目标待配置项的最终配置内容。
作为本申请一实施例，服务器400还包括第四确定单元。
第四确定单元用于将所述待配置项中除所述目标待配置项之外的其余待配置项的原始配置内容确定为其最终配置内容。
作为本申请一实施例，第一确定单元42包括：第二提取单元、第五确定单元及第六确定单元。其中：
第二提取单元用于提取所述监控实例创建请求携带的终端标识。
第五确定单元用于基于终端标识与用户的唯一身份标识之间的预设对应关系，确定所述终端标识对应的用户的唯一身份标识。
第六确定单元用于将所述终端标识对应的用户的唯一身份标识确定为所述终端所属用户的唯一身份标识。
以上可以看出，本实施例提供的一种服务器通过确定发送监控实例创建请求的终端所属用户的唯一身份标识，基于用户的唯一身份标识，对用户针对监控实例的待配置项所设置的配置内容进行身份标记，这样，即使不同用户针对同一类型的监控实例中的相同待配置项所设置的原始配置内容相同，但由于不同用户的唯一身份标识不同，从而使得服务器可以基于用户的唯一身份标识，对不同用户针对同一类型的监控实例中的相同待配置项所设置的配置内容进行区分，使得不同用户在同一待配置项的配置内容的设置上不会对彼此造成约束，即不同用户对同一待配置项所设置的配置内容可以相同，扩大了待配置项的配置内容的设置范围。
由于仅对要求配置内容具有全局唯一性的目标待配置项的原始配置内容进行身份标记，而对未要求配置内容具有全局唯一性的待配置项的原始配置内容不做任何处理，从而提高了监控实例的配置效率。
图5是本申请另一实施例提供的一种服务器的结构框图。如图5所示，该实施例的服务器5包括：处理器50、存储器51以及存储在所述存储器51中并可在所述处理器50上运行的计算机可读指令52，例如监控实例的配置方法的程序。处理器50执行所述计算机可读指令52时实现上述各个监控实例的配置方法各实施例中的步骤，例如图1所示的S11至S15。或者，所述处理器50执行所述计算机可读指令52时实现上述图4对应的实施例中各单元的功能，例如，图4所示的单元51至55的功能，具体请参阅图4对应的实施例中的相关描述，此处不赘述。
示例性的，所述计算机可读指令52可以被分割成一个或多个单元，所述一个或者多个单元被存储在所述存储器51中，并由所述处理器50执行，以完成本申请。所述一个或多个单元可以是能够完成特定功能的一系列计算机可读指令指令段，该指令段用于描述所述计算机可读指令52在所述服务器5中的执行过程。例如，所述计算机可读指令52可以被分割成第一提取单元、第一确定单元、发送单元、接收单元及标记单元，各单元具体功能如上所述。
所述服务器可包括，但不仅限于，处理器50、存储器51。本领域技术人员可以理解，图5仅仅是服务器5的示例，并不构成对服务器5的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件，例如所述服务器还可以包括输入输出设备、网络接入设备、总线等。
所称处理器50可以是中央处理单元（Central Processing Unit，CPU），还可以是其他通用处理器、数字信号处理器（Digital Signal Processor，DSP）、专用集成电路（Application Specific Integrated Circuit，ASIC）、现成可编程门阵列（Field-Programmable Gate Array，FPGA）或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
所述存储器51可以是所述服务器5的内部存储单元，例如服务器5的硬盘或内存。所述存储器51也可以是所述服务器5的外部存储设备，例如所述服务器5上配备的插接式硬盘，智能存储卡（Smart Media Card，SMC），安全数字（Secure Digital，SD）卡，闪存卡（Flash Card）等。进一步地，所述存储器51还可以既包括所述服务器5的内部存储单元也包括外部存储设备。所述存储器51用于存储所述计算机可读指令以及所述服务器所需的其他程序和数据。所述存储器51还可以用于暂时地存储已经输出或者将要输出的数据。
以上所述实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围，均应包含在本申请的保护范围之内。

Claims (20)

  1. 一种监控实例的配置方法，其特征在于，包括：
    若接收到终端发送的监控实例创建请求，则提取所述监控实例创建请求携带的监控实例类型标识；
    确定所述终端所属用户的唯一身份标识；
    基于与所述监控实例类型标识对应的监控实例模板创建监控实例，并将所述监控实例中的待配置项发送至所述终端，使所述终端获取并返回用户针对所述待配置项设置的原始配置内容；
    接收所述终端返回的所述待配置项的原始配置内容；
    基于所述唯一身份标识对所述待配置项的原始配置内容进行身份标记，将身份标记后的所述原始配置内容确定为所述待配置项的最终配置内容。
  2. 根据权利要求1所述的监控实例的配置方法，其特征在于，所述基于所述唯一身份标识对所述待配置项的原始配置内容进行身份标记，将身份标记后的所述原始配置内容确定为所述待配置项的最终配置内容，包括：
    基于预设的字符串组合方式，将所述唯一身份标识与所述待配置项的原始配置内容进行组合，得到所述待配置项的最终配置内容。
  3. 根据权利要求1所述的监控实例的配置方法，其特征在于，所述基于所述唯一身份标识对所述待配置项的原始配置内容进行身份标记，将身份标记后的所述原始配置内容确定为所述待配置项的最终配置内容，包括：
    获取所述待配置项的属性信息；
    基于所述待配置项的属性信息，从所述待配置项中确定目标待配置项；
    基于所述唯一身份标识对所述目标待配置的原始配置内容进行身份标记，将身份标记后的所述原始配置内容确定为所述目标待配置项的最终配置内容。
  4. 根据权利要求3所述的监控实例的配置方法，其特征在于，还包括：
    将所述待配置项中除所述目标待配置项之外的其余待配置项的原始配置内容确定为其最终配置内容。
  5. 根据权利要求1-4任一项所述的监控实例的配置方法，其特征在于，所述监控实例创建请求还携带终端标识；
    所述确定所述终端所属用户的唯一身份标识，包括：
    提取所述监控实例创建请求携带的终端标识；
    基于终端标识与用户的唯一身份标识之间的预设对应关系，确定所述终端标识对应的用户的唯一身份标识；
    将所述终端标识对应的用户的唯一身份标识确定为所述终端所属用户的唯一身份标识。
  6. 一种服务器，其特征在于，包括：
    第一提取单元，用于若接收到终端发送的监控实例创建请求，则提取所述监控实例创建请求携带的监控实例类型标识。
    第一确定单元，用于确定所述终端所属用户的唯一身份标识。
    发送单元，用于基于与所述监控实例类型标识对应的监控实例模板创建监控实例，并将所述监控实例中的待配置项发送至所述终端，使所述终端获取并返回用户针对所述待配置项设置的原始配置内容。
    接收单元，用于接收所述终端返回的所述待配置项的原始配置内容。
    标记单元，用于基于所述唯一身份标识对所述待配置项的原始配置内容进行身份标记，将身份标记后的所述原始配置内容确定为所述待配置项的最终配置内容。
  7. 根据权利要求6所述的服务器，其特征在于，所述标记单元具体用于：
    基于预设的字符串组合方式，将所述唯一身份标识与所述待配置项的原始配置内容进行组合，得到所述待配置项的最终配置内容。
  8. 根据权利要求6所述的服务器，其特征在于，所述标记单元包括：
    第一获取单元，用于获取所述待配置项的属性信息。
    第二确定单元，用于基于所述待配置项的属性信息，从所述待配置项中确定目标待配置项。
    确定单元，用于基于所述唯一身份标识对所述目标待配置的原始配置内容进行身份标记，将身份标记后的所述原始配置内容确定为所述目标待配置项的最终配置内容。
  9. 根据权利要求8所述的服务器，其特征在于，还包括：
    第四确定单元，用于将所述待配置项中除所述目标待配置项之外的其余待配置项的原始配置内容确定为其最终配置内容。
  10. 根据权利要求6-9任一项所述的服务器，其特征在于，所述监控实例创建请求还携带终端标识；
    所述第一确定单元包括：
    第二提取单元，用于提取所述监控实例创建请求携带的终端标识。
    第五确定单元，用于基于终端标识与用户的唯一身份标识之间的预设对应关系，确定所述终端标识对应的用户的唯一身份标识。
    第六确定单元，用于将所述终端标识对应的用户的唯一身份标识确定为所述终端所属用户的唯一身份标识。
  11. 一种服务器，包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机可读指令，其特征在于，所述处理器执行所述计算机可读指令时实现如下步骤：
    若接收到终端发送的监控实例创建请求，则提取所述监控实例创建请求携带的监控实例类型标识；
    确定所述终端所属用户的唯一身份标识；
    基于与所述监控实例类型标识对应的监控实例模板创建监控实例，并将所述监控实例中的待配置项发送至所述终端，使所述终端获取并返回用户针对所述待配置项设置的原始配置内容；
    接收所述终端返回的所述待配置项的原始配置内容；
    基于所述唯一身份标识对所述待配置项的原始配置内容进行身份标记，将身份标记后的所述原始配置内容确定为所述待配置项的最终配置内容。
  12. 根据权利要求11所述的服务器，其特征在于，所述基于所述唯一身份标识对所述待配置项的原始配置内容进行身份标记，将身份标记后的所述原始配置内容确定为所述待配置项的最终配置内容，包括：
    基于预设的字符串组合方式，将所述唯一身份标识与所述待配置项的原始配置内容进行组合，得到所述待配置项的最终配置内容。
  13. 根据权利要求11所述的服务器，其特征在于，所述基于所述唯一身份标识对所述待配置项的原始配置内容进行身份标记，将身份标记后的所述原始配置内容确定为所述待配置项的最终配置内容，包括：
    获取所述待配置项的属性信息；
    基于所述待配置项的属性信息，从所述待配置项中确定目标待配置项；
    基于所述唯一身份标识对所述目标待配置的原始配置内容进行身份标记，将身份标记后的所述原始配置内容确定为所述目标待配置项的最终配置内容。
  14. 根据权利要求13所述的服务器，其特征在于，还包括：
    将所述待配置项中除所述目标待配置项之外的其余待配置项的原始配置内容确定为其最终配置内容。
  15. 根据权利要求11-14任一项所述的服务器，其特征在于，所述监控实例创建请求还携带终端标识；
    所述确定所述终端所属用户的唯一身份标识，包括：
    提取所述监控实例创建请求携带的终端标识；
    基于终端标识与用户的唯一身份标识之间的预设对应关系，确定所述终端标识对应的用户的唯一身份标识；
    将所述终端标识对应的用户的唯一身份标识确定为所述终端所属用户的唯一身份标识。
  16. 一种计算机可读存储介质，所述计算机可读存储介质存储有计算机可读指令，其特征在于，所述计算机可读指令被处理器执行时实现如下步骤：
    若接收到终端发送的监控实例创建请求，则提取所述监控实例创建请求携带的监控实例类型标识；
    确定所述终端所属用户的唯一身份标识；
    基于与所述监控实例类型标识对应的监控实例模板创建监控实例，并将所述监控实例中的待配置项发送至所述终端，使所述终端获取并返回用户针对所述待配置项设置的原始配置内容；
    接收所述终端返回的所述待配置项的原始配置内容；
    基于所述唯一身份标识对所述待配置项的原始配置内容进行身份标记，将身份标记后的所述原始配置内容确定为所述待配置项的最终配置内容。
  17. 根据权利要求16所述的计算机可读存储介质，其特征在于，所述基于所述唯一身份标识对所述待配置项的原始配置内容进行身份标记，将身份标记后的所述原始配置内容确定为所述待配置项的最终配置内容，包括：
    基于预设的字符串组合方式，将所述唯一身份标识与所述待配置项的原始配置内容进行组合，得到所述待配置项的最终配置内容。
  18. 根据权利要求16所述的计算机可读存储介质，其特征在于，所述基于所述唯一身份标识对所述待配置项的原始配置内容进行身份标记，将身份标记后的所述原始配置内容确定为所述待配置项的最终配置内容，包括：
    获取所述待配置项的属性信息；
    基于所述待配置项的属性信息，从所述待配置项中确定目标待配置项；
    基于所述唯一身份标识对所述目标待配置的原始配置内容进行身份标记，将身份标记后的所述原始配置内容确定为所述目标待配置项的最终配置内容。
  19. 根据权利要求18所述的计算机可读存储介质，其特征在于，还包括：
    将所述待配置项中除所述目标待配置项之外的其余待配置项的原始配置内容确定为其最终配置内容。
  20. 根据权利要求16-19任一项所述的计算机可读存储介质，其特征在于，所述确定所述终端所属用户的唯一身份标识，包括：
    提取所述监控实例创建请求携带的终端标识；
    基于终端标识与用户的唯一身份标识之间的预设对应关系，确定所述终端标识对应的用户的唯一身份标识；
    将所述终端标识对应的用户的唯一身份标识确定为所述终端所属用户的唯一身份标识。
PCT/CN2018/105528 2018-06-11 2018-09-13 一种监控实例的配置方法、服务器及计算机可读存储介质 WO2019237538A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810592825.5 2018-06-11
CN201810592825.5A CN109032655B (zh) 2018-06-11 2018-06-11 一种监控实例的配置方法、服务器及计算机可读存储介质

Publications (1)

Publication Number Publication Date
WO2019237538A1 true WO2019237538A1 (zh) 2019-12-19

Family

ID=64612413

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/105528 WO2019237538A1 (zh) 2018-06-11 2018-09-13 一种监控实例的配置方法、服务器及计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN109032655B (zh)
WO (1) WO2019237538A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112711514A (zh) * 2020-12-30 2021-04-27 北京珞安科技有限责任公司 一种终端设备的监控系统、方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104022894A (zh) * 2014-05-12 2014-09-03 东软熙康健康科技有限公司 集中管理应用配置参数的方法、配置应用参数的方法
CN104113435A (zh) * 2014-07-04 2014-10-22 广州华多网络科技有限公司 生成标识的方法及装置
CN104333614A (zh) * 2014-10-31 2015-02-04 北京奇虎科技有限公司 终端识别的方法、装置及系统
CN106254575A (zh) * 2016-09-09 2016-12-21 广州酷狗计算机科技有限公司 一种确定用户标识的方法和装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100536410C (zh) * 2006-08-09 2009-09-02 艾默生网络能源有限公司 一种监控系统及其动态自配置方法
US10311513B2 (en) * 2012-03-14 2019-06-04 Nasdaq Technology Ab Method and system for facilitating access to recorded data

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104022894A (zh) * 2014-05-12 2014-09-03 东软熙康健康科技有限公司 集中管理应用配置参数的方法、配置应用参数的方法
CN104113435A (zh) * 2014-07-04 2014-10-22 广州华多网络科技有限公司 生成标识的方法及装置
CN104333614A (zh) * 2014-10-31 2015-02-04 北京奇虎科技有限公司 终端识别的方法、装置及系统
CN106254575A (zh) * 2016-09-09 2016-12-21 广州酷狗计算机科技有限公司 一种确定用户标识的方法和装置

Also Published As

Publication number Publication date
CN109032655A (zh) 2018-12-18
CN109032655B (zh) 2021-10-29

Similar Documents

Publication Publication Date Title
CN113574838B (zh) 通过客户端指纹过滤互联网流量的系统和方法
US10073916B2 (en) Method and system for facilitating terminal identifiers
AU2014235300B2 (en) Multi-layered storage administration for flexible placement of data
US11210426B2 (en) Tracing objects across different parties
US10834105B2 (en) Method and apparatus for identifying malicious website, and computer storage medium
US10389693B2 (en) Keys for encrypted disk partitions
EP3586256B1 (en) Remote administration of initial computer operating system setup options
WO2018145546A1 (zh) 一种鉴权方法、装置及存储介质
WO2020015092A1 (zh) 实例监控方法、装置、终端设备及介质
US20230376478A1 (en) Verifying structured data
US9477494B2 (en) System and method for reconciling duplicate configuration items in a configuration management database
CN110232279A (zh) 一种漏洞检测方法及装置
CN110120971B (zh) 一种灰度发布方法、装置及电子设备
CN109039803A (zh) 一种处理回调通知消息的方法、系统及计算机设备
US10693897B2 (en) Behavioral and account fingerprinting
WO2016058478A1 (zh) 数据获取方法、装置及系统
US11847412B2 (en) Enforcing data ownership at gateway registration using natural language processing
WO2019237538A1 (zh) 一种监控实例的配置方法、服务器及计算机可读存储介质
US11418570B2 (en) Robust computing device identification framework
WO2023087278A1 (zh) 一种云平台权限设置方法、装置、终端设备及存储介质
US10951600B2 (en) Domain authentication
CN105743667A (zh) 一种访问管控方法、装置及系统
WO2019237539A1 (zh) 一种监控数据的处理方法、服务器及计算机可读存储介质
CN109067542B (zh) Token生成方法、基于Token的追踪方法及装置
CN109271398B (zh) 数据库事务处理方法、装置、设备和计算机可读存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18922228

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18922228

Country of ref document: EP

Kind code of ref document: A1