CN114461501A - Resource abnormality detection method and device, storage medium, and electronic device - Google Patents
Resource abnormality detection method and device, storage medium, and electronic device Download PDFInfo
- Publication number
- CN114461501A CN114461501A CN202210138920.4A CN202210138920A CN114461501A CN 114461501 A CN114461501 A CN 114461501A CN 202210138920 A CN202210138920 A CN 202210138920A CN 114461501 A CN114461501 A CN 114461501A
- Authority
- CN
- China
- Prior art keywords
- resource
- ingress
- configuration information
- namespace
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3055—Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
- G06F11/3093—Configuration details thereof, e.g. installation, enabling, spatial arrangement of the probes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
- G06F11/324—Display of status information
- G06F11/327—Alarm or error message display
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Mathematical Physics (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the invention provides a resource abnormity detection method and device, a storage medium and an electronic device, wherein the method comprises the following steps: acquiring routing configuration information of a gateway of a target application; acquiring configuration information of Ingress resources configured by Namespace Namespace resources in the containerized application K8s, wherein the Ingress resources and the Namespace resources both comprise tag information of a target application, the Namespace resources are used for resource isolation in K8s, and the Ingress resources are used for flow distribution in K8 s; and performing exception detection on the Ingress resource based on the routing configuration information of the gateway and the configuration information of the Ingress resource. The invention solves the problem of monitoring the Ingress resource in the related technology and achieves the effect of effectively monitoring the Ingress resource.
Description
Technical Field
The embodiment of the invention relates to the field of communication, in particular to a resource abnormity detection method and device, a storage medium and an electronic device.
Background
With the continuous development of the cloud native technology, the traditional business is continuously clouded, the whole business environment becomes more and more complex, and the requirement for interconnection and access of internal and external services of the cloud becomes more and more urgent. The traditional gateway service only has a common static route configuration function, and the container service has the characteristics of light weight, multiple tenants, quick deployment and elastic expansion and contraction, and cannot be flexibly managed and dynamically configured.
On a container cloud platform based on Kubernetes, a user can manage and maintain an access route of self application service in a cluster in an Ingress resource mode so as to realize uniform access of the application service inside the cluster, but when facing to the external access requirement of the cluster under the condition of isolating an internal network and an external network of the cloud, a uniform gateway is needed to expose route information to external application so that the external application can access the internal service of the cluster.
However, in the prior art, a user cannot create Ingress resources at will, and the Ingress resources can be normally used only after being created through a series of pre-operations through a background service after passing through a release process. It is impossible to monitor Ingress resources under some kind of Namespace (a plurality of Namespace with variable quantity), which can only be all or specific (the quantity cannot be dynamically changed) Namespace, and Namespace must be monitored first, and then Ingress under Namespace is monitored. And a repeated compatibility mechanism and a prompt alarm mechanism are not provided, when Ingress resources which are the same as the published api address exist or are created abnormally in the cluster, errors of the upstream service address corresponding to the api can be caused, and task abnormity alarm prompt is not provided.
Disclosure of Invention
The embodiment of the invention provides a resource abnormity detection method and device, a storage medium and an electronic device, and aims to at least solve the problem of monitoring Ingress resources in the related art.
According to an embodiment of the present invention, there is provided a method for detecting an abnormality of a resource, including: acquiring routing configuration information of a gateway of a target application; acquiring configuration information of Ingress resources configured by Namespace resources in containerized applications K8s, wherein the Ingress resources and the Namespace resources both include tag information of the target applications, the Namespace resources are used for resource isolation in K8s, and the Ingress resources are used for traffic distribution in K8 s; and performing anomaly detection on the Ingress resource based on the routing configuration information of the gateway and the configuration information of the Ingress resource.
According to another embodiment of the present invention, there is provided an abnormality detection apparatus for a resource, including: the first acquisition module is used for acquiring the routing configuration information of the gateway of the target application; a second obtaining module, configured to obtain configuration information of an Ingress resource configured by a Namespace resource in a containerized application K8s, where the Ingress resource and the Namespace resource both include tag information of the target application, the Namespace resource is used for resource isolation in the K8s, and the Ingress resource is used for traffic distribution in the K8 s; and the first detection module is used for carrying out abnormity detection on the Ingress resource based on the routing configuration information of the gateway and the configuration information of the Ingress resource.
In an exemplary embodiment, the apparatus further includes: the first sending module is used for sending first request information to a packet manager Helm before the route configuration information of the gateway of the target application is acquired; the first request information is used for requesting the Helm to configure the gateway in the target application, and marking tag information of the target application in a control unit in the Namespace resource.
In an exemplary embodiment, the apparatus further includes: the first receiving module is used for receiving second request information of a user before acquiring configuration information of Ingress resources configured by Namespace resources in the containerized application K8 s; a first establishing module, configured to establish the Ingress resource in the Namespace resource based on the second request information, where tag information of a target application in the Ingress resource is set by the event processing application in K8 s.
In an exemplary embodiment, the first detecting module includes: a first determining unit, configured to add routing configuration information in the configuration information of the Ingress resource to routing configuration information in the gateway, and determine N pieces of routing configuration information, where N is a natural number greater than 1; a second determining unit, configured to determine abnormal routing configuration information from the N routing configuration information; and a first detection unit, configured to perform anomaly detection on the Ingress resource based on the anomaly routing information.
In an exemplary embodiment, the apparatus further includes: the first sending module is configured to send abnormal warning information to a user when it is determined that the Ingress resource is abnormal, where the abnormal warning information is used to warn the user that the Ingress resource is abnormal.
According to a further embodiment of the present invention, there is also provided a computer-readable storage medium having a computer program stored thereon, wherein the computer program is arranged to perform the steps of any of the above method embodiments when executed.
According to yet another embodiment of the present invention, there is also provided an electronic device, including a memory in which a computer program is stored and a processor configured to execute the computer program to perform the steps in any of the above method embodiments.
According to the method and the device, the configuration information of the Ingress resource configured by the Namespace Namespace resource in the containerized application K8s is acquired by acquiring the routing configuration information of the gateway of the target application, wherein the Ingress resource and the Namespace resource both comprise tag information of the target application, the Namespace resource is used for resource isolation in K8s, the Ingress resource is used for flow distribution in K8s, and anomaly detection is carried out on the Ingress resource based on the routing configuration information of the gateway and the configuration information of the Ingress resource. And the management and maintenance of Ingress resources are realized. Therefore, the monitoring problem of Ingress resources in the related technology can be solved, and the effect of effectively monitoring the Ingress resources is achieved.
Drawings
Fig. 1 is a block diagram of a hardware structure of a mobile terminal of a resource abnormality detection method according to an embodiment of the present invention;
FIG. 2 is a flow diagram of a method of anomaly detection of a resource according to an embodiment of the present invention;
FIG. 3 is an overall flow diagram according to an embodiment of the invention;
FIG. 4 is a flow chart of creating a gateway according to an embodiment of the present invention;
FIG. 5 is a flow diagram of creating Ingress resources according to an embodiment of the invention;
FIG. 6 is a flow diagram of anomaly detection according to an embodiment of the present invention;
fig. 7 is a block diagram of a resource abnormality detection apparatus according to an embodiment of the present invention.
Detailed Description
Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings in conjunction with the embodiments.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.
The method embodiments provided in the embodiments of the present application may be executed in a mobile terminal, a computer terminal, or a similar computing device. Taking an example of the method running on a mobile terminal, fig. 1 is a block diagram of a hardware structure of the mobile terminal of the method for detecting resource abnormality according to the embodiment of the present invention. As shown in fig. 1, the mobile terminal may include one or more (only one shown in fig. 1) processors 102 (the processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA), and a memory 104 for storing data, wherein the mobile terminal may further include a transmission device 106 for communication functions and an input-output device 108. It will be understood by those skilled in the art that the structure shown in fig. 1 is only an illustration, and does not limit the structure of the mobile terminal. For example, the mobile terminal may also include more or fewer components than shown in FIG. 1, or have a different configuration than shown in FIG. 1.
The memory 104 may be used to store a computer program, for example, a software program and a module of application software, such as a computer program corresponding to the resource abnormality detection method in the embodiment of the present invention, and the processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, so as to implement the method described above. The memory 104 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory located remotely from the processor 102, which may be connected to the mobile terminal over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The transmission device 106 is used for receiving or transmitting data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of the mobile terminal. In one example, the transmission device 106 includes a Network adapter (NIC), which can be connected to other Network devices through a base station so as to communicate with the internet. In one example, the transmission device 106 may be a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.
In this embodiment, a method for detecting an abnormality of a resource is provided, and fig. 2 is a flowchart of the method for detecting an abnormality of a resource according to the embodiment of the present invention, as shown in fig. 2, the flowchart includes the following steps:
step S202, obtaining the route configuration information of the gateway of the target application;
step S204, acquiring configuration information of Ingress resources configured by Namespace Namespace resources in the containerized application K8S, wherein the Ingress resources and the Namespace resources both comprise tag information of a target application, the Namespace resources are used for resource isolation in K8S, and the Ingress resources are used for flow distribution in K8S;
step S206, based on the route configuration information of the gateway and the configuration information of the Ingress resource, carrying out abnormity detection on the Ingress resource.
The executing agent of the above steps may be a server (e.g., a management server) or the like, but is not limited thereto.
In this embodiment, the Namespace is a resource in kubernets (abbreviated as K8s), resource isolation in different spaces can be achieved through the Namespace, and Ingress is a resource belonging to the Namespace. Different target applications under the current service can have a plurality of Namespaces, and each target application only concerns the resources under the Namespace in the target application. In this embodiment, each Namespace includes tag data of a target application, so as to implement division of Namespace target application dimensions, because Ingress itself belongs to Namespace, as long as Ingress also includes target application tag data the same as Namespace, Ingress can also implement division of target application dimensions, and gateway monitoring service can directly perform classification monitoring according to tag data, without being limited by dynamic addition and deletion of Namespace itself.
As shown in fig. 3, the overall process of this embodiment includes the following steps:
s301, creating Ingress resources in Namespace with different target application tags, and adding tags (consistent with Namesaccce) of the target applications to Ingress during creation.
S302, different Apisix-Ingress-controllers, monitor Ingress of different tags.
S303, Apisix-Ingress-controller converts the monitored Ingress configuration into an api routing configuration request and synchronizes to Apisix-admin.
S304, the Apisix-admin receives the request and then persists the data in the etcd.
And S305, the Apisix-gateway is responsible for processing the real flow control according to the route configuration in the etcd.
S306, the application, the service and the browser outside the cluster access the service inside the cluster through the address port and the route exposed by the Apisix-gateway.
Through the steps, the configuration information of the Ingress resource configured by the Namespace Namespace resource in the containerized application K8s is obtained by obtaining the routing configuration information of the gateway of the target application, wherein the Ingress resource and the Namespace resource both comprise tag information of the target application, the Namespace resource is used for resource isolation in K8s, the Ingress resource is used for flow distribution in K8s, and anomaly detection is carried out on the Ingress resource based on the routing configuration information of the gateway and the configuration information of the Ingress resource. And the management and maintenance of Ingress resources are realized. Therefore, the monitoring problem of Ingress resources in the related technology can be solved, and the effect of effectively monitoring the Ingress resources is achieved.
In an exemplary embodiment, before obtaining the routing configuration information of the gateway of the target application, the method further includes:
sending first request information to a packet manager Helm; the first request information is used for requesting Helm to configure a gateway in the target application, and marking label information of the target application in a control unit in the Namespace resource.
In this embodiment, the gateway application is pulled up by means of a hell Charts packet that is mainstream in the industry; by modifying the open-source apisix palm package, the apisix supports item label configuration; and by modifying the relevant logic of the apisix, the function of the apisix is expanded, so that the gateway can carry out classified monitoring through the project label.
As shown in fig. 4, creating a gateway includes the steps of:
s401, the management service initiates first request information to a Helm service;
s402, pulling up the gateway in the specified target application;
s403, after receiving the request, Helm pulls up the gateway application according to the corresponding Helm packet, and simultaneously marks the corresponding target application label on the apisix-Ingress-controller, telling the controller to monitor only Ingress resources under Namespace with the corresponding label.
In an exemplary embodiment, before obtaining the configuration information of Ingress resource of Namespace resource configuration in the containerized application K8s, the method further includes:
receiving second request information of the user;
and establishing an Ingress resource in the Namespace resource based on the second request information, wherein the label information of the target application in the Ingress resource is set through the event processing application in the K8 s.
The embodiment is used for establishing Ingress resources, and a mechanism called Webhook exists in Kubernetes, and the mechanism can intercept resources in the resource establishment process through a responsibility chain mode, so that custom logic is added. Therefore, by using the mechanism, when Ingress is created, Namesspace data to which the Ingress belongs is obtained, and then item tag data in the Namesspace is added into the Ingress, so that the Ingress has item attributes.
As shown in fig. 5, the method specifically includes the following steps:
s501, a user creates Ingress resources in different classes of Namespace through a management service or a cluster background;
s502, target application category label information is carried in the Namespace, and Webhook monitors Ingress creation events to acquire Namespace label information where Ingress is located;
s503, Webhook sets Namespace tag information into Ingress, and the Ingress contains target application tag information.
In an exemplary embodiment, the performing exception detection on the Ingress resource based on the routing configuration information of the gateway and the configuration information of the Ingress resource includes:
adding the route configuration information in the configuration information of the Ingress resource to the route configuration information in the gateway, and determining N pieces of route configuration information, wherein N is a natural number greater than 1;
determining abnormal route configuration information from the N route configuration information;
and carrying out exception detection on the Ingress resource based on the exception routing information.
And sending abnormal alarm information to the user under the condition that the Ingress resource is determined to be abnormal, wherein the abnormal alarm information is used for warning the user that the Ingress resource is abnormal.
The embodiment is used for detecting whether Ingress resources are abnormal or not, and after the Apisix gateway is expanded in function, all routing rules in Ingress are added, so that the gateway contains all normal and abnormal (repeated and ineffective) routing configuration data, and then simple analysis is performed by combining the Ingress data in Kubernets, which Ingress are abnormal can be easily known, and subsequently, only when a user logs in, abnormal alarm data is pushed to the user.
As shown in fig. 6, the method specifically includes the following steps:
s601, the management service acquires all routing information from api-admin and discovers abnormal routing configuration;
s602, the management service acquires configuration information in Ingress from Kubernetes apiserver;
and S603, carrying out secondary analysis on the management service aggregated data, recording the existence of the problem Ingress, and pushing and informing the user after the user logs in the management service.
In conclusion, the embodiment enables users to manage and maintain Ingress resources more friendly, convenient and diversified. The user does not need to additionally sense the existence of the gateway and learn how the gateway is used, only needs to pay attention to the use management of Ingress in the original service, and learning cost is avoided. The method can be used for classified monitoring management of Ingress under different Namespace, supports dynamic addition and deletion of Namespace, dynamically enlarges and reduces the monitoring range on the premise that the gateway is not restarted, and enables gateway management and service expansion to be more flexible.
Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present invention or portions thereof contributing to the prior art may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (which may be a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.
In this embodiment, a resource abnormality detection apparatus is further provided, and the apparatus is used to implement the foregoing embodiments and preferred embodiments, and details of which have been already described are omitted. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.
Fig. 7 is a block diagram showing the structure of an abnormality detection apparatus for resources according to an embodiment of the present invention, as shown in fig. 7, the apparatus including:
a first obtaining module 72, configured to obtain the routing configuration information of the gateway of the target application;
a second obtaining module 74, configured to obtain configuration information of an Ingress resource configured by a Namespace resource in a containerized application K8s, where the Ingress resource and the Namespace resource both include tag information of the target application, the Namespace resource is used for resource isolation in the K8s, and the Ingress resource is used for traffic distribution in the K8 s;
a first detecting module 76, configured to perform anomaly detection on the Ingress resource based on the routing configuration information of the gateway and the configuration information of the Ingress resource.
In an exemplary embodiment, the apparatus further includes: the first sending module is used for sending first request information to a packet manager Helm before the route configuration information of the gateway of the target application is acquired;
the first request information is used for requesting the Helm to configure the gateway in the target application, and marking tag information of the target application in a control unit in the Namespace resource.
In an exemplary embodiment, the apparatus further includes:
the first receiving module is used for receiving second request information of a user before acquiring configuration information of Ingress resources configured by Namespace resources in the containerized application K8 s;
a first establishing module, configured to establish the Ingress resource in the Namespace resource based on the second request information, where tag information of a target application in the Ingress resource is set by the event processing application in K8 s.
In an exemplary embodiment, the first detecting module includes:
a first determining unit, configured to add routing configuration information in the configuration information of the Ingress resource to routing configuration information in the gateway, and determine N pieces of routing configuration information, where N is a natural number greater than 1;
a second determining unit, configured to determine abnormal routing configuration information from the N routing configuration information;
and a first detection unit, configured to perform anomaly detection on the Ingress resource based on the anomaly routing information.
In an exemplary embodiment, the apparatus further includes:
the first sending module is configured to send abnormal warning information to a user when it is determined that the Ingress resource is abnormal, where the abnormal warning information is used to warn the user that the Ingress resource is abnormal.
It should be noted that the above modules may be implemented by software or hardware, and for the latter, the following may be implemented, but not limited to: the modules are all positioned in the same processor; alternatively, the modules are located in different processors in any combination.
Embodiments of the present invention also provide a computer-readable storage medium having a computer program stored thereon, wherein the computer program is arranged to perform the steps of any of the above-mentioned method embodiments when executed.
In the present embodiment, the above-described computer-readable storage medium may be configured to store a computer program for executing the above steps.
In an exemplary embodiment, the computer readable storage medium may include, but is not limited to: various media capable of storing computer programs, such as a usb disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk.
Embodiments of the present invention also provide an electronic device comprising a memory having a computer program stored therein and a processor arranged to run the computer program to perform the steps of any of the above method embodiments.
In an exemplary embodiment, the electronic apparatus may further include a transmission device and an input/output device, wherein the transmission device is connected to the processor, and the input/output device is connected to the processor.
In an exemplary embodiment, the processor may be configured to execute the above steps by a computer program.
For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary embodiments, and details of this embodiment are not repeated herein.
It will be apparent to those skilled in the art that the various modules or steps of the invention described above may be implemented using a general purpose computing device, they may be centralized on a single computing device or distributed across a network of computing devices, and they may be implemented using program code executable by the computing devices, such that they may be stored in a memory device and executed by the computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into various integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the principle of the present invention should be included in the protection scope of the present invention.
Claims (8)
1. A method for detecting an abnormality of a resource, comprising:
acquiring routing configuration information of a gateway of a target application;
acquiring configuration information of Ingress resources configured by Namespace Namespace resources in a containerized application K8s, wherein the Ingress resources and the Namespace resources both comprise tag information of the target application, the Namespace resources are used for resource isolation in K8s, and the Ingress resources are used for flow distribution in K8 s;
and carrying out anomaly detection on the Ingress resource based on the routing configuration information of the gateway and the configuration information of the Ingress resource.
2. The method of claim 1, wherein prior to obtaining routing configuration information for a gateway of a target application, the method further comprises:
sending first request information to a packet manager Helm;
the first request information is used for requesting the Helm to configure the gateway in the target application, and marking label information of the target application in a control unit in the Namespace resource.
3. The method according to claim 1, wherein before obtaining configuration information of Ingress resource of Namespace resource configuration in containerized application K8s, the method further comprises:
receiving second request information of the user;
establishing the Ingress resource in the Namespace resource based on the second request information, wherein the label information of the target application in the Ingress resource is set through the event processing application in the K8 s.
4. The method according to claim 1, wherein the performing exception detection on the Ingress resource based on the routing configuration information of the gateway and the configuration information of the Ingress resource comprises:
adding the route configuration information in the configuration information of the Ingress resource to the route configuration information in the gateway, and determining N route configuration information, wherein N is a natural number greater than 1;
determining abnormal routing configuration information from the N routing configuration information;
and carrying out anomaly detection on the Ingress resource based on the anomaly routing information.
5. The method of claim 4, further comprising:
and sending abnormal alarm information to the user under the condition that the Ingress resource is determined to be abnormal, wherein the abnormal alarm information is used for warning the user that the Ingress resource is abnormal.
6. An apparatus for detecting an abnormality in a resource, comprising:
the first acquisition module is used for acquiring the routing configuration information of the gateway of the target application;
a second obtaining module, configured to obtain configuration information of an Ingress resource configured by a Namespace resource in a containerized application K8s, where the Ingress resource and the Namespace resource both include tag information of the target application, the Namespace resource is used for resource isolation in the K8s, and the Ingress resource is used for traffic distribution in the K8 s;
and the first detection module is used for carrying out exception detection on the Ingress resource based on the routing configuration information of the gateway and the configuration information of the Ingress resource.
7. A computer-readable storage medium, in which a computer program is stored, which computer program, when being executed by a processor, carries out the method of any one of claims 1 to 5.
8. An electronic device comprising a memory and a processor, wherein the memory has stored therein a computer program, and wherein the processor is arranged to execute the computer program to perform the method of any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210138920.4A CN114461501A (en) | 2022-02-15 | 2022-02-15 | Resource abnormality detection method and device, storage medium, and electronic device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210138920.4A CN114461501A (en) | 2022-02-15 | 2022-02-15 | Resource abnormality detection method and device, storage medium, and electronic device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114461501A true CN114461501A (en) | 2022-05-10 |
Family
ID=81414578
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210138920.4A Pending CN114461501A (en) | 2022-02-15 | 2022-02-15 | Resource abnormality detection method and device, storage medium, and electronic device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114461501A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115277386A (en) * | 2022-06-30 | 2022-11-01 | 中盈优创资讯科技有限公司 | Registration center management method based on APISIX |
-
2022
- 2022-02-15 CN CN202210138920.4A patent/CN114461501A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115277386A (en) * | 2022-06-30 | 2022-11-01 | 中盈优创资讯科技有限公司 | Registration center management method based on APISIX |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110535831B (en) | Kubernetes and network domain-based cluster security management method and device and storage medium | |
| US11177999B2 (en) | Correlating computing network events | |
| US20190266537A1 (en) | Systems and methods for incident queue assignment and prioritization | |
| EP3072260B1 (en) | Methods, systems, and computer readable media for a network function virtualization information concentrator | |
| EP2284757A1 (en) | Security vulnerability information aggregation | |
| US10944655B2 (en) | Data verification based upgrades in time series system | |
| US20080162690A1 (en) | Application Management System | |
| US20230403215A1 (en) | Systems and methods of monitoring and controlling remote assets | |
| CN112328448A (en) | Zookeeper-based monitoring method, monitoring device, equipment and storage medium | |
| US20170163505A1 (en) | Application centric network experience monitoring | |
| KR102118487B1 (en) | Automatic quality inspection system and method of container based application for ci/cd | |
| CN114461501A (en) | Resource abnormality detection method and device, storage medium, and electronic device | |
| US11431575B2 (en) | Network system, topology management method, and program | |
| CN114398397A (en) | Data processing method, device, storage medium and system | |
| CN112448833B (en) | Multi-management-domain communication method and device | |
| WO2013161522A1 (en) | Log collection server, log collection system, log collection method | |
| CN114756301A (en) | Log processing method, device and system | |
| US10897401B2 (en) | Determining the importance of network devices based on discovered topology, managed endpoints, and activity | |
| CN113032054A (en) | Service execution method, device, storage medium and electronic device | |
| CN113778780A (en) | Application stability determination method and device, electronic equipment and storage medium | |
| CN112437146A (en) | Equipment state synchronization method, device and system | |
| CN110445628A (en) | A kind of task control method and device based on NGINX | |
| US20240073146A1 (en) | Transaction-level network policies for online applications | |
| US20230370331A1 (en) | Parameter value setting system, control method of parameter value setting system and program | |
| CN115438287A (en) | Method for generating chart without browser mode, electronic device and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |