WebWatchBot version history

WebWatchBot > Version History

Version History

WebWatchBot

This shows you how often WebWatchBot was updated with us over the past few months. Whenever available, we also include additional information for each update (new features, changes etc.).

version 5.1.11 - posted on Oct 22, 2009

Enhancement: Watch List, Status Report

version 5.1.10 - posted on Jul 10, 2009

Various bug fixes

version 5.1.9 - posted on Feb 26, 2009

No further details available

version 5.1.8 - posted on Jan 31, 2009

No further details available

version 5.1.7 - posted on Nov 18, 2008

Various minor bug fixes

version 5.1.5 - posted on Jun 19, 2008

No further details available

version 5.1.4 - posted on Apr 09, 2008

Enhancement: HTTP/HTTPS Watch Types: If the HTTP method is POST (not the default GET), the Watch Type displayed in the Watch List will show `HTTP (POST)` or `HTTPS (POST)` to easily identify Watch Items that are POSTing data.

version 5.1.3 - posted on Jan 18, 2008

Minor bug fix

version 5.1.2 - posted on Dec 18, 2007

Important Bug Fixes

version 5.1.1 - posted on Nov 22, 2007

Various bug fixes

version 5.1 - posted on Nov 08, 2007

No further details available

version 5.0.7 - posted on Oct 29, 2007

No further details available

version 5.0.6 - posted on Jun 05, 2007

Bug Fix (5.0.6.1): Enhanced HTTP error handling addressing two issues: 1. Entering a bad/non-existent URL, 2. Querying a URL of a web server that is not running or accepting connections. In both cases if the timeout is not set for the Watch Item, WebWatchBot can query indefinitely.

Bug Fix (5.0.6.2): Status Report: Removed special text which is only visible in Firefox browser. Bug Fix (5.0.6.3): Fixed spelling and gramatical errors. Bug Fix (5.0.6.4): Importing Snmp Watch Types did not import the community string. Bug Fix (5.0.6.5): Check for a newer version: Incorrectly reporting that user must be logged in as the local administrator in order to launch the WebWatchBot Updater. Bug Fix (5.0.6.6): Performance Counter Settings: Allocated more memory so that computers with a large number of performance counters would not receive the following error message when viewing all performance counters on the system: `The mszObjectList buffer is not large enough to hold the list of objects. Use the pcchBufferLength parameter to allocate the required size buffer.` Change: Update internal components which may address a problem where the UI will not load in rare cases on a few systems. Change: Performance Counters, values stored in the database to better handle European decimal notation of comma instead of period.

version 5.0.4 - posted on Jan 28, 2007

Minor bug fixes

version 5.0.3 - posted on Jan 07, 2007

Enhancement: HTTP/HTTPS Watch Types: Post Data value randomization. Types of replacement tags that we are looking for: (*TEXT:0*), (*DECIMAL:2.2*) and (*INTEGER:0*), where the number is the length of either the text string or the number. Decimals can have
Enhancement: Reports and Charts: Specify new Date Range for specific time periods for Last X units, e.g. 1 minute, 2 days, 3 weeks, 1 month, 2 years, etc
Enhancement: Reports: Added support for report output in PDF format
Enhancement: Thread Monitor: Each Watch Item and Transaction s thread is monitored every 15 seconds to ensure it is running, and restarted when it is not
Enhancement: Email Settings: Port number can be specified
Enhancement: HTTP/HTTPS Watch Types: When a 3xx redirection without `Location:` is specified in the HTTP header, WebWatchBot will redirect to the root of the url. For example, for the original url http://www4.symantec.com/Vrt/vrtcontroller the redirection
Enhancement: SNMP: Ability to specify an SNMP community other than `public`
Enhancement: Added `New` to right-click context menu on the Watch List
Bug Fix (5.0.3.1): Improved performance during startup and during settings updates for Transactions
Bug Fix (5.0.3.2): Some chart settings not being saved. Fixed
Bug Fix (5.0.3.3): Reports: Error message `An error occurred retrieving summary data from the database`. Fixed
Bug Fix (5.0.3.4): Database Maintance/Backup: Now preventing backups to be run in WebWatchBot when the back-end database is not local. Also fixes the issue where database maintenance would not run successfully because backup fails
Bug Fix (5.0.3.5): Alarm Command: If the length of the `Program`, `URL`, `Reset URL`, `Reset Program` exceeds the maximum length (about 240 characters), a message will be displayed and the text will be shortened
Bug Fix (5.0.3.6): WebWatchBot Service: If the database storing WebWatchBot s data is offline, an error will occur. Fixed

