Service alerting method and apparatus

Abstract

The present specification provides a service alarm method and device, applied to a cloud service platform, the cloud service platform is used for respectively connecting target service instance and target service provider, the target service instance is created by deploying the service provided by the target service provider on the cloud resource corresponding to the target user, the method comprises: obtaining alarm information for the target service instance; in the case of determining that the target user has given the target service provider alarm information acquisition authority for the target service instance, the alarm information is sent to the target service provider.

Description

Technical Field

[0001] This manual relates to the field of cloud computing, and in particular to a service alarm method and apparatus. Background Technology

[0002] With the development of cloud computing technology, more and more users are choosing to have third-party service providers offer the application software they need, allowing them to use the software directly without having to build or maintain it themselves. However, if the application software provided by the service provider is ultimately deployed on the user's cloud resources, then if any anomaly occurs, the user must proactively detect it and report it to the service provider before the service provider can troubleshoot. This results in low efficiency in handling anomalies. Furthermore, the existence of a many-to-many relationship between users and service providers leads to high management costs and difficulties. Summary of the Invention

[0003] In view of this, this specification provides a service alarm method and apparatus to address the shortcomings of the related technologies.

[0004] Specifically, this specification is implemented through the following technical solution:

[0005] According to a first aspect of the embodiments of this specification, a service alerting method is provided, applied to a cloud service platform, the cloud service platform being used to respectively connect to a target service instance and a target service provider, the target service instance being created by deploying a service provided by a target service provider on cloud resources corresponding to a target user, the method comprising:

[0006] Obtain alarm information for the target service instance;

[0007] If it is determined that the target user has granted the target service provider permission to obtain alarm information for the target service instance, the alarm information is sent to the target service provider.

[0008] According to a second aspect of the embodiments of this specification, a service alarm device is provided, applied to a cloud service platform, the cloud service platform being used to respectively connect to a target service instance and a target service provider, the target service instance being created by deploying a service provided by a target service provider on cloud resources corresponding to a target user, the device comprising:

[0009] An alarm information acquisition unit is used to acquire alarm information for the target service instance;

[0010] An alarm information sending unit is used to send the alarm information to the target service provider when it is determined that the target user has granted the target service provider permission to obtain alarm information for the target service instance.

[0011] According to a third aspect of the embodiments of this specification, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described in the first aspect.

[0012] According to a fourth aspect of the embodiments of this specification, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of the method described in the first aspect.

[0013] In the technical solution provided in this specification, the cloud service platform establishes a clear and controllable management channel between target users and target service providers by introducing authorization management technology, which improves the management efficiency of target users and target service providers in one-to-many or many-to-one situations. At the same time, when the target service instance generates an alarm, the target service provider can automatically and promptly receive and process the alarm information, thereby improving the efficiency of alarm processing.

[0014] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this specification. Attached Figure Description

[0015] Figure 1 This is a schematic diagram of the architecture of a service alarm system shown in an exemplary embodiment of this specification;

[0016] Figure 2 This is a flowchart illustrating an exemplary embodiment of a service alarm method as shown in this specification;

[0017] Figure 3 This is an exemplary embodiment of the present specification illustrating a three-way interaction between a user, a cloud service platform, and a service provider;

[0018] Figure 4 This is a schematic structural diagram of an electronic device shown in an exemplary embodiment of this specification;

[0019] Figure 5 This is a schematic diagram illustrating the structure of a service alarm device according to an exemplary embodiment of this specification. Detailed Implementation

[0020] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this specification. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this specification as detailed in the appended claims.

[0021] The terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to be limiting of this specification. The singular forms “a,” “the,” and “the” as used in this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

[0022] It should be understood that although the terms first, second, third, etc., may be used in this specification to describe various information, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this specification, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."

[0023] Figure 1 This is a schematic diagram of the architecture of a service alarm system shown in this specification. Figure 1 As shown, it may include cloud resources 11, service providers 12, and cloud service platforms 13.

[0024] Cloud resource 11 can be any Elastic Compute Service (ECS) instance or other cloud resource of the user. Cloud resource 11 can be used to deploy services to form the target service instance described below. The user may acquire ownership of cloud resource 11 by leasing or building their own cloud server, etc., and this specification does not impose any restrictions on this.

