The disclosure provides a service request processing method. A service consumer transmits a service request, including a plurality of service producer types, and an access order of service producer instances corresponding to the plurality of service producer types is determined. The service producer instances corresponding to the plurality of service producer types are controlled to process the service request according to the access order.

Examples herein relate to developing an orchestration plan. Examples disclose the development of a representation of a set of services wherein each service relates to other services via different types of relationships. The examples apply a set of dependency rules for each type of relationship at each service within the set of services such that the application of the set of dependency rules creates inter-service dependencies between state transitions of the set of services. Based on the creation of the inter-service dependencies, the orchestration plan is developed which includes a sequenced order of the state transitions for the set of services.

Examples herein relate to developing an orchestration plan. Examples disclose the development of a representation of a set of services wherein each service relates to other services via different types of relationships. The examples apply a set of dependency rules for each type of relationship at each service within the set of services such that the application of the set of dependency rules creates inter-service dependencies between state transitions of the set of services. Based on the creation of the inter-service dependencies, the orchestration plan is developed which includes a sequenced order of the state transitions for the set of services.

Provided herein are systems and methods for providing insights or metrics in connection with provisioning applications and/or desktop sessions to end-users. Network devices (e.g., appliances, intermediary devices, gateways, proxy devices or middle-boxes) can gather insights such as network-level statistics. Additional insights (e.g., metadata and metrics) associated with virtual applications and virtual desktops can be gathered to provide administrators with comprehensive end-to-end real-time and/or historical reports of performance and end-user experience (UX) insights. Insights relating to an application or desktop session can be used to determine and/or improve the overall health of the infrastructure of the session, Citrix Virtual Apps and Desktops, the applications (e.g., remote desktop application) being delivered using the infrastructure, and/or the corresponding user experience.

Provided herein are systems and methods for providing insights or metrics in connection with provisioning applications and/or desktop sessions to end-users. Network devices (e.g., appliances, intermediary devices, gateways, proxy devices or middle-boxes) can gather insights such as network-level statistics. Additional insights (e.g., metadata and metrics) associated with virtual applications and virtual desktops can be gathered to provide administrators with comprehensive end-to-end real-time and/or historical reports of performance and end-user experience (UX) insights. Insights relating to an application or desktop session can be used to determine and/or improve the overall health of the infrastructure of the session, Citrix Virtual Apps and Desktops, the applications (e.g., remote desktop application) being delivered using the infrastructure, and/or the corresponding user experience.

A first correspondence table in a terminal device stores a correspondence between an identifier of a process running on the terminal device and an identifier of a data stream created by the process, a second correspondence table stores a second correspondence between an identifier of an application and an identifier of a process created by the application. The terminal device receives an identifier, sent by a network security device, of a first data stream. The terminal device can find, in the first correspondence table, a first record storing the identifier of the first data stream to obtain an identifier of a process. The terminal device can find in the second correspondence table, a second record storing the identifier of the process in the first record to obtain an identifier of an application from the second record. The identifier of the application is then sent to the network security device.

A discovery application on a computing system is provided. The discovery application receives a user input, which is for discovery of resources associated with a cloud operating system of a cloud computing system. The user input includes an authentication credential and account information associated with the cloud operating system. Based on the received input, the discovery application executes a discovery pattern comprising operations for the discovery of resources. The cloud operating system includes a group of services to access such resources. At least one of the operations corresponds to an API call to an API endpoint associated with a service of the group of services. The discovery application receives a response to the API call from the cloud operating system. The response includes a payload of information associated with the resources. The discovery application updates, based on the received response, one or more configuration items in a configuration management database.

In one embodiment, a method includes storing, by a tracking server, a hash value for each of one or more tracking devices associated with the tracking server. The method includes receiving, at the tracking server from a user device, a hash value associated with a tracking device, the hash value computed based on a static value uniquely associated with the tracking device and a dynamic value maintained by the tracking device. The method includes identifying, by the tracking server, the tracking device based on a comparison between one of the stored hash values and the received hash value. The method includes updating, by the tracking server, one or more records associated with the identified tracking device based on the receiving the hash value.

A method of automatically creating trust communities in a fleet of devices. The method includes finding candidate devices in a fleet of devices via one or more candidate discovery techniques and generating device-related data based on the candidate devices that are found, analyzing the device-related data via an analytics engine and creating one or more fleet orchestrator device lists based on the analysis of the device-related data, and automatically creating one or more new trust communities or suggesting joining one or more previously existing trust communities based at least on the one or more fleet orchestrator device lists for the candidate devices, wherein the one or more new trust communities or previously existing trust communities include at least a sub-set of the devices in the fleet, and wherein at least one of the managed devices in the sub-set of devices is configured as a root device to publish files via a file sharing function.

A method of automatically creating trust communities in a fleet of devices. The method includes finding candidate devices in a fleet of devices via one or more candidate discovery techniques and generating device-related data based on the candidate devices that are found, analyzing the device-related data via an analytics engine and creating one or more fleet orchestrator device lists based on the analysis of the device-related data, and automatically creating one or more new trust communities or suggesting joining one or more previously existing trust communities based at least on the one or more fleet orchestrator device lists for the candidate devices, wherein the one or more new trust communities or previously existing trust communities include at least a sub-set of the devices in the fleet, and wherein at least one of the managed devices in the sub-set of devices is configured as a root device to publish files via a file sharing function.