version 5.0.2 - posted on Dec 08, 2006

Performance improvements, WebWatchBot database management, new features, and important bug fixes.

version 5.0.1 - posted on Oct 17, 2006

Bug Fix (5.0.1.1): Improved performance when starting up WebWatchBot Manager and the WebWatchBot Service.
Bug Fix (5.0.1.2): Database Upgrade: Corrected problem with regional settings where floating numbers are represented with a comma instead of a period, causing new installs and upgrades to fail.
Bug Fix (5.0.1.3): Service may not start-up when there are more than 25 Watch Items.
Bug Fix (5.0.1.4): Chart does not show correct memory usage units - in GB.
Bug Fix (5.0.1.5): Multi-selection actions now pause all preview pane updates for better performance.
Bug Fix (5.0.1.6): Killing the service process WWBServer.exe can cause the Gui to display the message that the connection to the remote server has been terminated.
Bug Fix (5.0.1.7): New Watch Items: Create a new watch item, switch to the schedule tab, click `New` -> Crash.
Bug Fix (5.0.1.8): Process and Service Watch Types: Charts now show CPU point labels.
Bug Fix (5.0.1.9): Disk Usage Watch Types: Y axis now show units, e.g. MB or GB
Bug Fix (5.0.1.10): Status Report: New monitoring types do not properly show Last and Avg.
Bug Fix (5.0.1.11): Process and Service Watch Types: Memory threshold check fixed.
Bug Fix (5.0.1.12): Reports: Reports run through the scheduler or with an email alert are now run in a separate process to prevent memory/resource leaking.
Change: Performance Chart: The performance chart now refreshes automatically every 60 seconds.

version 5.0 - posted on Oct 12, 2006

9 new monitoring types:
Monitor CPU, Memory, Application, & more
Process (Windows) Monitoring
Service (Windows) Monitoring
SNMP Monitoring
Disk Usage Monitoring
File Monitoring
Event Log (Windows) Monitoring
Trace Route Monitoring
Custom Monitoring

version 4.0.7 - posted on Jul 23, 2006

Various enhancements and bug fixes.

version 4.0.5 - posted on May 16, 2006

No further details available

version 4.0.4 - posted on Apr 11, 2006

Enhancement: Transactions: Session Id in URL. Handling of session variables in the URL by injecting dynamically generated session ids into subsequent Watch Items that are steps within a transaction.
Enhancement: Transactions: More detailed logging of 301 and 302 redirects.
Enhancement: Transaction Recorder: Most popup windows are now handled and displayed in the Transaction Recorder window.
Enhancement: Added new WebWatchBot preference: Redirect on HTTP 307: If True, WebWatchBot will automatically redirect to the URL specified in the header and/or content. Setting this option to TRUE (default) will cause WebWatchBot to act much like your browser does.
Enhancement: Added new WebWatchBot preference: Auto Redirect: If True, all HTTP redirects: 301, 302, and 307will be handled at a level lower than WebWatchBot normally handles redirects. Set this option to true if WebWatchBot is not properly handling individual redirects. This option overrides other redirection options.
Change: Transaction Recorder: Automatic detection of port number when a URL contains a port, e.g. http://www.domain.com:8080.
Change: Transaction Recorder: `about:blank` is no longer recorded. This is returned by some sites that popup windows.
Change: Transactions: If transaction steps are orphaned, three options are presented: keep, delete, or do nothing. Keep will make the Watch Item non-exlusive so that they operate independently, delete will permanently delete the Watch Item.
Bug Fix (4.0.4.1): HTTP Threads Simulate: If set to 0, an error will occur.
Bug Fix (4.0.4.2): WebWatchBot Security: If use encryption is False and a PassPhrase is present, sensitive data for imported Watch Items is still encrypted.
Bug Fix (4.0.4.3): Transactions: Statistical data is not updated properly in the GUI.
Bug Fix (4.0.4.4): Maintenance Mode: Added extra checks in Watch Item and Transaction threads for maintenance mode to prevent them from running during maintenance mode.
Bug Fix (4.0.4.5): Real-Time Chart: Corrected issue of data not reflecting real-time data if switching between the Performance Chart and the Real-Time Chart when the Performance Chart contains more data points than the Real-Time Chart.
Bug Fix (4.0.4.6): Database: Properly removing records from WatchDatabase table when a WatchItem is deleted.
Bug Fix (4.0.4.7): Watch Item and Transaction Test: A number of issues with testing Watch Items and Transactions have been resolved. The `Cancel` button in the test window has been removed. Transaction steps no longer add to the historical data.
Bug Fix (4.0.4.8): Watch Item: Deleting a Watch Item that is part of a transaction, reversed the execution order of the steps within the transaction.