[0025] Service provider 12 can provide the aforementioned users with a range of services required for deployment to the aforementioned cloud resource 11. Service provider 12 may be a third party at different service stages, such as an enterprise application service provider, IT integration service provider, delivery service provider, or managed service provider; this specification does not impose any restrictions on this.

[0026] The cloud service platform 13, supported by a cloud computing technology architecture, is a service management platform open to service providers 12 and users, enabling them to deliver and manage various services. Furthermore, the cloud service platform 13 can be a physical server containing an independent host, or it can be a virtual server hosted by a host cluster. During operation, the cloud service platform 13 can obtain alarm information related to the target service instances described below in cloud resources 11 and send it to the corresponding service provider 12.

[0027] Cloud resources 11, service providers 12, and cloud service platforms 13 can interact through various types of wired or wireless networks.

[0028] Figure 2 This is a flowchart illustrating an exemplary embodiment of a service alerting method described in this specification. Figure 2 As shown, this method can be applied to a cloud service platform, which is used to connect to the target service instance and the target service provider respectively. The target service instance is created by deploying the service provided by the target service provider on the cloud resources corresponding to the target user. The method may include the following steps:

[0029] S201, Obtain alarm information for the target service instance.

[0030] A target user can own a set of cloud resources. By deploying services on these cloud resources, service instances as described above can be formed. The services deployed on these cloud resources can be provided by service providers. For example, a target service provider can deploy its services on the cloud resources owned by the target user to form the target service instance. The cloud service platform can connect users and service providers. For instance, a service provider can publish its services on the cloud service platform, allowing users to access and subscribe to these services. If a target user subscribes to a service provided by a target service provider through the cloud service platform, the target service provider can deploy its services to the target user's cloud resources to form the target service instance; alternatively, the cloud service platform can handle the deployment process on behalf of the target service provider, simplifying the service provider's operations.

[0031] For service instances formed by deployed services, service providers can also provide corresponding operation and maintenance work. For example, the target service provider mentioned above can provide services for deployment to target users' cloud resources, and can also provide subsequent operation and maintenance work for the formed target service instances.

[0032] Each user can own multiple service instances, which can come from one or more service providers. A single service provider can also serve one or more users. Therefore, there can be one-to-one, one-to-many, or many-to-many relationships between users and service providers; this specification does not impose any restrictions on this. The target service instance is any one of all the service instances owned by the target user.

[0033] Alarm messages for a target service instance can characterize a predefined state of that instance. This predefined state can indicate an anomaly in the operation of the target service instance, and may include, but is not limited to, any of the following: functional bugs or vulnerabilities, structural code design errors, messages indicating non-compliance with relevant design specifications, system log information that does not meet preset conditions, or unidentifiable exceptions. Alternatively, this predefined state can reflect other information related to the target service instance that is not necessarily related to operational anomalies, such as periodically reporting important operational parameters of the target service instance. In short, alarm messages can be generated when the generation conditions are met; in other words, by defining the generation conditions, the alarm message generation process can be controlled.

[0034] The generation conditions can be defined according to actual needs. For example, the status information of the target service instance can meet predefined alarm information generation rules. These rules may include whether the target service instance has triggered a preset operation or event, or whether the target service instance's memory space, processor utilization, number of processes, and other operating parameters are abnormal. This specification does not impose any restrictions on this. The alarm information generation rules can be defined by the target service provider or the target user, or partially defined by the target service provider and partially by the target user. Therefore, by customizing the alarm information generation rules, highly customizable and flexible features are provided for the aforementioned alarm information.

[0035] In one embodiment, the alarm information can be actively generated by the target service instance. The target service instance itself supports the generation of alarm information, and the cloud service platform can obtain the alarm information generated by the target service instance in different ways. For example, the cloud service platform can subscribe to the alarm information from the target service instance, so that the target service instance can actively send the generated alarm information to the cloud service platform. Another example is that the cloud service platform can request the target service instance to query the generated alarm information at a preset period. Yet another example is that the alarm information can be set to be permanently recorded in certain files, such as logs, so the cloud service platform can obtain the alarm information by listening to the log content. This specification does not impose any limitations on this approach.

[0036] In another embodiment, the alarm information can be generated by a monitoring instance running on the cloud resources corresponding to the target user, which monitors the target service instance. That is, a monitoring instance targeting the target service instance runs on the cloud resources corresponding to the target user, and when the target service instance experiences a specific situation, this monitoring instance can generate corresponding alarm information. The monitoring instance can be any software program or system process that supports monitoring functions; this specification does not limit its scope.

