Abstract: The invention provides a method for producing an immunoconjugate, the method comprising combining one or more compounds of Formula I and an antibody construct of Formula II to provide the immunoconjugate of Formula III, wherein TA is a therapeutic agent, L is a linker, r is an integer from 1 to 50, Ar is an aromatic moiety comprising a substituent selected from PEG, —SO2CX3, —NR3+, —NO2, —SO3R, —SO2R, —CN, —CX3, —PO3R2, —OPO3R2, and salts thereof, each R independently is H, CX3, or C1-C4 alkyl, each X independently is hydrogen or a halogen, Y is CH2, PEG, or a bond, n is an integer from 1 to 4, and PEG has the formula: —(CH2CH2O)m-(CH2)p—, where p is an integer from 1 to 5 and m is an integer from 2 to 50. The invention also provides an immunoconjugate and a composition of immunoconjugates formed from said method.

Abstract: In one embodiment, a method for user performance journey monitoring is disclosed. The method illustratively comprises receiving, by a process, user journey information associated with an application and a plurality of application end users, the user journey information indicative of navigation paths of the application end users among a plurality of nodes configured to perform at least a part of the application; receiving, by the process, performance metric information indicative of performance of the plurality of nodes configured to perform at least the part of the application; correlating, by the process, the user journey information with the performance metric information based on one or more query criteria; and storing, by the process, the correlated user journey information and performance metric information in an application end user journey database indexed by the one or more query criteria.

Abstract: In one embodiment, a method for automatic application data collection is disclosed. The method illustratively comprises determining a stack trace associated with one or more business transactions, wherein at least one application is configured to perform at least part of the one or more business transactions; identifying, based on the stack trace, one or more methods of the at least one application that were invoked during performance of the one or more business transactions; selecting, from the identified one or more methods, a set of the one or more methods by applying at least one scoring heuristic to the identified one or methods; and configuring one or more monitoring agents executing on the at least one application to instrument the selected set of the one or methods at one or more instrumentation points, wherein application performance data is generated by instrumentation of the one or more instrumentation points.

Abstract: In one embodiment, a monitoring process monitors timing of navigations and resources of a web page load, and attributes timing of the navigations and resources into corresponding timing components. In particular, the monitoring process may attribute timing of static first-party resources and timing of hypertext transfer protocol (HTTP) redirects to a core frontend timing component, and may attribute timing of dynamic first-party resources to a core backend timing component. The monitoring process may also attribute timing of content delivery network (CDN) resources to a CDN timing component, and may attribute timing of non-CDN third-party resources to a third-party timing component. Lastly, the monitoring process may further attribute timing of network infrastructure connections to a core connections timing component. Accordingly, the monitoring process may then perform one or more actions based on the attributing steps.

Abstract: In one embodiment, a monitoring process monitors timing of navigations and resources of a web page load, and attributes timing of the navigations and resources into corresponding timing components. In particular, the monitoring process may attribute timing of static first-party resources and timing of hypertext transfer protocol (HTTP) redirects to a core frontend timing component, and may attribute timing of dynamic first-party resources to a core backend timing component. The monitoring process may also attribute timing of content delivery network (CDN) resources to a CDN timing component, and may attribute timing of non-CDN third-party resources to a third-party timing component. Lastly, the monitoring process may further attribute timing of network infrastructure connections to a core connections timing component. Accordingly, the monitoring process may then perform one or more actions based on the attributing steps.

Abstract: A session, consisting of multiple page views by a user with a web service, is monitored, analyzed, and diagnosed for a user. The session may include one or more requests or page views experienced by a user during the session. The session may be defined as the user experience on a series of network content pages visited through a single instance of a network browser. The session may be determined to end when no activity is detected from the user for a specified period of time. In other implementations, a session may be based on a user indication, a set period of time, or for some other reason. The data is collected by one or more agents throughout the system, reported to a controller, and correlated together at the controller for querying and reporting. The correlated data is reported by the controller to a user through an interface.

Abstract: A session, consisting of multiple page views by a user with a web service, is monitored, analyzed, and diagnosed for a user. The session may include one or more requests or page views experienced by a user during the session. The session may be defined as the user experience on a series of network content pages visited through a single instance of a network browser. The session may be determined to end when no activity is detected from the user for a specified period of time. In other implementations, a session may be based on a user indication, a set period of time, or for some other reason. The data is collected by one or more agents throughout the system, reported to a controller, and correlated together at the controller for querying and reporting. The correlated data is reported by the controller to a user through an interface.