 |
|
What is it?The log file on a Blackberry Enterprise server contains a number of entries that track every interaction between your enterprise,the Blackberry network, and those wonderful little devices. Searching that log for individual information is tedious and time consuming.The Blackberry Log Analysis tool will be a collection of design items that will automate much of the searching, parsing, and other tasks that an administrator may have to perform from day to day. The tool is in its infancy, and will be making a number of changes, right turns, and probably wrong turns before evolving to a mature product. Your input is appreciated and accepted with open arms. The entire application is available at OpenNTF.org You must be registered to download. This single file is made available, if you want to make changes to the Queue Report in version 0.1. You do not need this if you are using 0.1a or higher. Right Click the link, and select Save As, then save the file as QRepEntry.lss. You will need to make the necessary location changes in the QReport code to point to the correct location of the QRepEntry.lss file. All of the LotusScript code is in this 7z-Zip file. The MD5 hash of this file is "D5DD11A808DE5294B45C8BFACABAA85E" File size is 15K bytes. The Queue ReportThe first tool is an agent that runs on a regular basis. The administrator can change the timing, although I would suggest a nightly run at Midnight. The agent will look at yesterday's log entries, pull the "queue" reports out, then distill them to a report that can be sent to the administrator. The report is saved to the application so the sent report is optional. Individual reports are also created, and saved to the application.  Trends are quickly identified, and clients can be amazed as an administrator corrects issues before complaints are logged.  Potential rough spots are identified so the administrator can clear the issue quickly. 
The Individual Message ReportThe Individual Message Reports are created when the agent runs through the log file looking for Message Conversations. A Message Conversation is made up of several entries in a log file, tied together by a control number. BBAnalysis uses the NoteID found on most entries. As the parse engine works through each entry, as it finds new NoteID's, it starts a new "conversation", and attaches any other related parts to the conversation. Conversations are attached to an Account Owner. The report engine takes each of these Owners, and reports all their conversations to individual documents. Each document is limited to 201 conversations, so additional documents may be needed and created. As each document is created, the Individual Message Report view shows, by Owner, the conversation report(s). Opening a report will reveal details about the time Queued, Sent, and Confirmed. The Confirmed and Sent timestamps are compared for Latency or "how long did it take to actually deliver the message to the device, and receive back a confirmation."  Latency of a few seconds is not uncommon, but longer than five minutes may indicate some attention is needed. The tool will highlight entries of over five minutes in red.  You may find calendar entries listed with Notes in the last column. These entries can be either Updates or Deletes at this time. 
|
|