[0037] In another embodiment, the alarm information can be generated by the cloud service platform by monitoring the target service instance. This allows the target user to obtain alarm information for the target service instance without having to set up any monitoring instance for the corresponding cloud resource, thereby reducing the operational threshold for the target user and improving the user experience.

[0038] The methods for obtaining alarm information described above can be determined according to actual needs, and this manual does not impose any restrictions on them.

[0039] S202, if it is determined that the target user has granted the target service provider permission to obtain alarm information for the target service instance, the alarm information is sent to the target service provider.

[0040] Target users can set operation permissions for target service providers on target service instances, thereby managing the scope of operations the target service provider can perform on the target service instance. For example, when a target user grants the target service provider only read-only permissions for the target service instance, the target service provider can only perform read operations such as viewing directories and files on the target service instance. Similarly, when a target user grants the target service provider permission to obtain alarm information for the target service instance, the target service provider can directly obtain alarm information for the target service instance from the cloud service platform.

[0041] Alarm messages can be set to be sent to multiple different objects according to actual needs.

[0042] In one embodiment, the cloud service platform can synchronize alarm information sent to the target user to the target service provider, ensuring that both the target user and the target service provider receive the alarm information. This reduces the information gap between the two parties and facilitates efficient processing of alarm information. Those skilled in the art will understand that this specification does not limit the order in which the alarm information is sent, as long as it is ensured that the alarm information is sent to the target user and the target service provider separately. For example, it can be configured to send the alarm information to the target user first, then to the target service provider, or it can be configured to send the alarm information to the target service provider first, then to the target user, or it can be configured to send the alarm information to both the target service provider and the target user simultaneously.

[0043] Target users can proactively grant target service providers permission to receive alarm information for target service instances. Alternatively, when a target service provider needs permission to receive alarm information for a target service instance, it can proactively initiate a relevant request to the cloud service platform.

[0044] In one embodiment, the cloud service platform can receive a permission request initiated by a target service provider for a target service instance. The permission request requests permission to access alarm information for the target service instance. Based on the permission request, the platform sends permission confirmation information to the target user corresponding to the target service instance. Based on the operation result returned by the target user in response to the permission confirmation information, the platform determines whether to grant the target service provider permission to access alarm information for the target service instance. The permission request includes at least the description information of the target service provider, the description information of the target service instance, and the description information of the specific permission requested. The permission confirmation information is obtained based on the permission request and is used to confirm with the target user whether to grant the target service provider the aforementioned specific permission for the target service instance.

[0045] For example, when the target service provider needs to perform a data write operation on the target service instance but finds it lacks the corresponding permissions, it can send a permission request for that data write permission. When the target user corresponding to the target service instance receives the permission confirmation information for the request, and grants permission, the target service provider can successfully obtain the data write permission. Similarly, if the target user does not trust or need the target service provider to obtain the corresponding permission and denies it, the target service provider cannot obtain the data write permission. This operation effectively improves the efficiency of permission management for the target service instance by allowing the target service provider to actively request permissions.

[0046] When a target service provider performs a certain operation, it may need to have multiple different permissions at the same time. When a target user faces an authorization scenario that requires granting a large number of cumbersome permissions to the target service provider at the same time, the cloud service platform can provide a simplified operation process for the target user.

[0047] In one embodiment, the cloud service platform pre-encapsulates an authorization scenario in which the authorizing party grants the authorized party specified permissions for the service instance corresponding to the authorizing party. The cloud service platform receives an application request from the target user for the authorization scenario. The application request includes at least the description information of the target user, the description information of the target service provider, and the description information of the target service instance. The information contained in the application request is assigned to the authorization scenario, and the authorization scenario is applied so that the target user grants the target service provider the specified permissions for the authorization scenario corresponding to the target service. Before being assigned values, the authorization scenario only contains the encapsulated permissions. For example, the cloud service platform encapsulates read-only permissions such as "ecs:DescribeInvocations", "ecs:DescribeInstances", and "ecs:DescribeDisks" into a single "*:Describe*". When the target user sends the application request to the cloud service platform, the descriptive information about the target user, the target service provider, and the target service instance in the application request can be assigned to the authorization scenario. That is, the target user is the authorizing party, the target service provider is the authorized party, and the authorized object is the target service instance. This authorization scenario is then applied to grant the target user read-only permissions to the target service provider for the corresponding authorization scenario of the target service. By encapsulating the authorization scenario, the target user does not need to concern themselves with the specific authorized permissions, greatly reducing the operational threshold for configuring permissions for the target service instance and granting them to the target service provider, thus improving the user experience.

