not only would it be nice to publish the data jQuery collects; it would be great to allow users to share their data with us.
this effort involves building a Splunk input that accepts HTTP posts from a profiler running in a client.
the profiler would be an instrumentation script that duck-punches the jQuery lib, and reports back usage. we would want to throttle calls home, and also report on the environment (browser, resolution). the events would be API calls, stack traces/errors, and performance.
not only would it be nice to publish the data jQuery collects; it would be great to allow users to share their data with us.
this effort involves building a Splunk input that accepts HTTP posts from a profiler running in a client.
the profiler would be an instrumentation script that duck-punches the jQuery lib, and reports back usage. we would want to throttle calls home, and also report on the environment (browser, resolution). the events would be API calls, stack traces/errors, and performance.