Service graph highlights missing nodes and links

[0025] In order to read the various embodiments described below, it is useful for the following descriptions of the sections and their respective contents described:

[0026] Part A describes a network environment and may be used for embodiments described herein, the computing environment of the embodiments;

[0027] Part B describes for delivering a computing environment to embodiments of systems and methods of remote user;

[0028] Part C describes the application delivery controller for the embodiment virtualization systems and methods;

[0029] Section D describes embodiments for providing trunked system and method of device architecture environment; and

[0030] Part E The embodiments are described based on FIG service platforms and technologies; and

[0031] Section F describes embodiments of systems and method for reproducing a plurality of micro FIG services and services.

[0032] A. Network and computing environment

[0033] refer to Figure 1A , It depicts an exemplary network environment 100. Network environment 100 may include -104n (collectively referred to as network 104) via one or more networks 104 (1) and one or more servers 106 (1) -106 (n) (also generally referred to as the remote machine 106 or a communication server 106) or more clients 102 (1) -102 (n) (also generally referred to as a local client machine 102 or 102). In some embodiments, client 102 via one or more devices 200 (1) -200n (collectively referred to as 200 or gateway device 200) with the communication server 106.

[0034] Although Figure 1A Embodiment illustrated shows one or more networks 104 between the clients 102 and server 106, in other embodiments, the client 102 and server 106 may be on the same network 104. Various networks 104 may be the same type of network or different types of networks. For example, in some embodiments, the network 104 (1) may be a network such as a local area network (LAN) or a company's private network, and the network 104 (2) and / or network 104 (n) may be a wide area network (WAN) or public network Internet. In other embodiments, the network 104 (1) and the network 104 (n) may be a private network. Network 104 may employ one or more types of physical networks and / or network topology, such as a wired and / or wireless networks, and may employ one or more communication transport protocols, such as Transmission Control Protocol (TCP), Internet Protocol (IP ), user datagram protocol (UDP) or other similar agreements.

[0035] like Figure 1A , One or more network devices 200 may be located at various points in the environment 100 or each communication path. For example, device 200 may be deployed between the two networks 104 (2) (1) and 104, and apparatus 200 may communicate with each other to work in conjunction to accelerate network traffic between client 102 and server 106, for example. In other embodiments, the device 200 may be located on network 104. For example, apparatus 200 may be implemented as part of the client 102 and / or one of the server 106. In one embodiment, the device 200 may be implemented as a network device, such as the Citrix network of Fort Lauderdale, Florida, Citrix Systems, Inc. sold (formerly )product.

[0036] like Figure 1A, One or more servers 106 may operate as a server farm 38. Servers in the farm 38 can be grouped logically 106, and 102 from the client and / or server 106, in other geographically co-located (e.g., locally) or geographically dispersed (e.g., cloud-based). In one embodiment, server cluster 38 represents one or more clients 102 (e.g., an application server) executing one or more applications, and other uses are possible, such as a file server, a gateway server, proxy server, or other similar the server uses. The client 102 may seek to access hosted applications on the server 106.

[0037] like Figure 1A , In some embodiments, apparatus 200 may include one or more additional devices (such as a WAN optimization appliance 205 (1) -205 (n), commonly referred to as a WAN optimization appliance 205), its place, or its communicate. For example, WAN optimization appliance 205 may accelerate, caching, compression, or otherwise improve or optimize network traffic (such as to and / or from a WAN connection) performance, operation, flow control or quality of service, such as a WAN optimization file services (WAFS), acceleration server message block (SMB) or common Internet file system (CIFS). In some embodiments, the device 205 may be a performance enhancing agent or a WAN optimization controller. In one embodiment, the device 205 may be implemented as Fort Lauderdale, Florida, Citrix Systems, Inc. Sales of Citrix SD-WAN products.

[0038] refer to Figure 1B , Shows an example of a network environment for delivering on the client 102 and / or operating a computing environment a network 100 '. like Figure 1B , The server 106 may include one or more clients to a conveyor 102 conveying computing system environment, application and / or data file 190. The client 102 may include a client agent 120 and the computing environment 15. The computing environment 15 may execute or access operations, or the processing application 17 in the data file 16. The computing environment 15, application 16, and / or data file 17 can be delivered via the appliance 200 and / or server 106.

[0039] Acceleration computing device 200 may all or part of the environment 15 to delivery client 102, through the application delivery system 190, for example. For example, the device 200 and may be accelerated by the application process stream application data files from the data center to a remote transport user's location via transport layer traffic between a client 102 and a server accelerator 106. This acceleration may be provided by one or more techniques, such as: 1) transport layer connection pooling, 2) transport layer connection multiplexing, 3) transport control protocol buffering, 4) compression and 5) caching or other techniques . Device 200 may also provide load balancing server 106 to process requests from client 102, acts as a proxy or access server to provide access to one or more servers 106 to provide security and / or act as a Client 102 and server 106 of firewall between providing domain name service (DNS) resolution, provide one or more virtual servers or virtual internet protocol servers, and / or provide a connection from a secure virtual private network client 102 to a server 106 (the VPN), such as a secure sockets word layer (SSL) VPN connection and / or provide encryption and decryption operations.