[0048] When the cloud service platform determines that the target user has granted the target service provider permission to access alarm information for the target service instance, it can send the alarm information to the target service provider. Operation permissions may include read / write permissions, remote connection permissions, or permissions to receive specific information for the target service instance, etc., but this specification does not impose any restrictions on these permissions.

[0049] In one embodiment, the cloud service platform can query the service alarm permission rules corresponding to the target service instance. These rules record the authorized objects and / or descriptions of the authorized objects pre-set by the target user for the target service instance. If it is determined that the target service provider belongs to the authorized object defined by the service alarm permission rules, it is determined that the target user has granted the target service provider permission to obtain alarm information for the target service instance. The authorized object of the target service instance can be any service provider, and the description of the authorized object can be identification information representing any service provider. This identification information can be a unique identifier or name of the service provider on the cloud service platform, and this specification does not impose any limitations on this. Furthermore, the service alarm permission rules can be stored and maintained in the form of text, database tables, blockchain, etc., and this specification does not impose any limitations on this.

[0050] When a target service provider needs to remotely connect to a target service instance to maintain or configure services on that instance, the cloud service platform can provide a quick connection operation for the target service provider based on the target user's authorization status for the target service instance.

[0051] In one embodiment, the cloud service platform receives a remote connection request from the target service provider for a target service instance. This remote connection request is independent of the target user's username and / or password for the target service instance. If the target user has already granted the target service provider passwordless access permissions for the target service instance, a remote connection is established between the target service provider and the target user based on the remote connection request. Since the target user has granted the target service provider passwordless access permissions for the target service instance, in other words, the target service provider can connect to the target service instance without obtaining the target user's username and / or password, simplifying the remote connection process and improving the overall service efficiency of the target service provider.

[0052] As can be seen from the above embodiments, the service alarm method in this specification, under the premise of providing target users and target service providers with a management system based on the concept of "authorization" for operation management, improves the efficiency of target service providers in processing alarm information for target service instances, and avoids the time wasted by target users in discovering and actively notifying target service providers in related technologies; in addition, it simplifies the authorization operation of target users by encapsulating the authorization scenario, and improves the efficiency of target service providers in remotely connecting to target service instances by granting passwordless operation permissions, thereby improving the overall user experience of target users and target service providers.

[0053] Figure 3This is an exemplary embodiment of the present specification illustrating a three-way interaction between a user, a cloud service platform, and a service provider. Figure 3 As shown, this method can be applied to a cloud service platform, which is used to connect to the target service instance and the target service provider respectively. The target service instance is created by deploying the service provided by the target service provider on the cloud resources corresponding to the target user. The method may include the following steps:

[0054] S301, Initiates a permission request for the target service instance.

[0055] In one embodiment, there exists a target user, an independent software vendor (ISV) as the target service provider, and a Platform-as-a-Service (PaaS) platform as the cloud service platform. The target service provider deploys corresponding software service objects on the target user's cloud resources through the cloud service platform, thereby forming a corresponding target service instance. To obtain permission to access alarm information for the target service instance, the target service provider initiates a permission request to the cloud service platform for the target service instance.

[0056] S302, Receive permission request.

[0057] In one embodiment, the cloud service platform receives a permission request. In some cases, if the target user has pre-set permission management rules on the cloud service platform and entrusted the cloud service platform to manage permissions based on these rules, the cloud service platform can skip steps S303-305 and proactively determine whether to grant the target service provider the corresponding alarm information access permission based on the permission management rules.

[0058] S303: Send permission confirmation information based on the permission request.

[0059] S304, response permission confirmation message.

[0060] S305 returns the operation result for the permission confirmation information.

[0061] In one embodiment, the cloud service platform generates corresponding permission confirmation information based on the permission request and sends it to the target user. Accordingly, the target user receives the permission confirmation information and determines that the target service provider wishes to obtain permission to obtain alarm information for the target service instance, and the target user can decide whether to grant the target service provider permission to obtain alarm information for the target service instance based on the actual situation.

