Thank you very much Roland, Christian and Robert, I am not familiar (so I have to get more info) about the piwik. I am not sure I can make it look like part of the application. It is important to be able to customize what is published and to provide links back to the website.
My initial plan was to use the DB to store user info and some triggering procedure to publish data (similar to Robert's suggestion). It still seems straightforward and simple to implement. I find using a combination of user and domain variables to gather information more elegant (why didn't I think of that?) but also requires more code to write. (Roland, thank you for your offer to share information) In my case (the database has about 12K users, but very few connected at any time) I believe any solution will work. (It was very useful to find out about the limitations of each method; thank you Robert) I will still have to decide if I should use a refresh or push method to publish data. Also, IMO, getting access to server information will be very useful for admin purposes indeed. Many thanks again. MB _____ From: Robert Shubert [mailto:[email protected]] Sent: Wednesday, August 10, 2011 21:50 To: [email protected] Subject: RE: Witango-Talk: Monitoring Website Users I wonder if the TeraScript server could provide some of these metrics internally. There's a long standing request to allow a TAF to retrieve a list of user sessions currently active. It may also be possible to provide a tag that would report the number of requests processed for a user session, the last executed appfile, or an array of the session's requests. As for your solution, Mike, you will need to insert or update data in a database per request about each user and their session. You'll then have a monitoring TAF that might refresh every 5 seconds and display the latest record for each active session. The key to doing something like this is to be sure that the database is as light as possible. Since it'll be both writing or updating a lot and have frequent selects, you want to store just the bare minimum of data for the task at hand and have appropriate indexing. If using the database seems to add too much time, using domain scoped variables will be much faster. The trade off is that MS SQL Server will not appreciably slow down as your active user sessions scale up to 1000+ rows, however domain variables do suffer performance issues when several hundred (or more) rows are involved. This is something I hope to address in the next major release. Robert From: mike Bravu [mailto:[email protected]] Sent: Wednesday, August 10, 2011 4:41 PM To: [email protected] Subject: Witango-Talk: Monitoring Website Users Hi all, I need to monitor users on my website (using Witango Server 5.5/Windows 2003/MSSQL 2005). I need to know who is logged in, what pages they are viewing. The administrator of the site would prefer to have an applet/webpage opened that would list in (almost) real time the name of the user logged in and the current visited page (this would look like getting streaming info from a sport event, for example). Questions: 1- Has anybody had to deal with this issue and is willing to share info, or provide a hint? 2- Is there a way find out which users are logged in from the Witango server? I have a rudimentary solution in mind, but it is probably a heavy load for the CPU. I checked the forum but could not find anything pertinent to my problem. Thank you, MB _____ To unsubscribe from this list, please send an email to [email protected] with "unsubscribe witango-talk" in the body. _____ To unsubscribe from this list, please send an email to [email protected] with "unsubscribe witango-talk" in the body. ---------------------------------------- To unsubscribe from this list, please send an email to [email protected] with "unsubscribe witango-talk" in the body.
