User-configurable end user monitoring (EUM)

1. A method, comprising:

downloading, by a web browser executed by a client device, webpage data for a webpage from a web server;

downloading, by the client device, a browser extension for the web browser from a proxy service;

inserting, by the client device, instrumentation into the webpage data to collect event metrics for events associated with the webpage;

selecting, by the client device and based on a user-defined policy configured by an end user of the client device, a first set of event metrics from among the collected event metrics to be shared with the proxy service;

determining, by the client device and based on the user-defined policy, a second set of event metrics from among the collected event metrics that is not to be shared with the proxy service; and

sending, by the client device, the first set of event metrics, and not the second set of event metrics, to the proxy service, wherein the proxy service provides access to the first set of event metrics to one or more collectors registered with the proxy service,

wherein the browser extension performs the inserting, selecting, and sending steps.

2. The method as in claim 1 , wherein the events comprise an AJAX or WebSocket call made by the webpage after being loaded by the web browser.

3. The method as in claim 1 , wherein the events comprise one or more page load events.

4. The method as in claim 1 , wherein inserting the instrumentation into the webpage data to collect event metrics for events associated with the webpage comprises:

inserting a script into the webpage data, prior to the web browser loading the webpage data.

5. The method as in claim 1 , further comprising:

receiving, at the client device, the user-defined policy from a user interface of the client device.

6. The method as in claim 1 , wherein the instrumentation is inserted into the webpage data, based on the user-defined policy.

7. The method as in claim 1 , wherein the user-defined policy specifies that event metrics for error events are to be shared with the proxy service.

8. The method as in claim 1 , wherein the user-defined policy specifies that the event metrics are to be shared with the proxy service when a latency associated with the webpage exceeds a predefined threshold.

9. The method as in claim 1 , further comprising:

providing, by the client device, an indication of the collected event metrics via the web browser.

10. The method as in claim 1 , wherein the instrumentation, when executed, collects the event metrics using an application programming interface (API) of the webpage.

11. The method as in claim 1 , further comprising:

displaying, on the client device, a popup describing the performance of the webpage.

12. An apparatus, comprising:

one or more network interfaces to communicate with a network;

a processor coupled to the network interfaces and configured to execute one or more processes; and

a memory configured to store a process executable by the processor, the process, when executed, configured to:

download, by a web browser executed by the apparatus, webpage data for a webpage from a web server;

download a browser extension for the web browser from a proxy service;

insert instrumentation into the webpage data to collect event metrics for events associated with the webpage;

select, based on a user-defined policy configured by an end user of the apparatus, a first set of event metrics from among the collected event metrics to be shared with the proxy service;

determine, based on the user-defined policy, a second set of event metrics from among the collected event metrics that is not to be shared with the proxy service; and

send the first set of event metrics, and not the second set of event metrics, to the proxy service, wherein the proxy service provides access to the first set of event metrics to one or more collectors registered with the proxy service,

wherein the browser extension performs the inserting, selecting, and sending.

13. The apparatus as in claim 12 , wherein the events are selected from a group consisting of: an AJAX or WebSocket call made by the webpage after being loaded by the web browser; and one or more page load events.

14. The apparatus as in claim 12 , wherein the apparatus inserts the instrumentation into the webpage data to collect event metrics for events associated with the webpage by:

inserting a script into the webpage data, prior to the web browser loading the webpage data.

15. The apparatus as in claim 12 , wherein the process when executed is further configured to:

receive the user-defined policy from a user interface of the apparatus.

16. The apparatus as in claim 12 , wherein the instrumentation is inserted into the webpage data, based on the user-defined policy.

17. The apparatus as in claim 12 , wherein the user-defined policy specifies that event metrics for error events are to be shared with the proxy service or when a latency associated with the webpage exceeds a predefined threshold.

18. The apparatus as in claim 12 , wherein the process when executed is further configured to:

provide an indication of the collected event metrics to a user interface of the apparatus via the web browser.

19. The apparatus as in claim 12 , wherein the instrumentation is inserted into the webpage data by attaching the instrumentation to a main page of the webpage.

20. A tangible, non-transitory, computer-readable medium having computer-executable instructions stored thereon that, when executed by a processor on a device, cause the device to perform a method comprising:

downloading, by a web browser executed by the device, webpage data for a webpage from a web server;

downloading, by the device, a browser extension for the web browser from a proxy service;

inserting, by the device, instrumentation into the webpage data to collect event metrics for events associated with the webpage;

selecting, by the device and based on a user-defined policy configured by an end user of the device, a first set of event metrics from among the collected event metrics to be shared with the proxy service;

determining, by the device and based on the user-defined policy, a second set of event metrics from among the collected event metrics that is not to be shared with the proxy service; and

sending, by the device, the first set of event metrics, and not the second set of event metrics, to the proxy service, wherein the proxy service provides access to the first set of event metrics to one or more collectors registered with the proxy service,

wherein the browser extension performs the inserting, selecting, and sending steps.