[0062] In one embodiment, if the target user accepts the permission confirmation information, then S306 is executed; otherwise, the cloud service platform is instructed to send a notification message to the target service provider indicating that the permission application failed.

[0063] S306, determine the service alarm permission rules based on the operation results.

[0064] In one embodiment, the cloud service platform records the following in the service alarm permission rules for the target service instance based on the operation result: the authorized object for obtaining alarm information for the target service instance set by the target service provider as the target user.

[0065] S307, Obtain alarm information for the target service instance. The alarm information is generated based on the alarm information generation rules.

[0066] In one embodiment, the cloud service platform maintains alarm information generation rules for a target service instance. Assume these rules include the condition that "the remaining available memory of the target service instance is less than 2GB." Therefore, if the cloud service platform determines that the remaining available memory of the target service instance is less than 2GB through monitoring, it can confirm that the condition has been met and generate the corresponding alarm information according to the alarm information generation rules. The alarm information may include a unique identifier for the target service instance within the cloud service platform and information about the current memory usage status of the target service instance.

[0067] S308, query the service alarm permission rules corresponding to the target service instance.

[0068] In one embodiment, the cloud service platform can query service alarm permission rules to determine the authorized object for obtaining alarm information for a target service instance. For example, the authorized object may include the target service provider mentioned above.

[0069] S309, if it is determined that the target service provider is an authorized object of the alarm information acquisition permission for the target service instance as defined by the service alarm permission rules, it is determined that the target user has granted the target service provider the alarm information acquisition permission for the target service instance.

[0070] In one embodiment, if the cloud service platform determines, based on the query results of the service alarm permission rules, that the target service provider is the authorized object for obtaining alarm information for the target service instance, it can determine that the target user has granted the target service provider the permission to obtain alarm information for the target service instance.

[0071] S310, send alarm information.

[0072] In one embodiment, alarm information for the target service instance is sent to the target service provider so that the target service provider can perform operations such as "releasing idle memory" on the target service instance in a timely manner based on the content provided by the alarm information, so as to ensure that the target service instance can recover to normal in a timely manner and avoid the target service instance from becoming abnormal and causing damage to the interests of the target user.

[0073] Figure 4 This is a schematic structural diagram of an electronic device according to an exemplary embodiment. Please refer to... Figure 4 At the hardware level, the electronic device includes a processor, internal bus, network interface, memory, and non-volatile memory, and may also include other necessary hardware. The processor reads the corresponding computer program from the non-volatile memory into memory and then runs it, forming a service alarm device at the logical level. Of course, in addition to software implementation, this specification does not exclude other implementation methods, such as logic devices or a combination of hardware and software, etc. That is to say, the execution subject of the following processing flow is not limited to individual logic units, but can also be hardware or logic devices.

[0074] Corresponding to the embodiments of the aforementioned service alarm method, this specification also provides embodiments of a service alarm device.

[0075] Please refer to Figure 5 , Figure 5 This is a schematic diagram illustrating the structure of a service alarm device in an exemplary embodiment. For example... Figure 5 As shown, in the software implementation, the service alarm device may include:

[0076] The alarm information acquisition unit 501 is used to acquire the alarm information for the target service instance, wherein the target service instance is created by deploying the service provided by the target service provider on the cloud resources corresponding to the target user;

[0077] The alarm information sending unit 502 is used to send the alarm information to the target service provider when it is determined that the target user has granted the target service provider permission to obtain alarm information for the target service instance.

[0078] Optionally, the device further includes:

[0079] Alarm information generation unit 503, used for the alarm information to be actively generated by the target service instance;

[0080] Alternatively, the alarm information is generated by a monitoring instance running on the cloud resources corresponding to the target user monitoring the target service instance;

[0081] Alternatively, the alarm information may be generated by the cloud service platform through monitoring the target service instance.

[0082] Optionally, the alarm information sending unit 502 is specifically used for:

[0083] The alarm information sent to the target user is synchronized to the target service provider. Optionally, the device further includes:

[0084] The permission determination unit 504 is used to query the service alarm permission rules corresponding to the target service instance. The service alarm permission rules are used to record the authorized objects and / or description information of the authorized objects that the target user has pre-set for the target service instance.