version 4.0.3 - posted on Mar 21, 2006

Enhancement: Added alarm conditions, giving better control over how Watch Items fail and succeed. Response Time Threshold has been moved to this screen.
Enhancement: WebWatchBot Preferences: 3 new settings in the Common -> Watch Types -> HTTP/HTTPS section: HTTP retries, HTTP send timeout, HTTP receive timeout.
Enhancement: HTTP Watch Types: Response time broken down to show web page response time, number of images downloaded and response time total (if applicable).
Enhancement: Watch Items: New option "Trace Route On Failure (Database Watch Types Excluded)".
Change: Watch Item and Transaction Testing
Bug Fix (4.0.3.1): Performance chart: When switching from one Watch Item to another, then selecting chart options, the current chart s settings are overwritten with the previously selected Watch Item s chart settings.
Bug Fix (4.0.3.2): Alarm Reset: Resetting a Watch Item that is part of a transaction and transaction exclusive may not reset when "Reset Alarm" is performed manually even though the log will show that the Watch Item is Up.
Bug Fix (4.0.3.3): Email Alerts with Reports: Email alerts that include a report with a chart cause an error in WebWatchBot when the alarm is triggered.

version 4.0 - posted on Feb 07, 2006

Enhancement: Transaction Recorder
Easily record transaction steps by using the built-in browser.
Enhancement: Status Report: Continuously updated status report that is displayed in the UI and can be copied to your webserver or uploaded via FTP.
Enhancement: Chart settings: Chart settings saved for each individual Watch Item.
Enhancement: New Watch Type: Database. Connect to a database via connection string, execute a query, and search query results for search text.
Enhancement: Connectivity Monitor: Select a Watch Item that is used to determine that connectivity to the network and/or the Internet has been lost.
Enhancement: Watch Items and Transactions: Added new tab to Watch Item properties named `Schedule` to view, add, edit, and delete scheduled items.
Enhancement: Database Management: Old historical records can now be removed on demand
Enhancement: Watch List: Orphaned transaction steps
Watch Items that are transaction exclusive and are not not assigned to a transaction
are now displayed with purple text.
Enhancement: Email Alerts: Added two new fields `Subject` and `Additional Message Text`, providing extra customization to email alerts for an Alarm.
Enhancement: Watch List: Added two options to toggle showing Transactions and Watch Items that are steps in a transactions in Watch Lists that are filtered by status, e.g. All, Up, Down, etc. This option added to reduce the number of Watch Items displayed on installations with more than 100 Watch Items.

version 4.0.1 - posted on Jan 26, 2006

