Abstract: A software-development tool can present telemetry data with associated source code. For example, a computing device can identify, by a text editor, source code of a software application that is associated with telemetry data of performance metrics associated with running the source code. The computing device can display, by the text editor, an icon with the source code. The icon can indicate the source code is associated with the telemetry data. The computing device can receive an interaction with the icon. In response to receiving the interaction, the computing device can retrieve, by the text editor, the telemetry data from a telemetry-data repository for display in the text editor.

Abstract: A software-development tool can present telemetry data with associated source code. For example, a computing device can identify, by a text editor, source code of a software application that is associated with telemetry data of performance metrics associated with running the source code. The computing device can display, by the text editor, an icon with the source code. The icon can indicate the source code is associated with the telemetry data. The computing device can receive an interaction with the icon. In response to receiving the interaction, the computing device can retrieve, by the text editor, the telemetry data from a telemetry-data repository for display in the text editor.

Abstract: Software tracing can be accomplished in a multitenant environment according to various examples of the present disclosure. In one example, a processing device can receive tracing information and a tenant identifier. The tracing information can indicate a sequence in which a group of microservices forming a software application executed in response to a request transmitted to the software application. The tenant identifier can correspond to a particular tenant among a group of tenants having access to an instance of the software application. The processing device can then select, based on the tenant identifier, a particular collector from among a group of collectors corresponding to the group of tenants. The processing device can forward the tracing information to the particular collector for causing the tracing information to be stored in a datastore corresponding to the particular tenant.

Abstract: A method performed by a computing system includes receiving from a client component of an enterprise application, a request destined for a service component of the enterprise application, the request comprising authentication data and request data, the authentication data being associated with a current user of the client component, the user associated with an organization. The method further includes performing an authentication process to create principal data and role data associated with the request, the principal data identifying a user. The method further includes using the authentication data and request data, determining a current tenant of the client component. The method further includes replacing the principal data with updated principal data, the updated principal data identifying the organization. The method further includes updating the role data associated with the request to create updated role data that indicates roles of the user within the organization.

Abstract: An example method for processing a client request includes determining a set of functions to invoke for processing an initial request sent by a client to an application. The set of functions includes a function stored at a server. The method also includes invoking, by a proxy, the function at the server. The server provides the function as a function as a service (FAAS) for invocation by one or more third parties. The method further includes sending, by the proxy, a processed request to the application. The processed request is based on a result of the function. The method also includes receiving, by the proxy, a response to the processed request from the application.

Abstract: A server system includes a memory, a processor in communication with the memory, and a server managing a plurality of cooperating microservices. The server executes on the at least one processor to capture tracing information reported during invocation of a set of cooperating microservices. The tracing information includes a service name and version information associated with at least one microservice of the set of cooperating microservices. Additionally, the server builds an application deployment profile from the service name and version information, compares the application deployment profile to an existing profile, and classifies the application deployment profile as a previously existing profile, a subset profile, an extension profile, and/or an updated profile. The server tracks performance data associated with the application deployment profile.

Abstract: Software tracing can be accomplished in a multitenant environment according to various examples of the present disclosure. In one example, a processing device can receive tracing information and a tenant identifier. The tracing information can indicate a sequence in which a group of microservices forming a software application executed in response to a request transmitted to the software application. The tenant identifier can correspond to a particular tenant among a group of tenants having access to an instance of the software application. The processing device can then select, based on the tenant identifier, a particular collector from among a group of collectors corresponding to the group of tenants. The processing device can forward the tracing information to the particular collector for causing the tracing information to be stored in a datastore corresponding to the particular tenant.

Abstract: A server system includes a memory, a processor in communication with the memory, and a server managing a plurality of cooperating microservices. The server executes on the at least one processor to capture tracing information reported during invocation of a set of cooperating microservices. The tracing information includes a service name and version information associated with at least one microservice of the set of cooperating microservices. Additionally, the server builds an application deployment profile from the service name and version information, compares the application deployment profile to an existing profile, and classifies the application deployment profile as a previously existing profile, a subset profile, an extension profile, and/or an updated profile. The server tracks performance data associated with the application deployment profile.

Abstract: A server system includes a memory, a processor in communication with the memory, and a server managing a plurality of cooperating microservices. The server executes on the at least one processor to capture tracing information reported during invocation of a set of cooperating microservices. The tracing information includes a service name and version information associated with at least one microservice of the set of cooperating microservices. Additionally, the server builds an application deployment profile from the service name and version information, compares the application deployment profile to an existing profile, and classifies the application deployment profile as a previously existing profile, a subset profile, an extension profile, and/or an updated profile. The server tracks performance data associated with the application deployment profile.

Abstract: An authentication system includes an authentication server, an application having a proxy, and a token store. The token store receives an authentication request and sends the request to the authentication server. The authentication server authenticates the user based on the request. The token store requests an offline token from the authentication server. The authentication server sends the offline token to the token store. The token store generates a key-secret pair and stores the offline token and the key-secret pair in a database. The token store sends the authentication result of the user to the application. The application receives an authentication result and requests a key-secret pair from the token store. The token store sends the key-secret pair to the application. The key-secret pair is used to configure an agent, which adds the key-secret pair to a communication request sent to the application. The application processes the communication request.

Abstract: An example method for processing a client request includes determining a set of functions to invoke for processing an initial request sent by a client to an application. The set of functions includes a function stored at a server. The method also includes invoking, by a proxy, the function at the server. The server provides the function as a function as a service (FAAS) for invocation by one or more third parties. The method further includes sending, by the proxy, a processed request to the application. The processed request is based on a result of the function. The method also includes receiving, by the proxy, a response to the processed request from the application.

Abstract: A server system includes a memory, a processor in communication with the memory, and a server managing a plurality of cooperating microservices. The server executes on the at least one processor to capture tracing information reported during invocation of a set of cooperating microservices. The tracing information includes a service name and version information associated with at least one microservice of the set of cooperating microservices. Additionally, the server builds an application deployment profile from the service name and version information, compares the application deployment profile to an existing profile, and classifies the application deployment profile as a previously existing profile, a subset profile, an extension profile, and/or an updated profile. The server tracks performance data associated with the application deployment profile.

Abstract: A method performed by a computing system includes receiving from a client component of an enterprise application, a request destined for a service component of the enterprise application, the request comprising authentication data and request data, the authentication data being associated with a current user of the client component, the user associated with an organization. The method further includes performing an authentication process to create principal data and role data associated with the request, the principal data identifying a user. The method further includes using the authentication data and request data, determining a current tenant of the client component. The method further includes replacing the principal data with updated principal data, the updated principal data identifying the organization. The method further includes updating the role data associated with the request to create updated role data that indicates roles of the user within the organization.

Abstract: An authentication system includes an authentication server, an application having a proxy, and a token store. The token store receives an authentication request and sends the request to the authentication server. The authentication server authenticates the user based on the request. The token store requests an offline token from the authentication server. The authentication server sends the offline token to the token store. The token store generates a key-secret pair and stores the offline token and the key-secret pair in a database. The token store sends the authentication result of the user to the application. The application receives an authentication result and requests a key-secret pair from the token store. The token store sends the key-secret pair to the application. The key-secret pair is used to configure an agent, which adds the key-secret pair to a communication request sent to the application. The application processes the communication request.