[0085] If it is determined that the target service provider belongs to the authorized object defined by the service alarm permission rule, it is determined that the target user has granted the target service provider permission to obtain alarm information for the target service instance.

[0086] Optionally, the device further includes:

[0087] The permission request unit 505 is used to receive the permission request initiated by the target service provider for the target service instance, wherein the permission request is used to request permission to obtain alarm information for the target service instance;

[0088] Based on the permission request, permission confirmation information is sent to the target user corresponding to the target service instance;

[0089] Based on the operation result returned by the target user in response to the permission confirmation information, determine whether to grant the target service provider permission to obtain alarm information for the target service instance.

[0090] Optionally, the alarm information acquisition unit 501 is specifically used for:

[0091] The alarm information generation conditions include that the status information of the target service instance meets the predefined alarm information generation rules;

[0092] The alarm information generation rules are defined by the target service provider or the target user.

[0093] Optionally, the cloud service platform pre-encapsulates an authorization scenario in which the authorizing party grants the authorized party specified permissions for the service instance corresponding to the authorizing party, and the device further includes:

[0094] The permission scenario encapsulation unit 506 is used to receive the application request from the target user for the authorization scenario, wherein the application request includes at least the description information of the target user, the description information of the target service provider, and the description information of the target service instance.

[0095] The information contained in the application request is assigned to the authorization scenario, and the authorization scenario is applied so that the target user grants the target service provider the specified permissions for the target service corresponding to the authorization scenario.

[0096] Optionally, the device further includes:

[0097] The passwordless connection unit 507 is used to receive a remote connection request from the target service provider for the target service instance, wherein the remote connection request is unrelated to the username and / or password of the target user for the target service instance;

[0098] If the target user has granted the target service provider passwordless operation permissions for the target service instance, a remote link is established between the target service provider and the target user based on the remote link request.

[0099] The specific implementation process of the functions and roles of each unit in the above device can be found in the implementation process of the corresponding steps in the above method, and will not be repeated here.

[0100] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of the solution in this specification according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0101] The embodiments of the subject matter and functional operation described in this specification can be implemented in the following ways: digital electronic circuits, tangibly embodied computer software or firmware, computer hardware including the structures disclosed in this specification and their structural equivalents, or combinations thereof. Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a tangible, non-transitory program carrier for execution by a data processing apparatus or for controlling the operation of a data processing apparatus. Alternatively or additionally, the program instructions may be encoded on artificially generated propagation signals, such as machine-generated electrical, optical, or electromagnetic signals, which are generated to encode information and transmit it to a suitable receiving device for execution by the data processing apparatus. The computer storage medium may be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or combinations thereof.

[0102] The processing and logic flow described in this specification can be executed by one or more programmable computers that execute one or more computer programs to perform corresponding functions by operating on input data and generating output. The processing and logic flow can also be executed by dedicated logic circuitry—such as FPGAs (Field-Programmable Gate Arrays) or ASICs (Application-Specific Integrated Circuits), and the device can also be implemented as dedicated logic circuitry.

[0103] Suitable computers for executing computer programs include, for example, general-purpose and / or special-purpose microprocessors, or any other type of central processing unit. Typically, the central processing unit receives instructions and data from read-only memory and / or random access memory. The basic components of a computer include a central processing unit for implementing or executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include one or more mass storage devices for storing data, such as disks, magneto-optical disks, or optical disks, or the computer will be operatively coupled to such mass storage devices to receive data from or transfer data to them, or both. However, a computer is not required to have such devices. Furthermore, a computer can be embedded in another device, such as a mobile phone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a global positioning system (GPS) receiver, or a portable storage device such as a universal serial bus (USB) flash drive, to name a few.

[0104] Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices, such as semiconductor memory devices (e.g., EPROM, EEPROM, and flash memory devices), magnetic disks (e.g., internal hard disks or removable disks), magneto-optical disks, and CD-ROM and DVD-ROM disks. Processors and memory may be supplemented by or incorporated into dedicated logic circuitry.