Enhancement: WebWatchBot Security
Encryption of Sensitive Data.
Enhancement: Transaction Recorder
Easily record transaction steps by using the built-in browser.
Enhancement: Status Report: Continuously updated status report that is displayed in the UI and can be copied to your webserver or uploaded via FTP.
Enhancement: Chart settings: Chart settings saved for each individual Watch Item.
Enhancement: New Watch Type: Database. Connect to a database via connection string, execute a query, and search query results for search text.
Enhancement: Connectivity Monitor: Select a Watch Item that is used to determine that connectivity to the network and/or the Internet has been lost.
Enhancement: Watch Items and Transactions: Added new tab to Watch Item properties named `Schedule` to view, add, edit, and delete scheduled items.
Enhancement: Database Management: Old historical records can now be removed on demand
this feature was previously only available during scheduled maintenance periods.
Enhancement: WebWatchBot Preferences: Restarting the UI is no longer required when making changes. If needed, the service is restarted through the UI.
Enhancement: Watch List: Orphaned transaction steps
Watch Items that are transaction exclusive and are not not assigned to a transaction
are now displayed with purple text.
Change: License keys can be de-activated, enabling transfer of license keys to different computers.
Bug Fix (4.0.1.1): Modifying the Watch Type of multiple Watch Items and Transaction properties causes Transactions to stop running.
Bug Fix (4.0.1.2): Starting WebWatchBot Manager in Application Mode, then switching to Service Mode. The service will not start until WebWatchBot Manager is restarted.

version 4.0 - posted on Jan 10, 2006

No further details available

version 3.0.10 - posted on Oct 07, 2005

Enhancement: Transactions: Persist Form Data
This option will cause all steps after the first to use form data from the previous step. For example if step one has a form variable with a name that matches a form variable on step two, the value from step one will be persisted on step two.
Enhancement: Reports (HTML format): Report images are now copied along with HTML of the report to the destination directory specifed in the report setting `Output Filename`.
Enhancement: HTTP/HTTPS Watch Types: Added new field `Header`
Optional. Allows custom HTTP headers to be set.
Bug Fix (3.0.10.1): Transactions: When a transaction without a step is tested, the test window hangs and does not provide a way to exit. Added a warning message and now allowing the window to be closed.
Bug Fix (3.0.10.2): Watch Item Copy: Copying a Watch Item causes updates to the Watch List to stop until the UI is restarted
Bug Fix (3.0.10.3): Transactions: Removal of an intermediate step will cause step order to have a gap and not execute properly until the transaction summary is updated.
Bug Fix (3.0.10.4): HTTP/HTTPS Watch Types: Broken images in Output window pane caused by https pages referencing http pages and vice-versa.
Bug Fix (3.0.10.5): Transactions: Transaction steps not properly updating statistics in UI.
Bug Fix (3.0.10.6): HTTP/HTTPS Watch Types: A Watch Item run that fails may display the output from the last run, though no data (HTML) was actually received.
Bug Fix (3.0.10.7): Scheduled Reports: If one report from one Watch Item is scheduled to run twice or more at the same time, the application will crash. Logic added to make any subsequent runs of the same exact report wait until prior runs have completed.
Bug Fix (3.0.10): Various minor bug fixes.

version 3.0 - posted on Oct 06, 2005

No further details available

version 3.0.9 - posted on Sep 09, 2005

Bug Fix (3.0.9.6): Various minor bug fixes.

version 3.0.8 - posted on Aug 03, 2005

Bug Fix: DNS Watch Type: Lookup types not properly saving after modification.
Bug Fix: Delete Last Watch Group: Deleting the last Watch Group will cause an error in WebWatchBot Manager
bug introduced in v3.0.7.
Bug Fix: Alarm Action Command: Total length of command and parameters expanded to 255.
Bug Fix: When sending support a `Full Report`, the communication logs are now copied to ensure that they can be sent. Previously, files may have been locked, preventing the full logs from being sent.
Bug Fix: Various minor bug fixes.

version 3.0.7 - posted on Jul 11, 2005

