I am looking for help / suggestions here from two perspectives:
1) How are people monitoring the performance of their standard AlphaWebServer instance(s)?
2) How are people monitoring the user experience / performance on the client / browser side?
MORE DETAIL (1): I need a way to quantify how speedy (or actually slow in my case) the server is at responding to requests. At the moment I have one instance of the traditional AlphaWeb server version build 4642-4981 running. I have all the server logs turned on right now and I am starting to experiment with the "a5w_analyzeWebAccessLogs()" xbasic procedure. It charts the number of requests per minute. Maybe I just haven't seen it there yet, but I'm looking for something like how much time is the server taking, on average, to service requests. Of course it would really be nice to have that broken down by web component or xbasic call and action.
MORE DETAIL (2): I need a way to track on the client - browser, how many times the users are getting a non response to clicking of certain buttons. I have seen buttons that are supposed to open another Grid in the tabbedUI, just do nothing (other than perhaps the animated "wait" gif). I'm not usually in the system saving data, but of course saving data is the primary operation my users do and they are getting a lot of nothing happening when they click the save button in editable Grids. I have offered a replacement Grid in the form of a UX for the most commonly used Grid in the app and that seems to have cut down on the complaints about the system freezing up when saving data. But I really need a way to measure the system performance from the client-side and automatically upload that information to the server, so I can see what is going on. I need something that is going to record complete session timeout errors and failures and be able to handle the user killing the browser. One they log back into the system I need have information about the failure uploaded to the server. The ultimate goal here is to figure out if the AlphaWebServer is ignoring requests from my clients, or if the load balancer is dropping requests, or if some other part is messing things up for the users. As I start making changes to overcome these problems I need a way to monitor the system and determine if my changes are working. I have tried duplicating the errors reported by users and a lot of times I either cannot duplicate them or it takes many many tries to duplicate the issue. The users, of course, say "it fails 9 out of 10 times".
1) How are people monitoring the performance of their standard AlphaWebServer instance(s)?
2) How are people monitoring the user experience / performance on the client / browser side?
MORE DETAIL (1): I need a way to quantify how speedy (or actually slow in my case) the server is at responding to requests. At the moment I have one instance of the traditional AlphaWeb server version build 4642-4981 running. I have all the server logs turned on right now and I am starting to experiment with the "a5w_analyzeWebAccessLogs()" xbasic procedure. It charts the number of requests per minute. Maybe I just haven't seen it there yet, but I'm looking for something like how much time is the server taking, on average, to service requests. Of course it would really be nice to have that broken down by web component or xbasic call and action.
MORE DETAIL (2): I need a way to track on the client - browser, how many times the users are getting a non response to clicking of certain buttons. I have seen buttons that are supposed to open another Grid in the tabbedUI, just do nothing (other than perhaps the animated "wait" gif). I'm not usually in the system saving data, but of course saving data is the primary operation my users do and they are getting a lot of nothing happening when they click the save button in editable Grids. I have offered a replacement Grid in the form of a UX for the most commonly used Grid in the app and that seems to have cut down on the complaints about the system freezing up when saving data. But I really need a way to measure the system performance from the client-side and automatically upload that information to the server, so I can see what is going on. I need something that is going to record complete session timeout errors and failures and be able to handle the user killing the browser. One they log back into the system I need have information about the failure uploaded to the server. The ultimate goal here is to figure out if the AlphaWebServer is ignoring requests from my clients, or if the load balancer is dropping requests, or if some other part is messing things up for the users. As I start making changes to overcome these problems I need a way to monitor the system and determine if my changes are working. I have tried duplicating the errors reported by users and a lot of times I either cannot duplicate them or it takes many many tries to duplicate the issue. The users, of course, say "it fails 9 out of 10 times".