[0105] While this specification contains numerous specific implementation details, these should not be construed as limiting the scope of any invention or the scope of the claims, but rather are primarily intended to describe features of specific embodiments of a particular invention. Certain features described in the various embodiments herein may also be implemented in combination in a single embodiment. Conversely, various features described in a single embodiment may also be implemented separately in various embodiments or in any suitable sub-combination. Furthermore, while features may function in certain combinations as described above and even initially claimed in this way, one or more features from a claimed combination may be removed from that combination in some cases, and a claimed combination may refer to a sub-combination or a variation thereof.

[0106] Similarly, although the operations are depicted in a specific order in the accompanying drawings, this should not be construed as requiring these operations to be performed in the specific order shown or sequentially, or requiring all illustrated operations to be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Furthermore, the separation of various system modules and components in the above embodiments should not be construed as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

[0107] Thus, specific embodiments of the subject matter have been described. Other embodiments are within the scope of the appended claims. In some cases, the actions recited in the claims may be performed in a different order and still achieve the desired result. Furthermore, the processes depicted in the drawings are not necessarily shown in a specific order or sequence to achieve the desired result. In some implementations, multitasking and parallel processing may be advantageous.

[0108] The above description is merely a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of protection of this specification.

Claims

1. A service alarm method, characterized in that, The method is applied to a cloud service platform, which is used to connect to a target service instance and a target service provider, respectively. The target service instance is created by deploying services provided by the target service provider on cloud resources corresponding to the target user. The method includes: Obtain alarm information for the target service instance; If it is determined that the target user has granted the target service provider permission to obtain alarm information for the target service instance, the alarm information is sent to the target service provider. Sending the alarm information to the target service provider includes: The alarm information sent to the target user will be synchronized to the target service provider.

2. The method according to claim 1, characterized in that, The alarm information is actively generated by the target service instance; Alternatively, the alarm information is generated by a monitoring instance running on the cloud resources corresponding to the target user monitoring the target service instance; Alternatively, the alarm information may be generated by the cloud service platform through monitoring the target service instance.

3. The method according to claim 1, characterized in that, Also includes: Query the service alarm permission rules corresponding to the target service instance. The service alarm permission rules are used to record the authorized objects and / or description information of the authorized objects that the target user has pre-set for the target service instance. If it is determined that the target service provider belongs to the authorized object defined by the service alarm permission rule, it is determined that the target user has granted the target service provider permission to obtain alarm information for the target service instance.

4. The method according to claim 1, characterized in that, Also includes: Receive the permission request initiated by the target service provider for the target service instance, the permission request being used to request permission to obtain alarm information for the target service instance; Based on the permission request, send permission confirmation information to the target user corresponding to the target service instance; Based on the target user's response to the permission confirmation information, determine whether to grant the target service provider permission to obtain alarm information for the target service instance.

5. The method according to claim 1, characterized in that, The alarm information generation conditions include that the status information of the target service instance meets the predefined alarm information generation rules; The alarm information generation rules are defined by the target service provider or the target user.

6. The method according to claim 1, characterized in that, The cloud service platform pre-encapsulates an authorization scenario where the authorizing party grants the authorized party specified permissions for the service instance corresponding to the authorizing party, and also includes: Receive the application request from the target user for the authorized scenario, the application request including at least the description information of the target user, the description information of the target service provider, and the description information of the target service instance; The information contained in the application request is assigned to the authorization scenario, and the authorization scenario is applied so that the target user grants the target service provider the specified permissions for the target service corresponding to the authorization scenario.

7. The method according to claim 1, characterized in that, Also includes: Receive a remote connection request from the target service provider for the target service instance, wherein the remote connection request is unrelated to the target user's username and / or password for the target service instance; If the target user has granted the target service provider passwordless operation permissions for the target service instance, a remote link is established between the target service provider and the target user based on the remote link request.

8. A service alarm device, characterized in that, An apparatus applied to a cloud service platform, wherein the cloud service platform is used to connect to a target service instance and a target service provider, wherein the target service instance is created by deploying services provided by the target service provider on cloud resources corresponding to the target user, the apparatus comprising: An alarm information acquisition unit is used to acquire alarm information for the target service instance; An alarm information sending unit is used to send the alarm information to the target service provider when it is determined that the target user has granted the target service provider permission to obtain alarm information for the target service instance. The alarm information sending unit is specifically used for: The alarm information sent to the target user will be synchronized to the target service provider.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the steps of the method as described in any one of claims 1 to 7.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps of the method as described in any one of claims 1 to 7.

Images