Bug Fix: Crash: Various bug fixes that caused trial version to unexpectedly stop running on Windows 2003 SP1.
Bug Fix: Transactions: Crash when adding or updating a transaction while it is executing.
Bug Fix: Visual Alert: HTTP/HTTPS Watch Types
images appear broken.
Bug Fix: Alarm Action Command: After adding command(s) and/or URL(s) settings are saved, but do not always re-appear when editing after the first time.
Bug Fix: Alarm Action Command: If the command does not include a full path, an error message will appear. Removed this restriction to allow execution of programs that are in the SYSTEM PATH.
Bug Fix: Charting Transactions: Stacked charts for transactions should always be ordered by correct execution order.
Bug Fix: Invalid CA: HTTPS Watch Types that monitor pages which return an error dialog with the message `The certificate authority is invalid or incorrect` now bypass the error message and load the page.
Bug Fix: Schedule Items: After creating a Watch Item and selecting a report, changing the Watch Item causes the scheduled item to lose the report scheduled without notification.
Bug Fix: Schedule Items: Editing an existing schedule item that runs a report, the selected report is lost.
Bug Fix: Floating Window Panes: If a window pane, e.g. Real-Time Chart View, Performance Chart View, etc., is left open when the WebWatchBot Manager application is closed a crash would occur in previous versions. Now, the entire layout is reset to the default if a window pane is left floating.

version 3.0.6 - posted on Jun 14, 2005

Enhancement: Added new WebWatchBot preference: Redirect on HTTP 301: If True, WebWatchBot will automatically redirect to the URL specified in the header and/or content. Setting this option to TRUE (default) will cause WebWatchBot to act much like your browser does.
Change: Single quote allowed in Watch Item name, Group name, and Transaction name.
Bug Fix: Memory Leak caused by Old historical data removal
Bug Fix: Reports double-run: When running WebWatchBot as a Windows service, and if the manager is open when a scheduled report runs, the scheduled report(s) will run twice.
Bug Fix: Resolved date formatting issues with the Scheduler.
Bug Fix: Various minor bug fixes.

version 3.0.5 - posted on Jun 01, 2005

Enhancement: Execute Command on Alarm Reset: Added Watch Item alarm actions to execute an external program or URL upon alarm reset.
Enhancement: Real-Time Chart options: Specify the maximum number of units in milliseconds, or variable number of units (default and previous version setting).
Enhancement: Relative date ranges for reports: Report date ranges now include the option to specify `today`, `yesterday`, etc. in addition to specific start and end dates.
Enhancement: Relative date ranges for Response Time Chart: Response Time Chart date ranges now include the option to specify `today`, `yesterday`, etc. in addition to specific start and end dates.
Enhancement: Schedule Database Maintenance: Scheduled Items of type `Maintenance` now have two new options: `Compress and Repair` WebWatchbot database
MS Access database and for `All Watch Items` schedule entry
and `Remove old records` where you may instruct WebWatchBot to remove old records from All Watch Items or a selected Watch Item.
Enhancement: Old historical data removal: Scheduled Items of type `Maintenance` now have two new options: `Compress and Repair` WebWatchbot database
MS Access database and for `All Watch Items` schedule entry
and `Remove old records` where you may instruct WebWatchBot to remove old records from All Watch Items or a selected Watch Item.
Enhancement: Added custom header to email alerts: X-Urgent
Enhancement: Added `Refresh` menu item to `View` menu and to `Secondary` toolbar. Clicking on refresh when in the Dashboard View will reload all charts.
Change: Scheduled Items: New button `Type Settings` to set schedule type specific settings. Report list drop-down, `Add` and `Edit` buttons moved to Type Settings dialog for Schedule Report dialog.
Change: WWBCmdLine, log file is no longer appended to. If the log previously exists, then it is cleared before it is written to again.
Change: Response Time Chart aptly renamed Performance Chart.
Bug Fix: Scheduler: Right-click on scheduler area, then click `Add` or `Edit` buttons causes program crash.
Bug Fix: Transactions: Crash when adding or updating a transaction while it is executing.
Bug Fix: Enterprise/Trial version, using MS SQL Server: During extended maintenance periods for `All Watch Items`, the connection to SQL server can be broken. New program logic has been added to re-establish connections shortly before the maintenance period ends.
Bug Fix: Non-US date formatting: Numerous dates were displayed in US MM/DD/YYYY format. Corrected dates to reflect regional date format.
Bug Fix: Various minor bug fixes.