[0040] Application delivery management system 190 may be based on authentication and authorization policies applied policy engine 195, the calculated delivered to the remote user, or other user (e.g., client 102) 15 environment. Any applications and devices (e.g., client 102) from a remote network connection the user may obtain a computing environment and access to server stored data files. For example, the device 200 may request an application and data files from the server 106. In response to the request, the application delivery system 190 and / or server 106 may deliver the application and data file to the client 102, e.g., via an application stream to the computing environment on the client 102 15 operation, or via a remote display protocol or or otherwise via remote computing-based server-based. In one embodiment, the application delivery system 190 may be implemented as Citrix Workspace Suite Citrix Systems Inc. TM Any part of such applications and Citrix virtual desktops (formerly known as and.

[0041] Policy engine 195 can control and manage access to applications, execution and delivery. For example, policy engine 195 may determine that a user or client 102 may access one or more applications and / or how to apply or delivered to a user client 102, such as a server-based computing, streaming or local delivery to a client 120 for local execution.

[0042] For example, in operation, the client 102 may request the application (e.g., application 16 ') is performed and the server application delivery system 106 190, for example, based on 102 received from the client credentials and the related credential associated policy engine 195 applied user policies to determine how to execute the application 16 '. For example, the application delivery system 190 may enable the client 102 to receive application output data generated by execution of the application on the server 106 enables the client 102 can be received from the server 106 to the local execution of the application after the application, or may be via a network 104 streamed to the client application 102. For example, in some embodiments, the application may be a server-based or a remote-based application executed on behalf of the client 102 on the server 106. Server 106 may use a thin - client or remote display protocol, Independent Computing Architecture (ICA) Fort Lauderdale, Florida, Citrix Systems, Inc., such as a protocol, display output to the client 102. Application may be any application related to realtime data communications with (streaming graphics, for applications such as streaming video and / or audio or other data), or the delivery or application hosting service or remote desktop workspace (e.g., base facilities as a service (IaaS), Desktop as a service (DaaS), the workspace as a service (WaaS), software as a service (SaaS) or platform as a service (PaaS)).

[0043] Server 106 may include one or more performance monitoring agent 197 or service. In some embodiments, it may be dedicated to one or more servers 106 to perform performance monitoring. Performance monitoring data may be used to collect, aggregate, analyze, and report management is performed, for example by software, hardware, or a combination thereof. Performance monitoring may include one or more agents, for the client 102 (e.g., the client agent 120), server 106 (e.g., agent 197) or device 200 and / or 205 (not shown proxy) to monitor the execution , measurement and data collection activities. Typically, the monitoring agent (e.g., 120 and / or 197) transparent (e.g., the background) is performed on any user applications and / or devices. In some embodiments, the monitoring agent 197 includes Fort Lauderdale, Florida, Citrix Systems, Inc. Citrix called analysis of any product or Citrix application delivery management examples.

[0044] Monitoring agent 120 or 197 may occur during operation of the data network environment 100 at a predetermined frequency in real time to monitor, measure, collection and / or analysis and based on a given event. Monitoring agent 102 may monitor network 104, devices 200 and / or 205 and / or server 106 hardware, software and / or resource consumption and / or performance of communication resources the client. For example, transport layer connection such as a network connection, network delay, bandwidth utilization, end-user response time, application usage and performance, and a session connection to the application, cache usage, memory usage, processor usage, memory use duration, the database transaction, the client and / or server utilization, user activity, user activity, application crashes, errors or suspended, the time required to log in to the application, server, or application delivery system, and / or other properties conditions and metrics can be monitored.

[0045] Monitoring agents 120 and 197 may provide application performance management for the application delivery system 190. For example, based on one or more conditions or performance metrics are monitored, it can be dynamically (e.g., periodically or in real time) adjusting the application delivery system 190, to optimize the application server 106 to the client 102 based on transport network performance and environmental conditions .

[0046] In the described embodiment, client 102, server 106 and devices 200 and 205 may be deployed as and / or executed on any type and form of computing device, such as any desktop computer, laptop computer, or through at least one the mobile device communication network and performing the operations described herein. For example, client 102, server 106 and / or device 200 and 205 may each correspond to a single computer, multiple computers or a distributed computer network, such as Figure 1C The computer 101 shown.

[0047] like Figure 1C , The computer 101 may include one or more processors 103, a volatile memory 122 (e.g. RAM), non-volatile memory 128 (e.g., one or more hard disk drives (HDD) or other magnetic or optical storage medium, one or more solid state drives (the SSD) (such as a solid-state flash drive or other storage media), one or more mixing of magnetic and solid state drives and / or one or more virtual storage volume (such as a cloud storage), or such physical storage volumes and virtual storage volume or a combination of an array), a user interface (UI) 123, one or more communication interface 118 and a communication bus 150. The user interface 123 may include a graphical user interface (GUI) 124 (e.g., a touch screen, display, etc.) and one or more input / output (I / O) device 126 (e.g., a mouse, a keyboard, etc.). The nonvolatile memory 128 stores an operating system 115, one or more applications 116 and data 117, such as operating system 115 such that computer instructions and / or application 116 executed by processor 103 out of volatile memory 122. Input means for inputting data may be used in GUI 124 or 126 receives the data from the I / O device. Various elements of the computer 101 may communicate via a communication bus 150. like Figure 1C The computer 101 shown only shown as an example, because the client 102, server 106 and / or 200 and 205 can be any computing or processing environment capable of using the device as described herein may have the appropriate hardware operation and / or any type of software machine or group of machines to achieve.

[0048] The processor 103 may be one or more programmable processors, the processor executing one or more computer programs to perform functions of the system. As used herein, the term "processor" to perform the functions described, the electronic circuit operation or sequence. Function, operation or sequence of operations may be hard-coded into an electronic circuit or stored in the memory means by instructions soft-coded. "Processor" may use digital or analog signal values ​​to perform the function, operation or sequence of operations. In some embodiments, a "processor" may be embodied as one or more application specific integrated circuits (ASIC), a microprocessor, a digital signal processor, microcontroller, field programmable gate arrays (the FPGA), programmable logic array (PLA), a multi-core processor or general purpose computer with associated memory. "Processor" may be an analog, digital or mixed signal. In some embodiments, a "processor" may be one or more physical processors or one or more "virtual" (e.g., remotely located or "cloud") processor.

[0049] Communication interface 118 may include one or more interfaces to enable the computer 101 can access a computer network connection such as LAN, WAN or the Internet through a variety of wired and / or wireless or cellular.

[0050]In the described embodiment, the first computing device 101 can execute an application on behalf of the client computing device (e.g., client 102), which can execute a virtual machine that provides an application in its representative user or client computing device ( For example, client 102) execution sessions, such as hosting desktop sessions, can perform terminal service sessions to provide managed desktop environments, or access to computing environment, computing environment includes one or more of the following: one or more An application, one or more desktop applications, and one or more applications that can be performed therein.

[0051] B. Device architecture

[0052] figure 2 An exemplary embodiment of the device 200 is shown. As described herein, device 200 can be implemented as a server, gateway, router, switch, bridge, or other type of calculation or network device. like figure 2 As shown, the embodiment of the device 200 may include a hardware layer 206 and a software layer 205, and the software layer 205 is divided into user space 202 and kernel space 204. The hardware layer 206 provides a hardware element, the kernel space 204, and the service in the user space 202 executes based on these hardware elements, and allows the kernel space 204 and the program and service within the user space 202 to transmit data internally and outside the device 200. . like figure 2 As shown, the hardware layer 206 can include one or more processing unit 262 for performing software programs and services, memory 264 for storing software and data, and is used to transmit and receive data through network port 266, and for use in Encryption and decryption data (eg, encrypted processor 260 related to a security socket layer (SSL) or transport layer security (TLS) processing of data over network transmission and received data.

[0053] Operating system assignment, management, or otherwise manipulating the system memory into kernel space 204 and user space 202. The kernel space 204 is retained for running the kernel 230, including any device driver, kernel extension, or other kernel related software. As is known to those skilled in the art, the core 230 is the core of the operating system, and provides access, control and management of the resources and hardware related elements of the application 104. The kernel space 204 can also include multiple network services or processes that work together with the cache manager 232.

[0054] Device 200 may include one or more network stack 267, such as a TCP / IP-based stack for communicating with client 102, server 106, network 104, and / or other devices 200 or 205. For example, device 200 can establish and / or terminate one or more transport layers between client 102 and server 106. Each network stack 267 can include buffer 243 for queuing one or more network packets to supply device 200.

[0055] The kernel space 204 can include a cache manager 232, a packet engine 240, an encryption engine 234, a policy engine 236, and a compression engine 238. In other words, one or more of the processes 232, 240, 234, 236, and 238 operate in the kernel address space of the operating system of the device 200, which can reduce the data transaction and / or kernel mode and user mode of the entering and exit memory. The number of context switches, for example, because the data obtained in the kernel mode may not need to be delivered or copied to the user process, thread, or user-level data structure.

[0056] The cache manager 232 can copy data stored in other original data or previous calculations, generated or transmitted data to reduce data access time. In some embodiments, the cache memory can be a data object in the memory 264 of the device 200, or may be a physical memory having a faster access time than the memory 264.

[0057] Policy engine 236 can include a statistical engine or other configuration mechanism to allow user identification, designation, definition, or configure a cache policy and access, control, and management of objects, data or content cached by the device 200 cache, and define or configure Security, network traffic, network access, compression, or other functions performed by device 200.

[0058] Encryption engine 234 can handle any security related protocols such as SSL or TLS. For example, encryption engine 234 can encrypt and decrypt network packets or any part thereof via device 200, can be set, for example, between client 102, server 106, and / or other devices 200 or 205, and establish an SSL, TLS, or other secure connection. . In some embodiments, the encryption engine 234 can use a tunneling protocol to provide a VPN between client 102 and server 106. In some embodiments, the encryption engine 234 communicates with the encryption processor 260. Compression Engine 238 compresses network packets between client 102 and server 106 and / or between one or more devices 200.

[0059] The packet engine 240 can manage the core level processing of the packets received and transmitted via the network stack 267 via the network stack 267 to transmit and receive network packets via network port 266. The packet engine 240 can operate with the encryption engine 234, the cache manager 232, the policy engine 236, and the compression engine 238, for example, to perform encryption / decryption, traffic management, such as request grade content switching, and request grade cache redirection, and Data compression and decompression.

[0060] The user space 202 is a memory area or part of an operating system used by a user mode or a program running in a user mode. User mode Applications may not directly access the kernel space 204, but use service calls to access kernel services. User space 202 can include a graphical user interface (GUI) 210, a command line interface (CLI) 212, a shell service 214, a health monitor 216, and a daemon 218. The GUI 210 and CLI 212 enable system administrators or other users to interact with the device 200 and control the operation of the device 200, such as the operating system via the device 200. Shell service 214 includes a program, service, task, process, or executable instruction to support the user's interaction via the GUI 210 and / or CLI 212 and device 200.

[0061] Health Monitor 216 monitors, checks, reports and ensures that the network system is running normally and the user is receiving the requested content over the network, such as by monitoring device 200. In some embodiments, the health monitor 216 intercepts and checks any network traffic passed through the device 200. For example, the health monitor 216 can correspond to one or more interfaces of the encryption engine 234, the cache manager 232, the policy engine 236, the compression engine 238, the packet engine 240, the daemon 218, and the casing service 214 to determine the device 200. Any part of the status, condition, operating conditions or health. In addition, the health monitor 216 can determine if the program, process, service, or task is active and is currently running, check the status, errors, or historical logs provided by any program, process, service, or task to determine any part of the device 200. Any condition, state or error. In addition, the health monitor 216 can measure and monitor any applications, procedures, processes, services, tasks, or threads performed on device 200.

[0062] The daemon 218 is running continuously or runs in the background and proceeded by the periodic service request received by the device 200. In some embodiments, the daemon can forward the request to other programs or processes regarding the situation, such as another daemon 218.

[0063] As described herein, device 200 can reduce server 106 by opening and maintaining these connections to one or more transport layers of each server 106 to allow clients to access server 106 via the Internet (eg, "connect pool"). Due to the repeated opening and closing the transport layer connection caused by the transport layer connection of the client 102, a large amount of processing is caused. To perform a connection pool, device 200 can switch or multiplex communication by modifying the serial number and the confirmation number (eg, "connection multiplex") at the transport layer protocol level. The device 200 can also provide exchange or load balancing between the client 102 and the server 106.

[0064] As described herein, each client 102 can include a client agent 120 for establishing and exchange communication with device 200 and / or server 106 via network 104. Client 102 may have already installed and / or execute one or more applications communicating with network 104. The client agent 120 can intercept network communication from the network stack used by one or more applications. For example, client agent 120 can intercept network communication in any point in the network stack and redirect network communication to the client agent 120 desired, managed or controlled, for example, to intercept the transport layer, and redirect the transport layer connection To the IP address and port controlled or managed by the client agent 120. Therefore, the client agent 120 can transparently intercept any protocol layer below the transport layer, such as a network layer, and any protocol layer above the transport layer, such as a session, representation, or application layer. The client agent 120 can be provided with the transport layer interface to protect, optimize, accelerate, route, or load balancing any of the protocols that are carried by the transport layer via the transport layer.

[0065] In some embodiments, the client agent 120 is implemented as an independent computing architecture (ICA) client developed by Sijie System Co., Ltd., Florida Lauderdale. Client agent 120 can perform acceleration, streaming, monitoring, and / or other operations. For example, client agent 120 can accelerate application from server 106 to client 102. The client agent 120 can also perform endpoint detection / scanning and collect endpoint information about client 102 for device 200 and / or server 106. Device 200 and / or server 106 can use the collected information to determine and provide access, authentication, and authorization control of the connection of the client to network 104. For example, client agent 120 can identify and determine one or more client-side properties, such as: operating system and / or operating system version, operating system service pack, running service, processes, files, customers The presence or version of various applications of the machine, such as antivirus, firewall, security, and / or other software.

[0066] C. System and method for providing virtualization application delivery controller

[0067] Reference now image 3 The block diagram of the virtualization environment 300 is shown. As shown, the computing device 302 in the virtualization environment 300 includes a virtualization layer 303, a management program layer 304, and a hardware layer 307. The management program layer 304 includes one or more management programs (or virtualization manager) 301, which assign and manage at least one virtual machine (VM) (for example, one of VM 306) performed in the virtualization layer 303. Access to multiple physical resources in layer 307 (e.g., physical processor 321 and physical disc 328). Each VM 306 can include allocated virtual resources, such as virtual processors 332 and / or virtual disks 342, as well as virtual resources, such as virtual memory and virtual network interfaces. In some embodiments, at least one of the VM 306 can include a control operating system communication with the management program 301 and is used to perform an application for managing and configuring other VMs (eg, customer operating system 310) on the configuration device 302 (eg, 305).

[0068] In general, the management program 301 can provide virtual resources to the operating system of the VM 306 in any manner that simulates an operating system accessible to the physical device. Therefore, the management program 301 can be used to simulate virtual hardware, dividing physical hardware, virtualized physical hardware, and virtual machines that perform access to computing environments. In the schematic embodiment, the management program 301 can be implemented as a Citrix management program provided by Sijie System Co., Ltd., Florida Lauderdale. In a schematic embodiment, device 302 performing a management program that creates a virtual machine platform that can be performed on it thereon is referred to as a host server 302.

[0069]The management program 301 can create one or more VM 306, the operating system (eg, control operating system 305 and / or customer operating system 310) therein. For example, the hypervisor 301 loads a virtual machine image to create a VM 306 to perform an operating system. The management program 301 can present the abstraction of the hardware layer 307 to the VM 306, and / or control how the hardware layer 307 is presented to the VM 306. For example, management program 301 can manage resource pools distributed across multiple physical computing devices.

[0070] In some embodiments, one of the VM 306 (for example, a VM performing control operating system 305) can manage and configure other VM 306, such as by managing VM execution and / or terminating and / or managing virtual resources to VM allocation. In various embodiments, the VM can communicate with the hypervisor 301 and / or other VM via, for example, one or more application programming interfaces (APIs), shared memory, and / or other technical communications.

[0071] In general, VM 306 can provide access to the user of the device 302 to access the resources within the virtualization computing environment 300, such as one or more programs, applications, documents, files, desktops, and / or computing environments, or other resources. In some embodiments, VM 306 can be implemented as a full virtualized VM (e.g., hardware virtual machine or HVM) that they are virtual machines. In other embodiments, VM can know that it is a virtual machine, and / or the VM can be implemented as a semi-virtualized (PV) VM.

[0072] Although in image 3 A single virtualization device 302 is shown, but the virtualization environment 300 can include a plurality of networked devices in the system, at least one physical host execute a virtual machine. The device that the VM executed thereon can be referred to as a physical host and / or host. For example, device 200 can be implemented additionally or alternatively in virtualization environments 300 such as client 102, server 106, or device 200. The virtual device can provide a function similar to that of the device 200 for availability, performance, health monitoring, cache, and compression, connection multiplexing and poolization and / or security processing (for example, firewall, VPN, encryption / decryption) Wait).

[0073] In some embodiments, the server can execute multiple virtual machines 306, for example, on each of the cores and / or multiprocessor devices of the multi-core processing system. For example, although it is generally displayed in this article "processor" (eg, Figure 1C , 2 In 3), one or more processors can be implemented as a single core or multi-core processor to provide multi-thread, parallel architecture, and / or multi-core architecture. Each processor and / or core may have or use a distribution or distributing memory that can be accessed by the processor / nuclear access, and / or can have or using a common or by multiple processors / Nuclear sharing and accessible memory. This architecture allows for operation, tasks, load, or network traffic distributions across one or more processors and / or one or more cores (eg, through functional parallelism, data parallelism, stream-based data parallelism, etc.) .

[0074] Further, instead of (or other than this) the function of the core implemented in the form of a physical processor / core, such a function can be implemented in a virtualization environment (eg, 300) on the client 102, server 106, or device 200. This makes this function to be implemented across multiple devices (such as a cluster, server group, or network of computing devices, etc.). Various processors / cores can interface or communicate with multiple interface techniques (such as nuclear messaging, shared memory, kernel API, etc.).

[0075] In an embodiment in which multiple processors and / or multiple processor cores are employed, the described embodiments can distribute data packets between nuclear or processors, such as to balance the cross-core stream. For example, the packet distribution can be based on the function of each core, the source address, and the destination address of the destination address, and / or whether the load on the relevant core is higher than the predetermined threshold; the load on the relevant core is lower than the predetermined threshold; The load is smaller than the load on the other core; or can be used to partially determine any other metrics that forward the data packets to where the load is forwarded.

[0076] For example, a receiving side adjustment (RSS) can be used to distribute data packets between the core or processes to use multiple processor / cores in the network to process packets. RSS typically allows processing across multiple processor / core balanced packets while maintaining the orderly delivery of the packet. In some embodiments, RSS can use a hash scheme to determine the core or processor for processing the packet.

[0077] RSS can generate a hash from any type and form, such as a value sequence. This value sequence can include any part of the network packet, any header, field, or payload, such as a network packet, and includes any information tuple, such as an address, and port associated with the network packet or data stream. Hash results or any part thereof can be used to identify processors, cores, engines, etc. for, for example, via a hash table, an indirect table, or other mapping technology distribution network packet.

[0078] D. System and method for providing distributed cluster architecture

[0079] Although in Figure 1A and 1B It is shown as a single device, but device 200 can be implemented as one or more distributed or cluster devices. A separate computing device or device can be referred to as a node of a cluster. The centralized management system can perform load balancing, distribution, configuration, or other tasks to allow nodes to operate as a single computing system. Such clusters can be considered a single virtual device or computing device. Figure 4 A block diagram of a schematic computing device cluster or device cluster 400 is shown. Multiple device 200 or other computing device (eg, a node) can be added to a single cluster 400. The cluster 400 can operate as an application server, a network storage server, a backup service, or any other type of computing device to perform a number of functions of device 200 and / or 205.

[0080] In some embodiments, each device 200 of the cluster 400 can be implemented as a multiprocessor and / or multi-core device, as described herein. Such an embodiment may use a two-layer distribution system, and if the cluster distributes the packet to the cluster, and each node distributes the packets / core of the node, there is a device. In many embodiments, one or more device 200 of the cluster 400 can be physically packet or approacible to each other, such as a set of blade servers or racks in a given chassis, rack, / or data center. Device. In some embodiments, one or more device 200 of the cluster 400 can be geographically distributed, and the device 200 is physically or geographically not in the same location. In such an embodiment, geographically remote devices can be connected by a dedicated network connection and / or a VPN. In a geographically distributed embodiment, the load balancing can also take into account the communication delay between geographically remote devices.

[0081] In some embodiments, cluster 400 can be considered to be virtual devices that are grouped via common configuration, management, and purpose, not as a physical group. For example, a device cluster may include a plurality of virtual machines or processes executed by one or more servers.

[0082] like Figure 4 As shown, the device cluster 400 can be coupled to the first network 104 (1) via the client data plane 402, for example, to transmit data between client 102 and device cluster 400. The client data plane 402 can be implemented as a switch, hub, router, or other similar network device inside or outside of the cluster 400, and distributes traffic in a node crossing group 400. For example, the equivalent multipath (ECMP) route can be configured with a cluster, an open shortest path preferential (OSPF), the flow distribution, link aggregation (LAG) protocol or any Other types and forms of flow distribution, load balancing, and route to perform flow distribution.

[0083] The device cluster 400 can be coupled to the second network 104 (2) via the server data plane 404. Similar to the client data plane 402, the server data plane 404 can be implemented as a switch, hub, router, or other network device that can be inside or outside the cluster 400. In some embodiments, the client data plane 402 and the server data plane 404 can be combined or combined into a single device.

[0084] In some embodiments, each device 200 of the cluster 400 can be connected via an internal communication network or a rear plane 406. The rear plane 406 can enable node or inter-device control and configuration messages, between nodes for traffic, and / or for transmitting configuration and control traffic from administrators or users to cluster 400. In some embodiments, the rear plane 406 can be a physical network, a VPN, or a tunnel, or a combination thereof.

[0085] E. Platform and technology based on service map

[0086] Reference now Figures 5A-5C The system and method of the platform and technology for the service map will be discussed. The service diagram is a useful technical tool for visualizing services through its components and network elements. The service can be composed of a micro service, a specific collection of one or more functions of each micro service processing service. Network traffic can pass through the service topology (such as a client that communicates with the server) to access the service (eg, North-South traffic). The network traffic of the service can include network traffic transmitted between the micro-service level (such as between the data center or the data center). The service diagram can be used to identify and provide this network traffic of such network traffic, and the operation and performance of any network elements for providing services. The service diagram can be used to identify and determine the problem of the service, as well as which part of the topology causes this issue. The service diagram can be used to provide the implementation, management, and configuration of the service to improve operational performance of such services.

[0087] refer to Figure 5A Will describe the service diagram (such as Figure 5b The system is implemented in the system shown in the service map. The device on the network, such as network devices 200, 205, or server 206, may include a service graph generator and a configuration device 512, a service diagram display 514, and a service graph monitor 516. The service map generator and the configuration device 512 (always referred to as the service map generator 512) identifies topology 510 of the element in the network and the metric 518 associated with the network and elements to generate and / or configure service diagrams 505a-n. Service FIGS. 505A-N (Total referred to as service diagram 505) can be stored in one or more databases together with any of the metrics 518 'and / or topology 510'. The service map generator 512 can generate the data of the service diagram 505, which will be displayed in a display or presentation form such as via the user interface (total is called the service diagram 514). The service diagram monitor 516 can monitor the topology and service network elements for metric 518 to configure and generate the element and metric 518 of the service diagram 505 and / or dynamically or real-time update service diagram display 514 or display 514 by the service diagram. Elements and metrics 518.

[0088]Topology 510 may include identify, describe, or expressed otherwise specified in any one or more access service, or through a (service 275, such as any described herein) comprising one or more services such otherwise or any data element as a part thereof. Topology data may include any one or more networks and network elements to identify or describe the use of or access to services through, including any network device, router, switch, gateway, proxy, device, network connections or links, the Internet service supplier (ISP) and so on. Topology data may include identifying or any one or more applications or through use in accessing services, software, program, service, process, task or function described. One or more functions, in some embodiments, the service may be constituted by a plurality of microcells comprising a plurality of micro or service, each micro-services and services provided, one or more of the functions or operation or for the service, the function or operation. Topology data may include any one or more identified components described or service, such as a program for providing services, functions, applications or micro service. Topology may comprise any part on the parameters (such as, any topology element) topology, configuration data and / or metadata.

[0089] FIG service represent the service data 505 may include the topology 275, such as (e.g., such as Figure 5b Shown) constituting such a service or any element used by the service. FIG service node may be in the form of groups, such as a graphic form of nodes, and each node represents an element or functional topology and services. FIG service can be used via various connectors or link (which may be referred to as arcs) nodes connected to each other to represent the topology and services. Arc may identify relationships between elements connected by the arcs. You may be identified or described in a manner or to a plurality of service nodes and arcs arranged. It may be identified or described manner functions provided by one or more service nodes and arcs arranged. For example, a node may represent a function to function flow, such as the conversion (SSL terminal, VPN gateway), the filter (firewall) or the terminal (intrusion detection system). FIG functions within service may use one or more parameters and having one or more connectors.

[0090] FIG services may include any combination of nodes and arcs to represent service topology or a portion thereof. Service may be identified or described in any physical element and for accessing services and / or logical manner to deployment arrangement nodes and arcs. Network traffic may manner described identification or access to or use of the service stream are arranged nodes and arcs. May be identified or described components and services (service functionality plurality of micro communication with each other such as to provide a service) is arranged in a manner to nodes and arcs. FIGS possible to generate and service / services to the map generator or in the memory 514 to display the form of presence service in the manner of FIG storage device such as a database stored service FIG.

[0091] Service map generator 512 may include the establishment, creation, production, implementation, configuration or application update service 505 chart, programs, libraries, scripts, service, process, task, or any type and form of executable instructions. FIG generator may service read and / or write data representing FIG service database, file, or other type of storage device. FIG generator may include service logic, functionality, and operation to the arrangement of nodes and arcs constructed so as to have the service in the memory of FIG electronic representation. FIG generator may serve to read or access data in the database, and stores the data into a data structure and a memory element, can be implemented to provide or update or modify services represented in FIG node based. FIG service generator may use any of the information services is generated from topology FIG. FIG service network generator may be used to call or to recognize the topology discovery protocol or any part thereof. FIG generator may use the service (such as in a memory or storage device or from other devices) serve to generate any metric FIG. FIG generator may include service logic, functionality, and operation to the arrangement of nodes and arcs constructed so (such as the user interface on the display device) or provide services graphical visual representation of FIG. FIG generator may include service logic, function and operation to any service node or arc configuration diagram showing the configuration of parameters or elements corresponding or substantially represented by a node or arc. FIG generator may include service logic, functions and operations, including to, identify or provide services shown in FIG arrangement of nodes and arcs associated or as part of a measure. Services may include a map generator for creating, modifying service graph or chart to interact with the service, application, service, task, process or system application programming interface (API).

[0092] FIG display service 514 may include a presentation or FIG service displayed on the display device of any type and form of any electronic or graphic 505 of FIG. FIG display service may be presented in a visual form, so that the service nodes and arcs of the graph in any type of color, shape, size, or other graphical indicator indicates a state or status of the respective elements. FIG display service may be presented in a visual form, so that the service node of FIG arc and any type of color, shape, size, or other graphical indicator indicates one or more metrics state or condition. FIG display service may include any type of visual form of a user interface of FIG service, such as a control panel. FIG display service may include any type and form of user interface elements to allow the user to interact, manipulate service interface or FIG. The figure shows the portion may be selectable to the identification information, such as a metric or topology information on the service portion of FIG. FIG some services may provide a user interface displayed to the user on the service element or a portion of FIG action is taken such as to modify the configuration parameters or elements.

[0093] FIG monitor service 518 may include an application, program, library, script, service, process, task, or any type and form of executable instructions to receive, identify, process TOPOLOGY 510 518. FIG monitor service 518 via the configuration of FIG monitoring service metrics 518 elements, the performance and operation. FIG monitor service metrics can be obtained from one or more devices on a network. FIG monitor may identify the service from the network traffic passing through the apparatus of FIG monitor service or for metrics. FIG monitor service metrics may report received from any element topology (such as any element represented by the service nodes in the graph). Figure monitor service metrics may receive a report from the service. The state metric, the service monitor can determine FIG FIG or service represented by the service map (such as represented by a node serving FIG) elements, or condition of. The state metric, the service monitor can determine FIG FIG or service represented by the service view (FIG services, such as represented by the arc's) network traffic or network connection, or condition of. Service map generator and / or services, such as a monitor may FIG continuously or at a predetermined frequency or event-based, with nodes or arcs, arcs represented by a node or element, the service, or the state of the network traffic through the network topology, the status of or any measure or any change in conditions, to update the service map display.

[0094] Metric 518, 518 '(generally referred to as metrics 518) may be stored in Figure 5b On a network device, such as memory or storage devices. Metric 518, 518 'may be stored in the same database or a storage device to another device through a network, such as a server. Metric may comprise any type and form of any measurement element topology, service or network. Metric may include information about the network element represented by the node or arc received, or transmitted through the measure of the amount of the request or response to the network element, the rate or time. Metrics may include metrics about the element represented by the node or arc (such as a memory bandwidth) usage of resources. And performance metrics may include metrics regarding services (including any component or micro-services and services) operations, such as the response rate, and the transaction response time.

[0095] Figure 5b Describes the consideration to east - south implement micro-services network traffic and service related services map - West and North of network traffic. Briefly, the client 102 via one or more networks 104 to access the data center, the data center having a server 106A-106N provide one or more services 275A-275N (generally referred to as services 275) (referred to total server 106). Service can service a plurality of micro 575A-575N (generally referred to as a micro or mini-service service 575) configuration. Services may include micro-275A 575A service and 575N, and the service may include micro 275B and 575B service 575N. Micro service to communicate between the micro and services via an application programming interface (API). Figure 505 service can represent the topology and traffic on the network services (such as East - South network traffic - network traffic west and north) metrics.

[0096] North - South network traffic is often described network traffic between client and server, and associated with, such as Figure 5b Server and / or client server via a network as shown in the data center 104 via the network 104 to the client. East - West network traffic is often described network traffic between data center elements, and associated with, such as data center to data center, server-to-server, service to service or services to the micro-micro services.

[0097] Services 275 may include a micro-service 575. In some aspects, service-oriented architecture service micro-style form, which is constructed for different applications and services set smaller, rather than a single application or a whole (sometimes referred to as a monolithic application). Service having separate application or service (e.g., micro-services), that can run its own applications or services, and may use a different encoding or programming language to create, rather than a monolithic application. So, can pose a greater server consists of more simple and standalone program or service can be self-executing. These small programs or services together, to provide greater functionality and services. In some aspects, the application may be configured as a collection of loosely coupled services and services based on the service micro. The service broken down into different smaller service benefits in its improved modularity. This makes the application or service easier to understand, develop, test, and adapt to changes in architecture or deployment.

[0098] Micro services include one or more functions implemented or functionality. Micro-business service can be a functional fragment of a self-contained, with a clear or established interfaces, such as an application programming interface (API). In some embodiments, the micro-services can be deployed in a virtual machine or container. Service may use one or more functions on a micro-services, and further on a plurality of different micro-services or functions. When operating or perform a service, a service can be another micro-micro-services API calls, and the service can be invoked via micro API, event handlers or other interface mechanisms to provide a response. When operating or performing service micro, micro-services can be another micro-services API calls, the service of another micro-micro-service call in its operation or execution, and so on.

[0099] FIG service 505 may include a plurality of nodes 570A-N, the node connection or link via one or a plurality of arcs 572A-572N. FIG service may have different types of nodes. Node type may be used to represent a physical network element, such as a server, client, device or network devices. Node type may be used to represent an endpoint, such as a client or server. Node type can be used to represent a group of endpoints, such as the group of clients or servers. Node type may be used to represent a logical network element, such as a type or group of elements or subgroups of technology, software, or services. Node type may be used to represent functional elements, such as the topology of the elements or functionality provided by the service.

[0100] Any node configuration 570 and / or the representation may identify the element represented by the node status, condition and / or metrics. Graphical feature node may identify or specify the operation or performance characteristics of the element represented by the node. Whether the node size, color or shape may identify elements operating state of operation or activity. Node size, color or shape element may identify error conditions or problems. Node size, color or shape may identify the network element represented by the node received, transmitted or amount of the order or request or response to the network traffic passing through the network element. Node size, color or shape can be represented by a node identification element level of use of resources (such as memory, bandwidth, CPU or storage device). Node size, color or shape may identify a threshold for any correlation measure associated with the node or element represented by the node is associated.

[0101]The configuration and / or representation of any arc 572 can identify the state, condition, and / or metric of the elements indicated by the arc. Arc graphical features can identify or specify the operation or performance characteristics of elements represented by arc. The size, color or shape of the node can identify if the network connection indicated by the arc is an operational state of operation or activity. The size, color or shape of the arc can identify an error condition or problem with the connection associated with the arc. The size, color or shape of the arc can identify the error condition or problem of network traffic associated with the arc. The size, color or shape of the arc can identify the amount, request, or response amount, request, or response of the network traffic received by the network connection or link represented by the network connection or link indicated by the arc. The size, color or shape of the arc can identify the usage level of the network connection or traffic indicated by the arc to resources (such as bandwidth). The size, color or shape of the node can identify the correlation of the threshold of any metrics associated with the arc. In some embodiments, the metric of the arc may include any measurement of the amount of flow of each arc, delay of each arc or any measurement of the error rate of each arc.

[0102] Reference now Figure 5C The implementation of the method for generating and displaying the service diagram will be described. Brief Overview Method 580, at step 582, such as a configuration topology for one or more services. At step 584, a metric such as an element for monitoring the topology is monitored. At step 586, the service diagram is generated and configured. At step 588, a service diagram is displayed. At step 590, a problem that the configuration, operation, and performance of the service or topology can be identified or determined.

[0103] At step 582, the device recognizes the topology of one or more services. The device can be obtained, access, or receive topology 510 from a storage device such as a database. The device can be configured with a service topology, such as by a user. The device can discover the topology or part via one or more discovery protocols transmitted through the network. The device can be obtained or received from one or more other devices via a network. The device can identify network elements that form one or more services. The device can identify the function of providing one or more services. The device can identify other devices or network elements that provide functions. The device can identify network elements for the North-South traffic. The device can identify network elements for east-west flow. The device can identify micro services that provide services. In some embodiments, the service map generator is based on the topology or generating a service diagram. The service diagram can be stored in a memory or storage device.

[0104] At step 584, a metric such as an element for monitoring the topology is monitored. The device can receive metrics from one or more network elements of the topology from other devices. The device can determine the metric according to the network flow through the device. The device can receive metrics from the topology, such as via report or events. The device can monitor services to obtain or receive metrics for the service. Metrics can be stored in a memory or storage device (such as associated with the corresponding service diagram). The device can associate one or more metrics to the corresponding node of the service diagram. The device can associate one or more metrics to the corresponding arc of the service diagram. The device can be monitored and / or obtained periodically or at a predetermined frequency. The device can be monitored and / or received and / or received metrics such as real-time or dynamically when the metric is changed.

[0105] At step 586, the service diagram is generated and configured. The service map generator can generate a service diagram at least based on topology. The service map generator can generate a service diagram at least based on the service. The service map generator can generate a service diagram based on a plurality of services. The service map generator can generate a service diagram at least based on the micro service constituting the service. The service map generator can generate a service diagram based on the data center, data center server and / or data center service. The service map generator can generate a service diagram at least based on East-West traffic and corresponding network elements. The service map generator can generate a service diagram at least based on North-South traffic and corresponding network elements. The service map generator can configure the service diagram using parameters, configuration data, or metadata of elements indicated by the node or arc of the service diagram. The service diagram can be generated automatically by the device. The service diagram can be generated in response to the user, such as a request to the user interface of the device.

[0106] At step 588, a service diagram is displayed. The device can create a service diagram display 514 such as via a service graph generator to display or present via a display device, such as presenting it on a user interface. The service diagram shows the visual indicator or graphic characteristics of the node and arc of the service diagram (e.g., size, shape, or color) to identify the state, condition, or condition of the element associated with the node or arc or the corresponding element. The service diagram display can be displayed or rendered via a control panel or other user interface, and the user can monitor the service and topology in the control board or other user interface. The service diagram can be updated to display a change in metric or status, status, or / or conditions of the service, topology, or any elements thereof. Displayed via the service diagram, the user can interface or interact with the service diagram to discover information, data, and details of any network elements, such as the micro service of the service.

[0107] At step 590, a problem that the configuration, operation, and performance of the service or topology can be identified or determined. The device can determine the configuration, operation or performance of the service by comparing the metric with the threshold. The device can determine the configuration, operation or performance of the service by comparing the service's metrics to the previous or historical values. The device can determine the configuration, operation, or performance of the service by identifying a change in metrics. The device can determine the configuration, operation or performance of the service by identifying a node or arc or a change in the state, condition, or condition of an element represented by a node or arc. The device can change the configuration and / or parameters of the service diagram. The device can change the configuration of the service. The device can change the configuration of the topology. The device can change the configuration of a network element constituting a topology or service. Users can determine the configuration, operation or performance of the service by viewing, exploring, or interacting with the service diagram and any metrics. The user can change the configuration and / or parameters of the service diagram. Users can change the configuration of the service. Users can change the configuration of the topology. The device can change the configuration of a network element constituting a topology or service.

[0108] F. Systems and methods for identifying missing nodes or links for service diagrams

[0109] The embodiments described herein can provide tools for monitoring network conditions corresponding to service and / or micro services. Differently diagnosed with users (such as administrators), the systems and methods described herein can provide a tool that can actively monitor network conditions by this tool. Users can identify changes in network conditions that may cause events in the network. Therefore, the administrator can quickly and efficiently monitor the network condition based on data from or in the service diagram (eg, metrics). The embodiments described herein can improve the diagnosis and monitoring of micro-services corresponding to the service by providing visual assistance, through which the administrator can observe the metric corresponding to the micro service at different times. The embodiments described herein can reduce the closing time due to events by providing faster mechanisms, by which the administrator can remedy the incident. Various other benefits and advantages of the embodiments described herein will be described in detail below.

[0110] Reference now Figures 5A-5C as well as Figure 6A A schematic implementation of a system for identifying a closing, inactive or missing network link or micro-service, is described. like Figures 5A-5C In the present, apparatus 200 can include a service diagram generator generating and storeing service diagram 505 based on topology 510. The service diagram monitor 516 can monitor the topology 510 of the elements in the network and the metric 518 associated with the network and elements, such as to identify the missing network links and micro services. The service diagram monitor 516 may, for example, to monitor the metric 518 of the network element of the topology and service via an API to dynamically or real time to update the elements and metrics 518 of the service diagram 514 or by the elements represented by the service diagram 505 and Measure 518 thus identifys any nodes or links corresponding to closing, inactive or missing micro-service or network links in the service map 505.

[0111] In some embodiments, the service diagram monitor 516 can be configured and / or implemented to detect and identify any network links corresponding to the arc of the service diagram to delete, shut down, or inactive.

[0112] The service diagram monitor 516 can monitor network traffic via a link corresponding to one or more nodes corresponding to the microconference or an arc corresponding to one or more nodes corresponding to the microcontroller. The service diagram monitor 515 can identify any requests that fail to fail, such as a micro-service API call. The service diagram monitor 515 can identify any requests that have not returned responses, such as the API call to the micro service. The service diagram monitor 516 can identify any requests (such as an API call to the micro service). The service diagram monitor 515 can identify any requests such as an API call to the micro-service. The service diagram monitor 515 can identify any requests for closing (such as API calls to the micro service). The service diagram monitor 515 can identify any requests that are running but operational or functionally not processed or responding to a request. The service diagram monitor can identify micro-service that is transmitted to the micro service from the microcation transmission or network traffic that does not exist or has not yet the topology of the service diagram or the service map.

[0113] The service diagram monitor 516 can monitor any part of the network stack of any device that is being used to transmit the topology transmitting network traffic across the service diagram, such as any problem, such as any link to identify any link corresponding to the arc of the service diagram. The service diagram monitor can monitor the transport layer connection between the devices, such as the TCP connection between the requester and micro-service or between the micro service. The service diagram monitor can detect if a transport layer connection can be established or the transport layer connection is established. The service diagram monitor can detect whether the request for establishing a transport layer connection causes an error or returns an error. The service diagram monitor can detect whether the send request causes an error or returns an error via the established transport layer connection. The service diagram monitor can monitor any network status, condition, or condition under the transport layer to determine whether there is any problem when establishing or maintaining a network connection or network connection or other means communicating through any network link. The service diagram monitor can identify network links transmitted or transmitted via the network link from the network traffic that is not yet received by the service diagram or the service diagram.

[0114] The service diagram monitor can monitor any session above the application layer session or the transport layer to determine if there is any problem when establishing or maintaining a session. The service diagram monitor can monitor any application layer network traffic to determine if the session has established and there is no error. The service diagram monitor can monitor any application layer network traffic to determine if the request can be sent via established session without errors. The service diagram monitor can monitor any session above the application layer session or the transport layer to determine if there is any problem when sending a request (such as an API call via a session). The service diagram monitor can monitor any application layer network traffic to determine if any requests (such as API calls) are being transmitted to unknown sessions or old or expired sessions or via unknown sessions or old or expired sessions are being transmitted. The service diagram monitor can monitor any application layer network traffic to determine if there is any request (such as an API call) being transferred to an incorrect micro service. The service diagram monitor can monitor any application layer network traffic to determine if any requests (such as API calls) are being transferred to unacceptable or off. The service diagram monitor can identify network traffic is being sent to the microcate, or sends a session that does not exist via a network link, or transmits an application, service or micro service that has not been previously identified by the service diagram or service diagram, or is Send network traffic from it.

[0115]The service diagram monitor can monitor any network traffic, to determine if the request (such as an API call) source is from the expected source or by the expected network link based on the topology associated with the service graph. The service diagram monitor can identify the requested source IP address, source computer information, or source geographic information to identify requests from non-expected sources. The service diagram monitor can identify a request to be a network link that is not part of a topology associated with the service diagram. The service diagram monitor can identify a request to be a network link other than the topology of a non-expected network link.

[0116] The service diagram display and / or the service graph generator can be configured and / or implemented to identify, explain, or highlight any one or more missing, closed or unacceptable network links (arcs) and nodes (micro services). The service map generator can identify any difference or change between the topology of the topology of the selected service diagram or the topology of the monitoring service diagram. Based on these differences or changes, the service diagram display and / or the service map generator can identify the deletion, inactive or closing nodes and arcs in the service diagram, as follows Figure 6A Indicated. The service diagram display can identify such a node or arc by displaying such a node or arc by displaying or identifying a node or arc than an active or unlished node and an arc. The service diagram display can highlight or identify the missing node or arc via a graphic element (such as a dashed line or shadow or gray effect). A service diagram display can be generated to include any metrics, errors, or other information obtained from monitoring, incorrect, or closing metrics, incorrect or off, or other information.

[0117] Reference now Figure 6A The device can display the service diagram 505 in the service diagram display 514 to identify or highlight any deletion, unacceptable, or off node (micro service) or arc (network link). Briefly, the service drawings display 514 can display a service diagram 505 with multiple microacies that make up one or more services. The service diagram can include a network link represented by an arc to display a connection or network traffic between the micro service. The service diagram display can identify or highlight any deletion link (arc) 605 and / or any inactive, closed or missing node (micro service) 610. The service diagram display may include user interface 600 for displaying any function, a service diagram, and a service diagram of the device.

[0118] The service diagram shows that the missing link 605 can be identified in the service diagram. If the network link is recognized by the network link to delete, inactive or shutdown, the device can identify the same network link via a graphical element in the service diagram displayed by the service diagram. In some embodiments, the deletion, inactive or off network link can be represented by an arc drawn by a broken line in the display. In some embodiments, the deletion, inactive or off network link can be represented by an arc drawn by a shadow wire or a gray line in the display. In some embodiments, the deletion, inactive or off network link may be represented by an arc drawn by changing the size, shape, or color, to identify or highlight the deletion of the arc network link, not active Or close. In some embodiments, the deletion, inactive or off network link may be represented by an arc having a corresponding text or a flag to identify or highlight the network link deletion, inactive or off. In some embodiments, missing, inactive or closing network links can be labeled or identified by text or graphical elements in arc to identify the state, condition, or condition of the network link.

[0119] The service diagram shows that the missing node 610 can be identified in the service diagram. If the micro service is identified as missing, inactive or shutdown, the device can identify the micro service via a graphical element in the service diagram displayed by the service diagram. In some embodiments, the micro service that is missing, inactive or closed can be represented by a node drawn by a broken line in the display. In some embodiments, the micro service that is missing, inactive or closed can be represented by a node drawn by a hatching or a gray line in the display. In some embodiments, the missing, inactive or off micro service can be represented by a node drawn by changing the size, shape, or color to identify or highlight the microcation, inactive or shutdown of the node. In some embodiments, missing, inactive or closed micro services can be represented by nodes having corresponding text or tags to identify or highlight the micro-service lack of nodes, inactive or off. In some embodiments, the missing, inactive or closed micro service can be labeled or identified with text or graphic elements on the node to identify the state, condition, or condition of the micro service.

[0120] The user interface 600 displayed by the service diagram allows the user to interact, modify, and / or save the service diagram with the service graph displayed by the service diagram. In some embodiments, the user interface is configured to provide and access the functionality of the service diagram to select to monitor and / or display to the user. In some embodiments, the user interface is configured to provide and access the functionality for editing / modifying and / or saving the service diagram to provide and access. In some embodiments, the user interface is configured to provide and access functionality for comments, tags, identifiers, or highlighting nodes or arc missions, inactive, or off. In some embodiments, the user interface is configured to provide users with a reason, non-active or shutdown, or off,, not active, or shutdown to the user, not active or shutdown, or off,, not active, or off. Functionality. In some embodiments, the user interface is configured to provide and access functionality for annotation, tag, identification, or highlighting node or arc is not lost or otherwise active. In some embodiments, the user interface is configured to provide users with the function of executing commands on the elements of the service diagram (such as reboot, start or activation node or arc) to be run (such as reboot, start or activation node or arc) via the user interface. sex. In some embodiments, the user interface is configured to provide and accesses the functionality of metrics for selecting and / or checking elements such as missing nodes such as missing nodes, such as missing nodes or arcs.

[0121] Reference now Figure 6B A schematic implementation of a method for identifying a plurality of micro-serving services will be described. Brief Overview Method 620, at step 625, a device identification service diagram, such as a service diagram to be monitored. At step 630, the device monitors the topology, such as services related to the service diagram, network conditions, and the like. At step 635, the apparatus determines a network link or micro service of a service diagram corresponding to the arc or node of the closing or inactive service diagram. At step 640, the device displays the service diagram to identify an arc or node closes or inactive.

[0122] In more detail, in step 625, the apparatus identifies the service diagram, such as a service diagram to be monitored. The device can be configured to monitor a service diagram or multiple service diagrams. The device can identify the service diagram via the selection of the service diagram via the user. The user can select the service diagram via the user interface of the device (such as a command line interface or graphical user interface). The device can identify the service map from multiple service diagrams based on a set of standards or policies to monitor. The device can identify the service map based on the current or historical network traffic for monitoring. For example, the device can identify the most frequent monitoring during the past seven days to perform more frequent monitoring. The device can be monitored based on the time extension to identify the service map. For example, the device can identify a service diagram having the highest average delay to perform more frequent monitoring. The device can identify the service map based on a service diagram based on a critical degree or a priority to perform monitoring. For example, the device can monitor a service diagram that identifies a higher priority more frequently.

[0123] At step 630, the device monitors the topology related to the service diagram, such as a service, network condition, and the like. The device can monitor the micro service, the micro service can correspond to the node of the service diagram. The device can monitor links, and the link can correspond to the arc of the service diagram. The device monitors network traffic between the link and the micro service. In order to monitor the micro service and link, the device can monitor the API call passed through the device. The device can monitor the API call through a plurality of links between multiple micro services. The device can monitor the API call to the micro-service, where the API calls one of the devices or links to the micro service. The service diagram monitor can also monitor changes in the rate and / or rate of the API call, such as an event that causes or causes closing, inactive or missing components. The service diagram can monitor the number of errors or percentages of the API call or the number of times the API call timeout, to determine that there may be closable, inactive or missing components in the service diagram, such as any network link or micro service.

[0124] The device can monitor any portion of the network stack of any device for transmitting network traffic across the service graph to identify the missing or closing link or micro service. The device can detect whether or not the transmit request is erroneous or returned errors via the established transport layer connection. The device can monitor any network state, condition, or condition below the transport layer to determine whether there is a problem when establishing or maintaining network connectivity or other means communicating through any link. The device can identify network links that are not yet transmitted from topologically identified by the service diagram or the service diagram or transmitted via the network link.

[0125] At step 635, the apparatus determines a network link or micro service of a service diagram corresponding to the arc or node of the closing or inactive service diagram. If the device determines that the micro service or link does not receive at least a portion of the network traffic, the device can determine one of one or the link in the micro service is closed or inactive. The device can determine the link or micro service based on the reception error or timeout from the API call. The device can determine the link or micro service is inactive based on an error, fault, delay, or other problem of any transmission or session layer of the network stack. The device can determine that the micro service is inactive based on identifying the API call to the micro service that is running but operating or functionally not processed or responding to the request. The device can identify deletions or inactive links or micro-services by identifying network traffic to transmit or transmit or transmit or sending a micro service that does not present or has not been identified by the service graph.

[0126] The device can determine the arc or node of the service diagram to determine the arc or node of the service diagram by determining that the system is no longer used. For example, as a result of determining one or more APIs of the micro service no longer call, the device can determine that the micro service is closing or inactive. If the API call sent to the micro service fails, the device can determine that the arc or node of the service diagram is closed or inactive.

[0127] At step 640, the device displays the service diagram to identify the micro service or link is closed or inactive. The device can identify the node or arc in the display by changing one or more nodes representing one or more nodes of the micro service in the service diagram or representing one or more arcs of the link, identifying the node or arc in the display in the display, closing or deleting. . In some embodiments, the lacking, inactive or off micro service can be represented by a node having a corresponding text or a marker to identify or highlight the micro service of the node is missing, inactive or turned off. In some embodiments, the missing, inactive or closed micro service can be labeled or identified with text or graphic elements on the node to identify the state, condition, or condition of the micro service. In some embodiments, the micro service that is missing, inactive or closed can be represented by a node drawn by a broken line in the display. In some embodiments, the micro service that is missing, inactive or closed can be represented by a node drawn by a hatching or a gray line in the display.

[0128] In some embodiments, the deletion, inactive or off network link can be represented by an arc drawn by a broken line in the display. In some embodiments, missing, inactive or closed network links can be represented by arcs drawn by a shadow wire or gray line in the display. In some embodiments, the deletion, inactive or off network link may be represented by an arc drawn by changing the size, shape, or color. In some embodiments, the deletion, inactive or off network link may be represented by an arc having a corresponding text or tag. In some embodiments, the deletion, inactive or closing network links can be marked or identified with text or graphic element or identifies on arcs to identify state, status, or conditions of the network link. The system can display a node corresponding to the micro service or a shadow version of the arc corresponding to the link.

[0129]The device can automatically take action in response to the identified node or arc, such as executing commands or instructions to activate, execute, or establish a corresponding micro-service or network link. The device can automatically save the missing node or arc to the service diagram. The device can automatically troubleshoot or diagnose network links or micro services to detect problems or events that cause network link or micro-service missing, shutdown, or inactivity. Via the user interface, the user can interact with the service graph to execute the command or instruction to activate the network link or micro service, or troubleshoot and / or diagnose the network link or micro service. With the user interface, the user can save the missing node or arc as part of the service diagram.

[0130] The various elements described in the context of one or more embodiments may be provided separately or in any suitable sub-combination. For example, the procedures described herein can be implemented in hardware, software, or a combination thereof. Further, the process described herein is not limited to the specific embodiments described. For example, the process described herein is not limited to the specific processing order described herein, in contrast, process blocks can be re-sorted, combined, removed, or parallel or serially as needed to implement the results described herein.

[0131] It will be further understood that various changes may be made to various changes in the details, materials, and arrangements of components shown and illustrated herein without departing from the scope of the following claims.