|
Date
|
Description
|
State
|
Version
|
|
|
|
|
|
17.03.2022
|
What's New:
- Updated the logmon MCS to v4.20
Fixed Defects:
- Previously raised 'Exit Code Monitoring' alarms are not getting cleared when the threshold is not breached in the next polling interval.
Support case 32756543
- 'Send Message using Specific Subject' field does not exist in Log Monitoring (Enhanced) template.
Support case 32788038
- The "maximum alarm count" doesn't appear to work correctly.
Support case 32757028
- Unable to save multiple profiles for the 'Format Rules' template in MCS UI.
Support case 32849365
- In the MCS template, when creating the Logmon watcher rule with default severity, severity information is not getting saved.
Support case 32528497
- While creating the MCS template, the QoS metric for the variable sections is getting grayed out and is not editable.
Support case 32902364
- $FILENAME variable value is not resolved to the actual file name when a wild card (*) is used in the file path.
Support case 32905657
SHA-256 Checksum: 9c3c86721dd6426198296bab677d4efa54d0b7485a13499c9730ba2b6752e89f
|
GA
|
4.20
|
|
|
|
|
|
19.07.2019
|
What's New:
- Added subsystem ID for exit code monitoring in the command mode. You can now over-ride existing subsystem ID for alarms. For more information, see logmon Advanced AC Configuration and logmon Advanced IM Configuration.
- Enhanced the logmon MCS (version 4.12) to include dynamic QoS to publish QoS and computed baselines. For more information, see logmon MCS Profile Type Configuration.
Fixed Defect:
- Fixed an issue where the variable WATCHERMATCHEDLINE did not work as expected. Support case: 01259593
For more information, refer https://docops.ca.com/rest/ca/product/latest/topic?hid=logmon_RN&space=UIMPGA&language=&format=rendered
MD5 Checksum: 845116f3a9f14306e2ee366b40a9f08c
SHA-1 Checksum: d86d13bc76f1f59efb176d03032dc58858f9bbf6
|
|
4.11
|
|
|
|
|
|
18.02.2019
|
What’s New:
- Enhanced the probe to support adding a property for tracking 'updates' (events added) to the body of an existing log file, without reading the whole file again.
For Detailed Release Notes-Please refer
https://docops.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=logmon_RN
Note: Support case(s) may not be viewable to all
MD5 Checksum: 456c9010b7ea964f348cd0a6864659cf
SHA-1 Checksum: 05f059db38fea255214a732bce8378ac54884fb4
|
|
4.10
|
|
|
|
|
|
08.10.2018
|
What’s New:
- The probe now generates number of alarms specified in the Max Alarm Count based on the Suppression Keys. For more information, see logmon IM configuration and logmon AC configuration.
- (AC, IM, and MCS Interface) Added Excludes at the Watcher level. In the previous version of the probe, Excludes were present at the profile level only. For more information, see the IM configuration, AC configuration, and MCS configuration
- (AC, IM, and MCS Interface) Added Directory Recursion check box and Number of levels to Recurse field to allow the probe to look into the specified number of directories/folders to find a matching file pattern. For more information, see the IM configuration, AC configuration, and MCS configuration
For Detailed Release Notes-Please refer
https://docops.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=logmon_RN
Note: Support case(s) may not be viewable to all
MD5 Checksum: f7e955185f7f2ceec06efe5d612900d5
SHA-1 Checksum: b603295106dbcf9dd784465d7c2331fb23a232ea
|
|
4.00
|
|
|
|
|
|
13.02.2018
|
Fixed Defects:
1. The probe started reading the log file from the beginning after the probe was restarted. Salesforce Case: 00802824
2. The probe failed to start when upgrading to 3.91 on some Linux systems. Salesforce Case: 00873778
3. The probe was running out of available threads when the threads were not terminating properly and were aborted after some time. Salesforce Case: 00682136
4. The probe was saving a variable created using MCS template with ‘Ignore “To”’ configuration as ‘To End of Line’. Salesforce Case: 00668211
5. The probe version 3.91 failed to start on some Linux systems. Salesforce Case: 00920811
For Detailed Release Notes-Please refer
https://docops.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=logmon_RN
Note: Support case(s) may not be viewable to all
SHA-1: 532c42164815453ffb534583a8ea8127ab449443
MD5: 530b9c26b54a1bc78d7a7c626ce80dee
|
|
3.92
|
|
|
|
|
|
16.10.2017
|
What's New:
- Introduced the Variable Exceed Alarm, which generates alerts when the variables exceed or match the operator value.
Fixed Defects:
- The probe was creating core dumps. Salesforce case: 00606262
- The probe was not working on the SunOS 5.10 Generic_125101-04 i86pc operating system. Salesforce case: 00712559
- The field Send clear alarm was not available for MCS Profile Type Monitoring of the probe. Salesforce case: 00764177
- The user was not able to configure variables using MCS Profile Type Monitoring. Salesforce case: 00668211
- The probe configurations were impacted with the character limit on the Run Command On Match parameter in MCS Profile Type Monitoring. Salesforce case: 00840150
For Detailed Release Notes-Please refer to
https://docops.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=logmon_RN
Note: Support case(s) may not be viewable to all
md5sum: bcfe7a058195a63c5265336800e3ba2b
sha1sum: 98befaca6b5b4eee8b4f2fdf8508b34ab8a4f5bd
|
|
3.91
|
|
|
|
|
|
18.04.2017
|
What's New:
- Added support to test profiles using regular expressions in file path. Support case number 658483
- Added support for internationalization on AIX 64 Bit and HP-UX IA 64-Bit platforms.
Fixed Defects:
- The probe did not convert values in non-English locales to decimal values in QoS messages. Support case number 505302
- The probe was unable to monitor URLs with the % symbol. The probe incorrectly expanded the % symbol in URL profiles as time formatting primitives. Support case number 643969
Important! This version of the probe does not support FIPS encryption.
For Detailed Release Notes-Please refer to
https://docops.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=logmon_RN
Note: Support case(s) may not be viewable to all
md5sum: 1b361bd2078d657c1a4134de0bb42566
sha1sum: 673499005cca5e2053499c2fc95470f76f827eef
|
|
3.90
|
|
|
|
|
|
12.04.2017
|
What's New:
- (IM Interface only) Added support for:
- AES-128 encryption that is required for FIPS compliance
- Monitor Windows systems where FIPS encryption is enabled
For more information, see Enable FIPS Encryption and Probe Specific Changes After Upgrade sections.
Important! In a FIPS encryption enabled environment, you cannot configure the probe from Admin Console (AC) interface.
md5sum: 7e8940367ff53c6225527fd44446e327
sha1sum: 68e3574abc9dfafe2c838b1ac37e8ea25b2cac91
|
|
3.80
|
|
|
|
|
|
15.03.2017
|
Fixed Defect:
- For the AS400 systems, the probe was unable to search a text based on the regular expression. Support case number 00601757
- The probe was unable to generate alarms and QoS for the log files that were read from the HPUX system.
md5: e982fdc7953b8f82788cf2a08104d1c5
|
|
3.71
|
|
|
|
|
|
15.11.2016
|
What's New:
1. Test Command mode profiles from the Probe Utility interface.
2. Added alarm message and severity options for pattern match thresholds.
3. Configure missing file and clear alarms for individual profiles.
4. Use positive lookahead regular expression in the end expression of a format rule.
Fixed Defects:
1. (On iSeries platform) The probe did not monitor a .mbr file in the EBCDIC format. Support case number 521534
2. (On HP-UX platform) The probe did not display correct exit codes as SHELL and PATH variables were missing in the environment. Support case number 512468
3. (For Windows and UNIX platforms) Updated the probe documentation about using % as a variable in a filename or a command. Support case number 477760
For Detailed Release Notes-Please refer
https://wiki.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=logmon_RN
Note: Salesforce case(s) may not be viewable to all customers.
|
|
3.70
|
|
|
|
|
|
08.07.2016
|
What's New:
1. Added support to monitor log files that are greater than 2 GB. CA recommends you to monitor only the updates to large files. Monitoring large files from start can increase the CPU usage.
Note: The probe does not support monitoring of log files that are greater than 2 GB on 32-bit UNIX systems.
2. Added support to use multiple strings in regular expressions using UTF-8 encoded pattern files.
Fixed Defects:
The probe was unable to read UTF-8 files with special characters. Support case number 357073
For Detailed Release Notes-Please refer
https://wiki.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=logmon_RN
Note: Salesforce case(s) may not be viewable to all customers.
|
|
3.60
|
|
|
|
|
|
03.05.2016
|
Fixed Defects:
1. The probe was unable to read some files on AIX platform. Support case numbers 00284131, 00290605.
2. The CPU utilization of the probe was high when monitoring URLs in UTF-8 encoding. Support case number 00275815
3. When running on Japanese system, the probe generated illegible alarms when the system encoding was selected as UTF-8. Support case number 00272866
4. Updated the IM Configuration article to state that the probe does not support commands (such as Telnet) that require two way communication between the user and the system. Support case number 00268926.
5. Added a recommendation in the IM Configuration article to not use regular expressions while using the Enable File Missing/Open Alarm option to clear the missing file alarm. Support case number 00308935
For Detailed Release Notes-Please refer
https://wiki.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=logmon_RN
Note: Salesforce case(s) may not be viewable to all customers.
|
|
3.56
|
|
|
|
|
|
20.01.2016
|
Fixed Defects:
1. The probe did not correctly convert variable characters to defined file encoding in URL mode. Support case number 00245330
2. The probe did not support white spaces in paths for batch files. Batch files include commands that can be monitored. Support case numbers 00270650, 00246042
For Detailed Release Notes-Please refer
https://wiki.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=logmon_RN
Note: Salesforce case(s) may not be viewable to all customers.
|
|
3.55
|
|
|
|
|
|
01.10.2015
|
What's New:
Added support for IBM iSeries version V7R2.
Fixed Defects:
1. The probe was unable to read UTF-16LE files. Salesforce case 00169492
2. The probe was crashing with exit code functionality. Salesforce case 00169505
3. The probe was not able to retrieve complete command output in the command mode. Salesforce case 70001673
4. Updated document regarding localization support article. Salesforce Case 70002007
5. Updated the document regarding alarms in the url mode. Salesforce case 00163388
For Detailed Release Notes-Please refer
https://wiki.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=logmon_RN
Note: Salesforce case(s) may not be viewable to all customers.
|
|
3.54
|
|
|
|
|
|
04.08.2015
|
Fixed Defect:
The probe restarts when a variable was added to the sub-system id. Salesforce cases 00170003, 00169384, 00167502, 00168440, 00168601, 00166738, 00168537.
For Detailed Release Notes-Please refer
https://wiki.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=logmon_RN
Note: Salesforce case(s) may not be viewable to all customers.
|
|
3.53
|
|
|
|
|
|
30.06.2015
|
Upgraded support for factory templates.
Removed localization support on AIX platform.
Fixed a defect where probe was unable to detect “File encoding” when “File encoding” was selected from GUI. (Salesforce Case: 00167536)
For Detailed Release Notes-Please refer
https://wiki.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=logmon_RN
|
|
3.52
|
|
|
|
|
|
17.06.2015
|
Fixed internal defects
For Detailed Release Notes-Please refer
https://wiki.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=logmon_RN
|
|
3.51
|
|
|
|
|
|
08.06.2015
|
Added Features:
Upgraded OpenSSL to version 1.0.0m.
The probe now has an option to generate alarms only on the first match of regular expression (defined in Watcher Rule), in a specified interval.
Fixed Defects:
The regular expressions were not working with the defined threshold. (Salesforce Case: 00156818, 00159939, 00158632)
The probe was not generating correct exit code on windows, unix, linux, solaris and aix. (Salesforce Case: 00157528, 00160884)
Exit code variables were not expanding on USM. (Salesforce Case: 00161303)
Improved CPU usage of the probe. (Salesforce Case: 00153268)
For Detailed Release Notes-Please refer
https://wiki.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=logmon_RN
|
|
3.50
|
|
|
|
|
|
31.03.2015
|
The probe can now be migrated to standard static alarm thresholds using the threshold_migrator probe.
Added support for Factory Templates
For Detailed Release Notes-Please refer
https://wiki.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=logmon_RN
|
|
3.49
|
|
|
|
|
|
31.12.2014
|
Fixed Defects:
Entries for the QoS Variable having multiple targets were getting overlapped on the USM. (Salesforce Case: 00149257)
No Exit code alarm was generated on Windows OS in case command was not found. (Salesforce Case: 00150798)
View option in the GUI did not show updated file content. (Salesforce Case:00147856)
Probe stopped working when the number of characters in the match expression is greater than 1020. (Salesforce Case: 00145499)
No alarms were generated when the threshold applied on a watcher variable is breached. (Salesforce Case: 00137155)
The probe did not identify the UTF-16 log files. (Salesforce Case: 00139268)
For Detailed Release Notes-Please refer
https://wiki.ca.com/display/UIMPGA/Log+Monitoring+%28logmon%29+Release+Notes
Note:Salesforce case(s) may not be viewable to all
https://wiki.ca.com/display/UIMPGA/Log+Monitoring+%28logmon%29+Release+Notes
|
|
3.48
|
|
|
|
|
|
20.11.2014
|
New Feature:
Added a timeout option for the Command mode profiles to kill the command process and all its child processes after a defined time limit.
For Detailed Release Notes- Please Refer
http://docs.nimsoft.com/prodhelp/en_US/Probes/AdminConsole/logmon/ReleaseNotes/index.htm
|
|
3.47
|
|
|
|
|
|
21.10.2014
|
New Feature:
1. Added the localization support for AIX 64-Bit operating systems.
Fixed Defect:
1. Fixed a defect where the probe is reading the log file always from beginning when running in update mode. This issue occurred when the probe reads some unprintable characters. (Salesforce Case: 00136466)
2. Fixed a defect where the probe was writing text Debug to the log file when the log level is zero.
3. Fixed a defect where the probe was not identifying the PCRE space characters (/s) in a regular expression. This issue was also causing the probe crash on Linux and Solaris operating systems. (Salesforce Case: 00138780)
For Detailed Release Notes- Please Refer
http://docs.nimsoft.com/prodhelp/en_US/Probes/AdminConsole/logmon/ReleaseNotes/index.htm
|
|
3.45
|
|
|
|
|
|
22.09.2014
|
New Feature: added a Timeout option to kill an executing script and return the processing control to the probe.Fixed a defect where the -R option, which makes the monitoring start from the end of the file, was not working.Fixed a defect where logmon was not starting due to dependency on ICU lib files. (Salesforce Case: 00141353)
For Detailed Release Notes-Please refer
http://docs.nimsoft.com/prodhelp/en_US/Probes/AdminConsole/logmon/ReleaseNotes/index.htm
|
|
3.44
|
|
|
|
|
|
30.06.2014
|
Added the internationalization support for Simplified Chinese, Japanese, Korean, Spanish, German, French, Italian and B-Portuguese languages from VB GUI and WEB GUI
For localization support through WEB GUI probe must run with NMS 7.6 or higher version and PPM 2.34 or higher version
Added the support for zLinux environment.
Updated the probe VB GUI and WEB GUI for configuring the format interval and for specifying the character encoding in different locales.
Note: Do not use the Raw Configure for VB and WEB GUI for updating the probe configuration in the non-English locales because it can corrupt the entire probe configuration file.
For Detailed Release Notes-Please refer
http://docs.nimsoft.com/prodhelp/en_US/Probes/AdminConsole/logmon/ReleaseNotes/index.htm
|
|
3.42
|
|
|
|
|
|
21.02.2014
|
Enhanced the probe for making file missing/open alerts user-configurable with its clear alarms on probe restart
For Detailed Release Notes-Please refer
http://docs.nimsoft.com/prodhelp/en_US/Probes/AdminConsole/logmon/ReleaseNotes/index.htm
|
|
3.32
|
|
|
|
|
|
27.12.2013
|
Added feature to send alerts when files being monitored are missing or can't be opened
Added support for format rules monitoring blocks of data spanning multiple check intervals
Fixed functionality "abort on match" in case "match on every run" is also selected.
Fixed issue related to alarm subject not overwritten.
For Detailed Release Notes-Please refer
http://docs.nimsoft.com/prodhelp/en_US/Probes/AdminConsole/logmon/ReleaseNotes/index.htm
|
|
3.31
|
|
|
|
|
|
13.12.2013
|
Fixed issue related to alarm not sending for missing file.
Fixed issue related to alarm subject not overwritten.
Fixed issue related to Format rules dont work across check intervals.
|
|
3.30
|
|
|
|
|
|
15.10.2013
|
Fixed issue related to alarm subject not overwritten.
Fixed issue related to Invalid entries in callback crashes probe.
Fixed issue related to Probe PID changing.
|
|
3.27
|
|
|
|
|
|
05.09.2013
|
Fixed issue related to locale.
|
|
3.26
|
|
|
|
|
|
10.04.2013
|
Fixed issue related to logmon sending empty qos.
Fixed issue where Text profiles returns "0" instead of matching string as it used to.
|
|
3.25
|
|
|
|
|
|
14.03.2013
|
Added Probe Defaults
|
|
3.24
|
|
|
|
|
|
11.02.2013
|
Fixed memory leak issue on windows ,Linux and Aix machines.
|
|
3.23
|
|
|
|
|
|
11.01.2013
|
Fixed an issue of multi-line formats not matching with expected precidence.
Fixed issue related to incorrect alarms for JP Regex in watcher rule.
Fixed: AGL (mik) - Delete all profiles, error message runtime error 91.
Fixed below issues related to japanese.
Alarm in Japanese.
Expression in Japanese.
View File in Japanese character.
Open file with Japanese character in file name.
|
|
3.22
|
|
|
|
|
|
31.08.2012
|
Fixed crash issue on Linux
|
|
3.21
|
|
|
|
|
|
14.08.2012
|
Added fix for variable expanding in message string.
Added option to override alarm severity for max alarm message.
Added fix to clear max alarm only if error condition is returned to normal.
Added fix to support abort on match functionality in URL mode.
Added support for exit code monitoring when mode is set as command.
Extended format rule limitation to 200 lines.
Added support to refer entire text block as a variable.
|
|
3.20
|
|
|
|
|
|
11.06.2012
|
Fixed SOC Issue
|
|
3.13
|
|
|
|
|
|
28.03.2012
|
Fix Issue with QOS generation in test profile through GUI.
GUI fix:Test profile screen will now be opening even if the watcher contains a numeric name.
The help button will now display online help instead of CHM
|
|
3.12
|
|
|
|
|
|
15.03.2012
|
Fixed localization issue in soc
|
|
3.11
|
|
|
|
|
|
21.01.2011
|
Added fixes for web-based Service Oriented Configuration.
|
|
3.03
|
|
|
|
|
|
31.12.2010
|
Support for reading alarm tokens from cfg.
Added support for Web-based Service Oriented Configuration (SOC).
|
|
3.02
|
|
|
|
|
|
15.10.2010
|
Added fix to read a new file from beginning for the first time when "Updates" mode
is selected and "Match on every run" option is enabled.
e.g. When files are monitored based on time/day using %m,%M etc.
|
|
3.01
|
|
|
|
|
|
16.09.2010
|
Added support for wildcard characters in file-name.
Added support to configure severity and message for "Match on every run" option per watcher.
Added Support for internationalization.
Fixed the crash due to stack overflow.
|
|
3.00
|
|
|
|
|
|
15.09.2010
|
Fixed a problem with variables, when using with format definitions.
|
|
2.92
|
|
|
|
|
|
30.06.2010
|
Made changes to libraries with respect to configuration locking.
|
|
2.91
|
|
|
|
|
|
05.05.2010
|
Added NIS (TNT2) Support.
|
|
2.90
|
|
|
|
|
|
05.05.2010
|
Fixed the suppression key problem that was introduced in version 2.82
|
|
2.85
|
|
|
|
|
|
31.03.2010
|
Windows: Converted Command executable to short path name.
Fixed interaction between logmon and url_response probes
|
|
2.84
|
|
|
|
|
|
05.02.2010
|
Improved url_response probe interaction.
|
|
2.83
|
|
|
|
|
|
05.02.2010
|
Fixed problem with large suppression keys in max alarms alarm situation.
Enabled Source override for max alarm situation.
|
|
2.82
|
|
|
|
|
|
05.02.2010
|
Fixed File browsing for AS400.
|
|
2.81
|
|
|
|
|
|
30.12.2009
|
Added a feature to test a profile or individual watchers within a profile for regular expression.
Added a fix to set proper timeout.
|
|
2.80
|
|
|
|
|
|
30.09.2009
|
Fixed issue in underlying library where the probe would fail to find the correct file location when the file had been both truncated and appended to.
|
|
2.72
|
|
|
|
|
|
21.09.2009
|
Added a fix for monitoring files on non-domain machines in windows.
Added support for Linux systems with glibc 2.2.
Monitoring of files using UNC path is now possible.
Suppressing logic to avoid sending excessive alarms.
Fixed the issue of message variables not getting filled properly.
Message variable expansion fixed when match on every run is selected.
When both QoS and Alarm are selected for a profile only Variable QoS or number of matches (if selected) are sent.
Modified layout of QoS tab for Watchers in the GUI.
|
|
2.71
|
|
|
|
|
|
20.04.2009
|
Modified thread pool behaviour to avoid timing problems.
Added logging to show when a thread has been started.
Retry after 5 seconds if a thread is not available (was 60 seconds).
Fixed log file preview function to enable viewing the last section of large log files.
Removed numeric input checking on variable 'limit'.
Fixed configurator failure on creation of new QoS from watcher.
Disabled 'View' button for mode 'command'.
Fixed error situations in file browser.
Added support for Windows on Itanium 2 systems (IA64).
|
|
2.62
|
|
|
|
|
|
19.12.2008
|
Rebuild following NimBUS library fixes.
Modified pt-lib call to be able to detect log file changes when the file date was unchanged.
|
|
2.56
|
|
|
|
|
|
11.09.2008
|
Fix problem assigning variable from regex which contains just one character.
Fix problem expanding date primitives in path. Fix problem with last line in a multi-line format rule being skipped.
Bring 2.5x into line with changes made in the 2.4x series.
Fix potential problem with parsing of variables from a matched line.
Added support for 64-bit Windows (x64).
Please note that, for version 2.54 and higher of this probe, NimBUS Robot version 3.00 (or higher) is a prerequesite. You are advised to carefully read the document
"Upgrading the NimBUS Robot"
before installing/upgrading.
|
|
2.54
|
|
|
|
|
|
17.07.2008
|
Fixed potential problem extracting variables from a matched line.
Added dynamic buffer allocation for suppression keys.
Corrected several minor issues with the configuration tool:
- Advanced tab greyed out for url type profiles
- Wrong tooltip for 'Send clear alarm'
- Move up/down changed active state and upper/lower case profile name problems.
|
|
2.41
|
|
|
|
|
|
08.05.2008
|
Fixed a timing problem which could cause a line in the log file to be skipped by the next scan if it was written during the current scan of the file.
Does not post messages when not specified to do so.
QoS target defaults to profile.watcher when not specified.
Corrected parameter transfer on url View.
Modified handling of Exclude rules to minimize cpu usage when scanning files.
Allow wildcards in path names as well as file names.
|
|
2.39
|
|
|
|
|
|
19.12.2007
|
Fixed memory leak when probe is restarted.
Fixed potential thread deadlock upon failure to save last_run time.
Fixed issue with file offset being stored incorrectly when probe is stopped/restarted.
UNIX: Fixed incorrect time display in logfile and potential heap corruption issues due to a non-threadsafe system call.
Increased size of buffers used to store profile and watcher names. Fixed memory leak when alarm message was over 1024 characters.
Fixes segmentation violation due to failed compilation of a regex. Log an error message when a regex fails to compile.
Added support for editing archived configurations.
Enhanced configuration tool resize.
Fixed problem with $FILENAME expansion.
Added support for refering environment variables.
|
|
2.23
|
|
|
|
|
|
19.10.2007
|
Add advanced option "sendclear" to watchers. If set it will send a clear alarm if the current watcher is as expected and the watcher has a suppresion key set. Note this requires that the suppression key is unique enough that it will not clear an alarm unexpectedly. Using a variable that is unique for each alarm situation in the suppresion key is advised.
|
|
2.19
|
|
|
|
|
|
20.09.2007
|
Apply changes to log level and log size after restart of the probe.
GUI: When copying a profile the excludes are also copied.
|
|
2.18
|
|
|
|
|
|
03.08.2007
|
Store last run for profiles in logmon.dta so expansion of LASTRUN() is correct even after a restart.
Fix problem with Format rules not triggering.
Fix problem reading directories with / as path separator on windows systems.
Fix problem with abort on match flag. Fix problem with date expansion in filenames/commands.
GUI fix when trying to view contents of a web page
|
|
2.17
|
|
|
|
|
|
25.05.2007
|
Library change (and platform list corrected)
|
|
2.14
|
|
|
|
|
|
09.02.2007
|
Fixed problem where alarm flag would be reset to 'yes' on every restart.
Fixed potential hang situation where a thread would fail to release a lock.
Added support for URL authenticaton when windows authentication is used with a proxy configuration.
Probe has been re-written as a multi-threaded daemon.
Profiles are checked in a thread, allowing for higher throughput and configurable intervals for each profile.
A new mode 'url' is available, which fetches a web page through the url_response probe and performs checks on the page.
Variables in a watcher can be read from positions in the regular expression in addition to the fixed character or column specifications used prior to this release.
Variables can have a threshold set, where an alarm is sent only if the variable is outside the expected value.
Variables can generate Quality of Service (QoS) messages, either with their values (if numerical) or with the result of the check against an expected value (both numerical and strings).
A watcher is no longer bound to sending either Alarm, QoS or user defined messages. One or more types of message can be selected for each watcher.
Added ability to run a command when a watcher matches.
|
|
2.02
|
|
|
|
|
|
05.12.2006
|
Fixed problem with using time formatting together with wildcards in filenames.
Extended timeout for getting 'queue' data.
Fixed crash caused by long log messages. Now long log messages will be cut after 1024 characters.
The introduction of wildcards caused the two modes of 'queue' and 'command' to not function any longer. The wildcard check is now only performed if the mode is set to scanning files, and for the modes of 'queue' and 'command' it is working as before wildcards was introduced. 'command' was also not showing up in dropdown list. This is fixed.
|
|
1.67
|
|
|
|
|
|
22.09.2006
|
Added possibility to send number of matches per run as QoS.
Fixed core dump on True64 (long regexp).
Fixed GUI problem when minimizing/restoring window.
Fixed spelling error in GUI.
Changed name of ‘Checkpoint ID’ field to ‘Suppression key’.
Fixed missing subsystem ID when copying profiles.
Stripped off unnecessary text in $PROFILE variable.
Fixed problem with blank fields and tabs.
Added possibility of using wildcards in filenames.
Fixed blank variable problem.
Fixed problem with long matching lines.
|
|
1.63
|
|
|
|
|
|
06.06.2005
|
Added FILENAME message variable.
Resolved problems with large amounts of new log-data arriving while scanning for updates on a log file.
|
|
1.61
|
|
|
|
|