version 3.0.4 - posted on Apr 26, 2005

Bug Fix: WWBCmdLine: Fixed bug with Clear Statistics, preventing stats from being cleared.
Bug Fix: Added Logic to remove orphaned transactions, which may have been left behind in version 3.0.
Bug Fix: Standard and Professional versions were limited to a maximum number of Watch Items of 24 and 49 respectively.
Bug Fix: Updates to the Log and Output pane not being updated when the WebWatchBot service running under an account other than the `System` account or the `System` account is not configured to `Allow service to interact with desktop`
Bug Fix: Setting the interval to less than 15 seconds causes crash after second performance warning.
Enhancement: Added new WebWatchBot preference: Redirect on HTTP 302: If True, WebWatchBot will automatically redirect to the URL specified in the header with the `Location:` attribute. In some cases, due to network configuration, automatic redirects do not occur automatically and this setting needs to be set to TRUE.
Enhancement: Added new WebWatchBot preference: Start Delay: Maximum number of milliseconds to delay between starting each active thread when WebWatchBot starts. This delay is necessary when more than 50 Watch Items are configured to prevent performance problems caused by too many Watch Items running simultaneously.
Enhancement: Added new WebWatchBot preference: Warm Up: If a number greater than 0 is specified, WebWatchBot will discard statistics collected for the number of runs specified.
Enhancement: Enterprise/Trial version, using MS SQL Server: Added several new indexes.
Change: `Run all Watch Items at start up` WebWatchBot preference moved in WebWatchBot Preferences from Common, General section to Advanced, General Section

version 3.0.3 - posted on Mar 22, 2005

Bug Fix: Running WebWatchBot as a Windows Service now works through Remote Desktop/Terminal Services. The incompatibility issue has been resolved.
Bug Fix: Upgrade process: When adding columns, if the column exists an error is raised for non-English Windows installations.
Bug Fix: Enterprise/Trial version, using Remote Connection: Resolved a number of issues with Remote Connection functionality.
Bug Fix: Corrected potential problem with scheduling reports where an error message regarding duplicate layers is displayed.
Bug Fix: Fixed crash caused when in Scheduler View, selecting the menu items Edit->Delete or Edit->Properties when no scheduled item is selected.
Bug Fix: Double-run after Watch Item ends maintenance period.
Bug Fix: After individual Watch item maintenance mode ends, there is a delay until the first time the Watch Item is run. The delay has been eliminated.
Change: The requirement for the WebWatchBot Service (named WWBServer in the Windows Services list) to run under the system account has been removed. You can specify any valid Windows login account.

version 3.0.1 - posted on Mar 02, 2005

Enhancement: Reports can now use date ranges that include a specific time.
Bug Fixed: Enterprise/Trial version, using MS SQL Server. The uptime/downtime chart in the dashboard displays no data.
Bug Fixed: When a transaction is selected and displayed in the `Explorer`, when creating a new watch item, one is prompted to add it to the current transaction. If the answer is `yes`, the Watch Item is properly added to the transaction.
Bug Fixed: BUG11Feb2005 : WebWatchBot Maintenance Schedule
When running WebWatchBot as a Windows Service: Adding, changing or deleting a scheduled maintenance window for `All Watch Items` requires a service restart to take effect.
Bug Fixed: Report Summaries now accurately reflect date range if specified in report settings.
Bug Fixed: Deleting a scheduled item through the menu option: Edit -> Delete -> Delete Scheduled Item could cause an error or the deletion of the wrong scheduled item.
Bug Fixed: Enterprise/Trial version, using MS SQL Server. Data type for HistoryItem table are `smalldatetime`, should be `datetime`. Upgrade process will fix this error, or can be manually altered through SQL Server tools.
Bug Fixed: After clearing stats, the real-time chart would increase the number of maximum data points until the chart is refreshed.
Bug Fixed: Some data points in the data editor have blank labels.
Bug Fixed: Minor bug fixes

version 3.0 - posted on Jan 12, 2005

