Nimsoft Monitor url_response Release Notes - Nimsoft Library

ASSESSMENT | PLANNING | MANAGEMENTWARRINGAHLOCAL GOVERNMENT AREAHAZARD REDUCTION GUIDELINESReport prepared for:Warringah Council(Project No. 57-14)May 2006ABN 87 096 512 088 | address Suite 503 3-5 Stapleton Ave Sutherland NSW 2232postal PO Box 12 Sutherland NSW 1499 | phone 02 8536 8600 | fax 02 9542 5622web www.ecoaus.com.au

Contact NimsoftFor your convenience, Nimsoft provides a single site where you can access informationabout Nimsoft products.At http://support.nimsoft.com/, you can access the following:■■■■■Online and telephone contact information for technical assistance and customerservicesInformation about user communities and forumsProduct and documentation downloadsNimsoft Support policies and guidelinesOther helpful resources appropriate for your productProvide FeedbackIf you have comments or questions about Nimsoft product documentation, you cansend a message to support@nimsoft.com.

ContentsChapter 1: url_response General Overview 7Chapter 2: Requirements 9Hardware Requirements .............................................................................................................................................. 9Software Requirements ............................................................................................................................................... 9Supported Platforms .................................................................................................................................................... 9Chapter 3: Considerations 11Installation Considerations ......................................................................................................................................... 11Chapter 4: Fixed Defects 13Revision History .......................................................................................................................................................... 13Contents 5

Chapter 2: RequirementsThis section contains the requirements for the url_response probe.This section contains the following topics:Hardware Requirements (see page 9)Software Requirements (see page 9)Supported Platforms (see page 9)Hardware RequirementsThe url_response probe should be installed on systems with the following minimumresources:■■Memory: 2-4 GB of RAM. This probe OOTB configuration requires 256 MB of RAM.CPU: 3 GHz dual-core processor, 32-bit or 64-bitSoftware RequirementsThe url_response probe requires the following software environment:■ Nimsoft Monitor Server 5.1.1 or later■ Nimsoft robot version 5.23 or later■ Java Virtual Machine version 1.6 or later (deployed as part of the probe package)Note: For SOC functionality, NM Server 5.6 or later and UMP 2.5.2 or later is required.Supported PlatformsThe url_response probe supports the same set of operating systems and databases assupported by the Nimsoft Server solution. Please refer to the Nimsoft CompatibilitySupport Matrix for the latest information on supported platforms.Chapter 2: Requirements 9

Chapter 3: ConsiderationsThis section contains the considerations for the url_response probe.This section contains the following topics:Installation Considerations (see page 11)Installation ConsiderationsThe default installation directory for url_response probe has changed to /probe/application from/probe/network. This is applicable for versions 3.7x and above. If you downgrade to probe version lower than3.71, the config files will not merge.Some web servers require user authentication. The url_response probe normally transmits user information asspecified in the HTTP / HTTPS protocols. This will normally work with webpages where on interactive use thebrowser will prompt for logon information.When the web pages implement their own logon screen, you will normally have to use the E2E ApplicationResponse Monitoring.In Microsoft environments, authentication with web servers and proxy servers is normally of the 'Basic' type. if'Windows Integrated Authentication' is required, the 'Windows NT Authentication' check box in the profile mustbe selected. Proxy settings will then be fetched from the registry, as saved by Internet Explorer.Because of limitations in the libraries used, problems can occur on multi-processor computers. If problems occur,the probe can be made to run in synchronous mode (fetching one URL at a time) by setting the force_synchronousflag in the setup section of the configuration file. Please note that this will limit the number of profiles the probewill be able to handle.In the case of fast networks, if the ignore connection time option is selected then the response time of the URLmay sometimes be below 1 millisecond. This will be reported as 0 in the probe.Chapter 3: Considerations 11

Chapter 4: Fixed DefectsThis section contains the fixed defects for the url_response probe.This section contains the following topics:Revision History (see page 13)Revision HistoryThis section describes the history of the revisions for this probe.Date Description State VersionFeb 2013 Added Probe Defaults for the probe GA 4.14Nov 2012 ■ Added Support For Ubuntu/Debian/CentOS- 64Bit Debain&Ubuntu-32 BitGA 4.13■Fixed: Issue of memory leak.Sep 2012 ■ Fixed Issues related to SSL Certification Fixed Certificationerror related to severity Fixed Issue related to File DumpFixed Issue related to 35SSL Connect error Fixed Issue relatedto form authentication■Added Support for Debian/Ubuntu for Peer1 for libc.so.6Jan 2012 Added fix to Can’t get source field for QoS messages. 4.11Dec 2011 ■ Added support for IPv6. Added fix to send clear alarm on eachinterval if "sendAlarmOnEveryInterval" is set to "yes" in theCFG and no threshold is breached.■Fixed minor bugs in the GUI4.124.10Chapter 4: Fixed Defects 13

Revision HistoryDate Description State VersionJul 2010 ■ Added support to send alarms after collecting all samples.■■Added fix to content matching in page when Windowsauthentication is enabled.Added fix to handle the lookup failures when a monitoredURL has port numbers.09.07.2010 ■ Added support for Solaris platform.3.813.80■■■Added fix to allow variables in "Alarm source override" field.Added fix to properly rename the profile names.Added fix for NIS defect.Jun 2010 Made changes to libraries with respect to configuration locking. 3.71May 5 2010 ■ Changed the probe installation folder from Network toApplication. (Please refer to the Installation notes section)May 5 2010Sep 30 2009■■■■■■Added support to prohibit use of white space in the probeconfigurator.Fixed the issue of look for substring in content failure.Fixed issue of QoS column in profile view does not work.Fixed issue of profile not getting created through wizard.Added support for virtual host name.Added support for extended NIS database information.Added support for mapping the custom delayed messages toprofiles.Changed the response time to total time provided by curl insteadof nimbus timer.3.703.643.63Chapter 4: Fixed Defects 15

