Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook



The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic

Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.

If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.

Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.

Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Logging / monitoring the server response times

  • Filter
  • Time
  • Show
Clear All
new posts

  • Logging / monitoring the server response times

    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".