New features include:
Scheduler: Schedule maintenance periods for individual or all Watch Items. Detailed maintenance periods can be one-time or recurring. Extensively detailed maintenance patterns can be configured. For example, one a day, once a weekday, once a week, Fridays only, etc.
Schedule reports for individual Watch Items. Detailed execution times can be one-time or recurring. Extensively detailed recurrence patterns can be configured
Dashboard: Gain an instant understanding of your monitoring through the WebWatchBot Dashboard. Key features such as Failing Watch Items, Slow Watch Items, Uptime/Downtime, and Health Status, will help you take action.
SQL Server Integration: WebWatchBot and Microsoft SQL Server(7/2000) provide an high performing and scalable solution for your server monitoring needs.
Remote Connectivity: Remotely connect to your WebWatchBot installation over tcp/ip through a remote connection.
Email a Report: Send a report via email to one or more recipients. Schedule reports to execute and have them emailed automatically.

version 2.1.5 - posted on Dec 14, 2004

Bug Fixed: Response time for a test should be closer to actual run for HTTP/HTTPS Watch Types.
Bug Fixed: Response time for Ping Watch Types should be more accurate.
Bug Fixed: Occassional WebWatchBot Manager crash when running a test on a Watch Item.
Bug Fixed: Log file failed to initilize for new Watch Items until WebWatchBot Application/Server restart.
Bug Fixed: Running a test in the Watch Type Settings window for POP3 and SMTP types would cause a crash.
Bug Fixed: Running a test in the Watch Type Settings for POP3 and SMTP types would not reflect changes in fields in that settings window.
Bug Fixed: After clearing stats on a Watch Item, if the Real-Time view is visible when a new data point is added by the Watch Item running, an exception occurs.
Bug Fixed: Automatically wrap lines in alarm email address fields, and the post data field.
Bug Fixed: Sending of email alerts for Watch Items which are transaction steps would fail to send.
Bug Fixed: Email alert headings now display HTTP status code and explanation as intended.
Bug Fixed: Text color in outlook bar is now the default Windows Text color (from the system settings) instead of white, which is unreadable.
Bug Fixed: Snapshot feature for HTTP Search Settings, now will pass username/password authentication, cookies, and post data if specified.
Change: The stored date and time for the last database maintenance is now stored as a number (total seconds since January 1, 1970) to correct a localization problem with determining when the last database maintenance was performed.
Change: Ping Watch Types now have a log file.
Change: If post data for HTTP Watch Types, contain a < (less than sign) as the first character, the Content-type will be automatically set to `text/xml`. By default the Content-type is `application/x-www-form-urlencoded`
Change: The window layout for WebWatchBot Manager will be reset the first time this version is installed and run.
Change: Circular log type has been removed since it has been widely reported to cause problems.
Change: Minor cosmetic changes.

version 2.1.4 - posted on Oct 10, 2004

Version 2.1 and up includes transaction monitoring.

version 2.1.2 - posted on Sep 19, 2004

Minor bug fixes and enhancements

version 2.1 - posted on Jul 31, 2004

Major change: Transactions. WebWatchBot provides the functionality to execute, in a defined sequence, one or more watch items that collectively form one entity for monitoring known as a Transaction.
Though Transactions are commonly a series of web pages, WebWatchBot allows any Watch Type, e.g., SMTP, POP3, HTTP, etc., to be executed within a Transaction.

version 2.0.2 - posted on May 09, 2004

5 new monitoring types added: SMTP, POP3, FTP, Port, and DNS. Enhanced HTTP and HTTPS monitoring: Post data, set cookies, and authentication. Real-time charting including ability to copy-and-paste chart and data, print chart, and chart multiple items for comparison. Optionally runs as a Windows Service. Data is stored in a SQL compliant database for easy export and custom reporting. Now includes command line interface for scheduling of reports.

version 2.0.1 - posted on Apr 08, 2004

Bug fixes and minor enhancements

version 2.0 - posted on Mar 02, 2004

No further details available

version 1.1.4 - posted on Dec 23, 2003

No further details available