Revision HistoryDate Description State VersionSep 9 2009Added sampling for:1.DNS resolution time2.Time to first byte3.Time to last byte4.Download time5.Redirect Time6.TCP Connect Time3.62Added alarm and QoS for:1.DNS resolution time2.Time to first byte3.Time to last byte4.Download time5.Redirect Time6.TCP Connect TimeAdded bug fixes in GUI.Added new profile form in GUI.Added QoS for string found.Aug 25 2009Fixed problem running on Linux without dynamic librariespresent. (This was a problem in new installations of version 3.5x.Upgrades worked OK).3.53Aug 21 2009 ■ Added support for SSL handling in case of windows and curl.3.60■■■■■■Added retry support before sending String found/not foundalarms in case of forwarded urls.Support for overwiting of the subsystem ID.Enhancements and Bug fixes in GUI."No thread available" alarms are now not sent if it is the firstrun of the profile.Proper termination of the retry while loop in case of restartsand probe shutdown.Added feature to ignore connection time in url response QoSand alarms.16 url_response Release Notes

Revision HistoryDate Description State VersionJan 2009 ■ Fixed issue of missing SubsystemID in default clear alarm.3.52■■■■■■■■Added the error code for invalid certificate.Fixed the issue with https and nt-authentication.Fixed the issue of "NimBUS" as user agent in case of windowsauthentication even if overriden by user.Fixed problem with test function and passwords.Corrected handling of https when used in conjunction withWindows NT authentication.Fixed handling of url options when using Windows NTauthentication.Added schedule for profilesGrouping support for profile list.■ Added Support for windows 2008, linux 64 and windows 64bit.■■■■User defined clear message.Added alarm on fetched bytes threshold.Added alarm on load time below threshold.Moved critical section initalization to after configuration fileread, as the critical section may not be used depending onconfiguration parameters.Jul 25 2008 Linux: removed references to IPWorks library. 3.42Jul 10 2008 ■ Resolved Configuration tool crash on Alarm MessageOverrides occuring when undefined messages were defined.■■■Implemented timeout in use of new underlaying libraryintroduced in version 3.40.Modified thread handling on restart and stop to allowunfinished threads to complete.Added alarm message for delayed execution of profiles. Thissituation can occur when a profile is still running or when nothread is available for profile execution.Jun 2008 ■ Changed underlaying library to be able to resolve issues onLINUX.■■Modified configuration tool to disallow specifying an emptystring as a profile name as this resulted in removal of allnon-modified profiles.Added option to set user agent string.3.413.40Chapter 4: Fixed Defects 17

Revision HistoryDate Description State VersionApr 2008Modified configuration tool to disallow specifying an empty stringas a profile name as this resulted in removal of all non-modifiedprofiles.Known issues: This version and previous versions running onLinux have a bug in a library which can cause the probe to hog cpuand hang or crash. A new version solving this problem will bemade available as soon as old functionality has been ported andverified using the new library.3.31Feb 2008 ■ LINUX package requires Robot 2.65 or higher to avoidinstallation problems.3.29Nov 2007■Hanging thread problem on Linux systems fixed.Updated underlaying library to resolve problem with ok returncode on LINUX when the web server was actually not available.3.27Sep 10 2007 ■ Fixed occasional program failure on probe restart.■Fixed alarm message handling for the 'config_error' alarmsituation.Sep 7 2007 ■ All platforms: Fixed serious memory leak when called fromlogmon.■LINUX: Explicit dependency on Robot >= 2.60 added to thepackage to ensure that a suitable glibc is available oninstallation.Feb 2007 ■ Fixed problem with NTLM authentication against proxyserver.Nov 2006■■■■Added option to set alarm source for each profile.Added support for saving page to disk if status indicates thatfetch was unsuccessful.Added support for encrypted passwords when fetching pageson behalf of another probe or GUI (test_url callback).Linux version added. Note: Glibc v2.3 required to run thisprobe! Test_url callback threaded to allow pages to befetched on behalf of other probes.Fixed expansion of variables again. Now all available variables isexpanded for all message types.3.263.253.233.20Aug 2006Additional flags set when using Windows Authentication to fixissue with redirection from a non-SSL to a SSL connection.3.1918 url_response Release Notes

Revision HistoryDate Description State VersionJul 2006 ■ Additional flags set when using Windows Authenticationwithout username/password.■■Fixed issue regarding alarms not being updated/cleared(Probe hung because RECEIVE timeout was not set when'Windows NT Authentication' was used ).Mar 2006 ■ New version of IP*Works for better support of Windows 2003Server.■■Implemented language option for HTTP Get.General error corrections.Nov 2005 ■ Fixed expansion of variable $url3.183.163.15■Fixed minor bugs in ConfiguratorIt is now possible to insert regular expressions when looking forsubstrings in page content.Jul 2004 ■ Additional QoS value: Fetch time in bytes per second.3.13■Added 'Accept' headersChapter 4: Fixed Defects 19