Has anyone done any thinking or implementing about instrumenting Web Builder applications? Discussion on DotnetRocks made me think - the proponent was saying that you need to know what people are doing or you can't improve or focus on issues.

Now, sending what is happening to the server is one thing, and let's assume that is taken care of. A simple POST should cover it anyway. Is there any way to intercept form show, or page control clicks, or such like? How detailed to go? How to ensure it is anonymous? Any thoughts?

--

Matthew Jones

Matthew,

<< Now, sending what is happening to the server is one thing, and let's assume that is taken care of. A simple POST should cover it anyway. Is there any way to intercept form show, or page control clicks, or such like? How detailed to go? How to ensure it is anonymous? Any thoughts? >>

That's the main thing with telemetry data: making sure that users a) know that you're doing it, and b) that doing so does not violate their privacy or data.

As for EWB, this is a fairly easy thing to integrate into the core processing since it all is handled in the WebUI unit.  It's similar to how we can detect when a user hasn't touched the mouse or keyboard for X seconds.  There's a common event manager that can tell you when something is clicked on, or something is typed, and what that something is.  If you're interested in me pursuing this, I can certainly add it to the enhancements list.

Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

>  If you're interested in me pursuing this, I can certainly add it to the enhancements list.

I think it would be good to be able to hook into things. Obviously in some manner that is minimal impact if not used, or even if it is. I realise it would be up to the developer to keep the impact of logging to a minimum, perhaps storing an action and processing them later at idle time.

--

Matthew Jones