Options Dialog


You can define all HostMonitor's settings in the Options dialog window. Customize the color palette for windows, colors for HTML logs & reports, mailer parameters, proxy settings, log file formats, options for utilities, etc. Options are categorized on different pages and navigation is made through a convenient tree structure. Some parameters can be defined from the command line.

network monitor: options


Interface
Grouped on the Interface page are the general look and feel options that apply to the program, its main window and built-in utilities.

Style
Define how tests are displayed in the Test Detail Area:
  • Report - table view, one test per line as a small icon followed by detailed test information
  • List - top-down view, a small icon with a test name;
  • Icon - tests arranged left to right, a large icon with a test name;
  • Small icon - tests arranged left to right, a small icon with a test name;

    Color scheme
    Chose a color scheme to be used for the main window, log viewer and utilities. Select one of the pre-defined or create a new scheme by pressing the button to the right of the Scheme Name box.
    See Color profiles for more information on colors.

    Show grid lines
    If the option is enabled, HostMonitor will display gridlines to separate task items in the main window.

    Show tests in subfolders (recursive)
    If the option is disabled, displayed in the Test Detail Area will be tests contained directly in the currently selected folder. If the option is enabled, all tests contained in the current folder and in all of its descending subfolders will appear in the Test Detail Area.
     

  • Columns

    Use the Columns page to select columns (test parameters) to display in the Test Detail Area. To select/deselect a column, toggle the check mark next to it. To change a column's display order, highlight the column and then use the Up and Down arrow buttons to the right of the list of columns to display.

    The Sort by list defines the order in which tests will be arranged. To add a column to the sort order, highlight a column in the left-hand list and then click the Right arrow button. The column will show up in the Sort by list. To remove a column from the search order, select a column in the Sort by list and then click the Left arrow button.

    To change the display name of a column, highlight the column and click the little button to the right of the list box.

    Here is a list of test parameters supported by HostMonitor with a brief description of each parameter.
    Column name   Field description
    Test name The name of the test
    Test method The type of the test
    Test by Name of the remote agent that performs the test. Field displays "HostMonitor" when the test is performed by HostMonitor
    Comment Any arbitrary comments
    Related URL Test-related URL
    Master test The name of the Master test (for more information on test dependencies see Common test properties)
    Interval The time between two consecutive runs defined for the test
    Schedule The name of the associated schedule
    Alert profile Alert profile name
    Private log The specified private log file name
    Created at The time when the test was created
    Modified at The time when the test was last modified
     
    Status The current status of the test
    Recurrences The number of consecutive tests resulting in the same status as the current one
    Reply The value last returned by the test (the meaning of the Reply parameter is test specific)
    Last test time The time when the test was last performed
    Last status The status of the previous test
    Last reply The value returned by the previous test (test-specific)
    Acknowledged at The date and time when test status was acknowledged
    Acknowledged by   Name of the operator who have acknowledged the test status
    ACK comment Shows the comment which was provided for "acknowledge" operation

    In addition to the static test parameters (test name, interval, status, etc.), and current status related (status, reply, etc.) a number of dynamic statistics data fields are maintained and can be viewed (and reset) in real time.
    Column name   Field description
    Alive % "Good" to overall tests ratio, in percent
    Dead % "Bad" to overall tests ratio, in percent
    Unknown % "Unknown" to overall tests ratio, in percent
    Total time The time the test has been in monitoring
    Alive time The overall time the test has had a "Good" status
    Dead time The overall time the test has had a "Bad" status
    Unknown time The overall time the test has had an "Unknown" status
    Total tests Overall tests performed
    Passed tests The number of "Good" tests
    Failed tests The number of "Bad" tests
    Unknown result tests The number of "Unknown" tests
    Average reply The average value of the results obtained
    Min reply The minimum value of the results obtained
    Max reply The maximum value of the results obtained
    Status changed at The time when the status last changed
    Status changes count The number of times the status has changed
     

    Preferences
    On this page define the following options:

    Font options:
    • Windows Font
      Choose the font/size for the main window, log viewer and the utilities.

    • Terminal window font
      Choose the font/size for the Telnet utility.
    Tray icon options:
    • Icon in system Tray
      Hide to tray HostMonitor when it is minimized.

    • Animate tray icon when working
      The program can animate the tray icon when it is in working mode.

    • Change icon when a host dies
      HostMonitor will change icon from blue to red when any host changes status to "bad", or change color to yellow if a test goes to "Unknown" status.

    • HostMonitor always Top
      HostMonitor will remain in front of all other windows (unless minimized).
    Autosave options:
    • Do not save test list automatically. If this option is selected, HostMonitor does not save test list modifications automatically. Saving changes is up to the user (use the "Save" or "Save as" menu items in the File menu). If changes have been made, the program will remind you to save them before exiting, loading another TestList, etc.
      BTW: HostMonitor will save modification automatically if Windows is shutting down

    • Save tests and stats at midnight. With this option selected HostMonitor will save test settings (if test list was modified) and statistical information (Alive%, Dead%, Total time and other counters) every midnight. Of course you may save modifications and statistics manually using menu File -> Save

    • Auto save TestList after any changes. If this option is selected, HostMonitor will automatically save changes every time you add or import new test items, remove a test, modify, enable or disable items, etc. Also HostMonitor will save test statistics every 30 minutes (HostMonitor does not save statistical information constantly for better performance).

    Auto save windows options
    When this options is enabled the program will save and restore window parameters (column widths, the size of the panels, etc).

    Keep a list of N recent addresses
    Instructs HostMonitor to keep a history of recently used addresses.


    Store statistics in HML file
    This option tells HostMonitor to write all statistical information into a file, so that the statistics build up across multiple program sessions. If the option is turned off, when an HML file closes down, the statistics pertaining to its tests get reset. Please note that statistics for any or all of the tests can be nullified at any time using the "Reset ..." menu command.

    Store "Recurrences" in HML file
    This is an important option, because it is the "Recurrences" field that the program looks at to determine what actions and when to fire off. Therefore, if the option is deselected, upon closing an HML file or shutting down HostMonitor, the counter will be reset, so that when the program is restarted, actions will be triggered as tests are first performed. With the option turned on, recurrence counters will be saved on shutdown, and at the next startup the program will pick up where it left off, as if the program execution was not interrupted.

    Remember current folder
    If this option is turned on, HostMonitor will remember current folder and display it on the next load of the file with tests.
     

    IP-Monitor
    Options for the IP-Monitor utility: refresh time, chart colors, number of grid lines.
     
    Message window settings

    HostMonitor can display a popup window when a test changes its status (as long as you specify the "Show message" option in the alert profile for the test). On this page of the Options dialog window you can define the parameters for this popup window.

    Position
    You can choose "Predefined position" option and define the coordinates for the top left corner of the window. Or choose "Show in the last remembered position" option and HostMonitor will remember the window position on the screen and will display the popup window in the same location.

    Time live

  • "Close after N sec" - Select this option and specify the amount of time a window will stay open before automatically closing, unless the [Close] button is selected or the [Stop] button is used to stop the countdown.
  • "Close manually" - Window will stay open on screen until the [Close] button is used. Stay on top" style
    Popup window will appear in front of all other windows
     
  • Behavior
    On this page define the following options :

    Recheck dependant test items when master test status has been changed
    This option tells HostMonitor to recheck all dependant test items immediately after their master test failure or recovery (otherwise tests will be executed on regular schedule). This helps to maintain more accurate statistic information. Note: option does not have effect for tests that depend on logical expression.

    Consider status of the master test obsolete after N seconds
    This parameter is used by the program to determine whether the Master test status is up-to-date. Before starting a dependent test HostMonitor checks the status values of the Master tests defined on it. If Master test was performed more than N seconds ago, HostMonitor will recheck the Master test item before checking dependant items.
    Please note: HostMonitor makes an exception for SNMP Trap test methods. If such test is used as Master test, its status never considered as obsolete. In other words status of Master SNMP Trap test will always be considered as up-to-date, regardless of the time when last trap message was received.

    Don't start more than [N] tests per second
    HostMonitor is multi-threaded so it can test many hosts simultaneously. This parameter defines how many tests per second the program will start.

    Reset "Recurrences" and refresh test status after editing test properties?
    This option will determine the behavior of the program when the user changes the test parameters (using Test Properties dialog). You can choose one of the 3 options:
  • Always reset "Recurrences" - after modifying test, program will work as the test was just created, the program will perform test and starts alert actions if needed
  • Ask confirmation - the program will ask user about action
  • Don't reset - the program will not reset any counters

    Reset "Recurrences" when test gets disabled
    With this option enabled HostMonitor will reset "Recurrences" counter for a test every time when this test become disabled. "Recurrences" field determines what actions and when to fire off. It means that with this option enabled when test will be disabled and enabled again, actions will be triggered as tests are first performed.

    Request for comment when test gets disabled
    With this option enabled HostMonitor will request comment every time operator disables test item(s). However operator may continue operation without entering any information (keep comment field empty).

  • Startup
    On this page you can define different options to determine HostMonitor's behavior at startup.

    File load mode
    This parameter set HML file (file with list of tests) that HostMonitor should use for monitoring
  • empty list after load - do not load an HML file
  • load file [xxx] - load specified file
  • restore last status - reload last used file Start/Stop mode
    Define if program should starts monitoring upon loading or not. There are 3 options:
  • start after loading
  • stop after loading
  • restore last status Window status
    Choose state of HostMonitor's main window:
  • minimize after loading - minimize main window after startup.
  • maximize after loadng - maximize main window after startup.
  • normal size - display window in it's normal size after startup.
  • restore last status - restore window's position, size and state that were set at the last closing of the program Error handler
    This parameter defines program's behavior in case error occurs at startup. Choose 1 of 3 options:
  • Normal start - show error message (if one occurs) and continue after user confirmation.
  • Ignore errors during starting - don't stop and display message.
  • Quit if an error occurs - HostMonitor displays message, waits 20 seconds and quits if the user does not press any key to continue.

    Place program in Startup menu
    Mark this option to add HostMonitor into Startup group. Windows 9x/ME automatically starts programs listed in the startup group upon loading, Windows NT/2000/XP starts these programs upon user logon. Also on Windows 2000/XP you can install HostMonitor as a service, please refer to "How to install HostMonitor as Win32 Interactive service" section for more information.

    Also you can specify these parameters using command line. See "Command line parameters" section.
     

  • Service

    HostMonitor uses settings located on this page only when starts as Win32 interactive service (how to install HostMonitor as a service you can read here).

    Log on as
    Specify user account (login and password) to impersonate the security context of the user.
    When HostMonitor starts as a service, it uses the system account (as all interactive services). But this account may not have all the necessary permissions, so some tests will not work correctly (UNC test, "disk free space" test for shared drives, "CPU Usage" test for remote machines, etc). If you need these tests, you will need to assign a special user account. In this case HostMonitor will impersonate the security context of the user.
    Note: Do not change the account using the system utility "Services". If you do so, HostMonitor will not be able to interact with the desktop.

    Startup delay
    In some cases, initialization of dependent applications and services on the HostMonitor machine may consume a substantial amount of time. If HostMonitor's tests depend on these applications, false alerts may be generated while they are initialized.
    This setting will cause HostMonitor to wait at least (n) minutes before executing the first monitoring cycle thus allowing applications and services to start and initialize properly. A setting of "1" (one minute) should be adequate for most systems.

    When service is being stopped
    Define HostMonitor's behavior when service is being stopped, choose 1 of 2 options:

  • save changes in HML file
  • discard all changes
     
  • Access method

    On this page define the method to access the net to retrieve URLs.

    Type of access to retrieve pages:

  • USE REGISTRY CONFIGURATION
    Retrieves the proxy or direct configuration from the registry.
  • DIRECT TO NET
    Resolves all host names locally.
  • VIA NAMED PROXY
    Passes requests to the proxy unless a proxy bypass list is supplied and the name to be resolved bypasses the proxy.
  • PRECONFIG, PREVENT USING JAVA/SCRIPT/INS
    Retrieves the proxy or direct configuration from the registry and prevents the use of a startup JScript or Internet Setup (INS) file.
     
  • Proxy
    Define the following settings if the access method is set to "VIA NAMED PROXY"

    Proxy server - address of your proxy server
    Proxy port - port number of the proxy server
    Use proxy authentication - if your proxy server require authentication you may specify the username and password in these fields.

    Proxy bypass list - list of addresses that don't need to be accessed through your proxy server. This list may include IP addresses, host names, or names of computers from your intranet. Also, wildcards may be used as well to match domains, host names or addresses. For example: www.*.com; 128.*; *man*; and so on. For local addresses use the "<local>" macro. Use semicolons ";" to separate entries.
     

    Log settings: Primary log / Backup log


    network monitor: options

    You may specify Primay and Backup common logs, so there are 2 identical sets of parameters located on 2 pages in the Options dialog:
    - [Primary log]
    - [Backup log]
    For each log you may choose defferent log type (ODBC or File), file format (HTML, Text or DBF) and logging mode (Full, Brief, Midnight or Reply). E.g. you may use Full logging mode for primary ODBC log managed by your SQL server and use Brief logging mode for backup HTML log stored on local hard drive.
    HostMonitor can switch from primary to backup log when necessary or use both logs at the same time. Also HostMonitor may execute specified alert profiles when primary or backup logs are not accessible.

    First you should decide what type of the log do you need: File or ODBC and choose logging mode that will be used for all test items.

    Log type

    • None
      Choose this option if you are really sure you don’t need a log
    • File
      Record test results into a file stored on local hard driver is a fast and most reliable solution. HostMonitor supports three different data formats: plain text, HTML and DBF.
    • ODBC
      Starting with version 3.0, HostMonitor can write log information into database using any ODBC driver installed on your system (e.g Oracle, MS SQL or MySQL database). It’s a very flexible solution - you may define table structure and choose type of the fields to fit your needs. However you must be sure that ODBC driver (provided by 3rd party) works reliable and will not cause HostMonitor to crash.
      E.g. Microsoft dBase Driver v 4.00 causes resource leakage; Oracle driver v8 may crash application.

    Default logging mode
    This option tells HostMonitor when information should be written. Choose one of the following options:

    • Full: Save information about every performed test
      The "Save information about every performed test" option tells HostMonitor to add a record every time a test is performed.
    • Brief: Write a record when test status changes
      With this option selected no logging happens as consecutive tests return same status value, until the status changes, at which point a new log record is added.
    • Midnight: Write a record when test status changes + midnight logging
      With this option selected HostMonitor records information about current status of all test items at midnight (every night), then no logging happens as consecutive test probes return same status value, until the status changes, at which point a new log record is added.
    • Reply: Write a record when test status or reply value changes
    While the second option (Brief) is obviously most space-efficient, the first one (Full) allows you to build up statistics on helpful test parameters like response time, reply value, etc. This statistical information can be then parsed and visualized by the Log Analyzer.
    3rd option is useful if you are using Log Analyzer to generate reports for different time intervals but you do not want to keep large log files.

    Please note: you may change logging mode for particular test items in the Test Properties dialog by choosing one of the options:
  • Default - the common settings defined in the Options dialog are used;
  • Brief - record information whenever status of the test changes;
  • Full - record all test results, regardless of whether their status had changed or not;
  • Reply - record information into log every time the status or reply value of the test changes.



  • File log
    If you have chosen "File" as type of the log, then you should define location and name of the common log file. Select one of the following options:
  • Log to specific file
  • Automatically change the log every month (MMYYYY-Log.ext)
  • Automatically change the log every week (WWYYYY-Log.ext)
  • Automatically change the log every day (DDMMYYYY-Log.ext)

  • If you select option to automatically change the log file date macro variables may be specified in the log file name. HostMonitor interprets text between the '%' of the log name as a macro, where 'DD' represents the day of the month, ‘WW' - current week number, 'MM' - the month, 'YY' - the year in two digit format, 'YYYY' - the year.

    Log format
    Choose format of the log file:

  • HTML file
  • Text file
  • DBF file
    “File” logs support three different data formats: plain text, HTML and DBF. Each file format has its own strengths and weaknesses.

    Plain text:
  • Text log is the most compact of the three formats (about 80 bytes per record)
  • All fields in a text log are delimited with Tab (09), so you can easiliy import the data from a text log into a spreadsheet or a database

    HTML:
  • HTML logs are more visual;
  • HTML logs can be made automatically available over the Web;
  • on the flip side, HTML logs take up a lot more disk space (about 800 bytes per record) than text or DBF logs.

    DBF:
  • DBF logs are relatively compact (173 bytes per record).
  • DBF log data is easy to analyze and manipulate, or import into another DBMS

    Please note: The date and time formats used internally in DBF files do not depend on the system's regional setings. Therefore, changing the system date/time formats has no effect on Log Analyzer's ability to interpret those log elements, which is not the case with the text format. If you choose to keep your log in a text file, and then change the system date/time format, Log Analyzer may have difficulties calculating test parameters of the date/type type, like the alive/dead time. To avoid this problem, turn on the "Use fixed date&time formats" option located on the Miscellaneous page in the Options dialog. In this case, HostMonitor will use the date&time formats specified, regardless of the system settings.


    ODBC log


    If you have chosen "ODBC" log type, then you should specify data source and SQL query for the logging.

    ODBC data source
    Choose one of ODBC data sources available on your system.
    Note #1: Windows provides system data source names and user data source names (System DSN and User DSN). User data sources are local to a user and accessible only by the specified user.
    If you start HostMonitor as service, it will not be able to use User DSN. So, if you are planning to start HostMonitor as service and as regular application, select "System DSN" option (that is located on Misc page in the Options dialog) and choose system ODBC data source for the logging. In this case HostMonitor will work equally in both modes.
    Note #2: you must be sure that ODBC driver (provided by 3rd party) works reliable and will not cause HostMonitor to crash. E.g. Microsoft dBase Driver v 4.00 causes resource leakage; Oracle driver v8 may crash application.

    Login
    Specify user identifier, if necessary

    Password
    Specify password, if necessary

    Timeout
    Specify the number of seconds to wait for a login request to complete. If value is 0, the timeout is disabled and a connection attempt will wait indefinitely.

    SQL Query
    Here you should specify SQL query to logging test data. Format of the query is up to you; you may use the macro variables to put in as much detail as you want. For instance, SQL command might look like this:
    INSERT INTO HMLOG (EVENTTIME, TESTNAME, STATUS, REPLY, TESTID, TESTMETHOD, RECURRENCES) VALUES (‘%DateTime%', '%TestName%', '%Status%', ‘%Reply%', %TestID%, ‘%TestMethod%’, %Recurrences%)
    Of course an appropriate database table has to be created before you start using the ODBC logging.
    Note #1: Maximum length of the query: 4096 symbols.

    However some parameters are obligatory, especially when you plan to use Log Analyzer. Database logging table should store the following information:
    Macro variableField typeAlternative variableAlternative typeMeaning
    %DateTime% datetime or timestamp   time of the event
    %TestName% char or varchar   name of the test item
    %TestID% int   unique test ID*
    %TestMethod% char or varchar  test method**
    %Status% char(16) or varchar %StatusID% int or tinyint status of the test
    %Reply% char or varchar %Reply_CStyle%
    %Reply_Number%
    %Reply_Integer%
    char or varchar
    decimal or float
    int
    reply value***
    * ID is unique within test list (HML file). If you are running several instances of HostMonitor, test item from listA may have the same TestID as different item from listB. In such case you may use separate tables for each instance of HostMonitor or add additional field and use %HM_FILEGUID% variable.
    ** If you are using descriptive names for your test items, you may skip this field. However its better to use TestMethod field, unless you need to keep your database as compact as possible.
    *** If you don’t need very accurate statistics for Traffic Monitor and/or Performance Counter test items, you may use %Reply_Integer% variable and int data type.

    Note #3: If you are using Log Analyzer and you have chosen "ODBC" as primary log, you should describe database parameters using "ODBC logs Manager" dialog (that is available thru Log Analyzer menu File -> Setup ODBC logs) and mark "Use this source as default" option. This allows you to use ODBC logs for "Statistics" feature (HostMonitor: menu Test -> Show statistics).


    Alerts


    Execute alert profile when log inaccessible
    If you mark this option and choose alert profile, HostMonitor will execute specified actions when it’s impossible to record data into the log (e.g. disk is full or SQL server does not respond).

    Execute alert profile when log comes to life
    This option tells HostMonitor to execute specified actions when log becomes acessible (e.g. link to SQL server has been restored).
     
  • System log


    HostMonitor uses the system log to record events like start/stop monitoring, as well as information on started and/or failed alert actions. You can either specify a particular file name for the log, or use date macro variables to have HostMonitor switch to a different file every day, week, month or year.

    There are two more options available:

  • Record info about successful actions
  • Record info about failed actions
    You can select one, both, or non of these options.

    To get more information about different logging options available in HostMonitor, please, refer to "Log & Reports" section.
     
  • Log processing


    HostMonitor can switch from primary to backup log when necessary or use both logs at the same time. Choose one of the following options:

    • Use backup log when primary is not accessible
      If both logs are specified, HostMonitor uses primary log until 1st failure. When logging operation fails, HostMonitor switches to backup log right away. However it will try to use primary log for the following test probes and switch back to primary log in case of success. If logging operation fails 8 times in a row, HostMonitor will not check primary log for the next 5 min.
    • Use primary and backup logs all the time
      This option tells HostMonitor to use both logs at the same time. It has sense when you are using different logging options for primary and backup log. E.g. you may use Full logging mode for primary ODBC log managed by your SQL server and use Brief logging mode for backup HTML log stored on local hard drive.

    Special file processing

    The following options allow you to manage log files: e.g. you may set HostMonitor to remove files older than 3 months, or you may configure HostMonitor to keep just 2 log files - for previous and current month.

    There are 2 similar sets of options: one for common log files, another - for private log files.

    You may define command line for execution and choose one of 3 available options to specify when HostMonitor should execute external command for processing common log file(s):

    • If common log(s) was created <N> days/weeks/months/years ago
      with this option selected HostMonitor will apply specified external command for each log file that was created specified number of days/weeks/months or years ago. HostMonitor checks age of log files once a day (normally at midnight).
    • If common log(s) is bigger than <N> KB
      with this option selected HostMonitor will apply specified external command for current log file only when its size reaches specified limit. ("current" means this option does not affect old log files into which no records are added anymore).
    • If common log(s) is switching
      with this option selected HostMonitor will apply specified external command for current log file when HostMonitor switches to another (new) log. E.g. if you use "Automatically change the log every month" option, HostMonitor will execute specified command before creating new log at midnight every 1st day of every month.
    Please read notes below. Some important restrictions apply to external programs:

    You may choose one of 2 options to specify when HostMonitor should execute external command for processing private log file(s). They could be same as for common log (above) or different:
    • If private log(s) was created <N> days/weeks/months/years ago
      with this option selected HostMonitor will apply specified external command for each log file that was created specified number of days/weeks/months or years ago. HostMonitor checks age of log files once a day (normally at midnight).
    • If private log(s) is bigger than <N> KB
      with this option selected HostMonitor will apply specified external command for current log file only when its size reaches specified limit. ("current" means this option does not affect old log files into which no records are added anymore).
    Please read notes below. Some important restrictions apply to external programs:

    Execute command:
    You may specify 2 commands for execution: one for common log files, another for private logs. You may use special variables in the command line:
      %log%  - represents full name (including path) of the log file (e.g. C:\Program Files\HostMonitor\Logs\04-2004.htm)
      %logpath%  - represents path to the log file (including trailing back slash. E.g. C:\Program Files\HostMonitor\Logs\)
      %logname%  - represents name of the log file (e.g. 04-2002.htm)
      %logext%  - represents extension of the log file (e.g. ".htm")
    (!) Please note:
    When you design external command/application for log processing you should consider following: external application MUST NOT lock CURRENT log file for more than 60 seconds. If it does, HostMonitor will terminate external application to unlock the log.
    So, if you want to perform some operation that can take more than 60 sec (e.g. pack log file or move it to slow backup device), move it to another folder or rename log file first and then start slow process. See example #4
    On the other hand, this limitation is not applicable for processes that work with old log files. If you change log file dynamically and want to pack old log files, you may do this without any restrictions. See example #2 and #3

    Examples:

    1. If you want to keep 2 log files at any moment: one log for current month and another for previous month, you may use following settings:
      • If common log(s) was created 1 month ago execute command cmd /c   move /y   "%log%"   "%logpath%oldlog%logext%"
      • Name of the log file could be static, you don't need to use "Automatically change the log every month" option (but you may use this option if you want)

      Please note: 1 month ago doesn't mean exactly 1 month (30 or 31 days) ago. It means "previous" month. E.g. if log file was created in October (any day of the October), HostMonitor will execute specified command on November 1st.

    2. If you want to keep log files for last 3 months, you may use following settings:
      • If common log(s) was created 3 months ago execute command cmd /c del "%log%"
      • Name of the log file should be dynamic. Use Automatically change the log every month (week or day) option

    3. if you want to zip old log files once a year,
      • use "Automatically change the log every month (week or day)" option
      • set If common log(s) was created 1 year ago execute command pkzip c:\logs\archive.zip "%log%" option
      Here you may start archive program to pack log file. It will lock the file but it's not a problem in this case - HostMonitor switches to a new log (because of ""Automatically change the log…" option)

    4. If you want to zip current log file when it reaches 1,000,000 Kb simultaneously starting new log, this is more complicated because archiver is not allowed to lock log file for more that 1 minute. One of possible solutions:
      • you may create simple BAT file with the following commands
        cd %~p1
        mkdir tmp
        move /y %1 tmp\%~n1%~x1
        pkzip c:\logs\archive.zip tmp\%~n1%~x1
        Comments:
        3rd command moves log file, it allows HostMonitor to create new log. If you move file within the same drive, Windows moves it fast;
        4th command starts archiver that may pack new (moved) file as long as it needs, HostMonitor will work with another file
      • use If common log(s) is bigger than 1000000 Kb execute command cmd /c NameOfTheBATfile.BAT %log% option to start that BAT file
    HTML Colors
    Customize color scheme for HTML log files. You can use Color Profiles dialog to select scheme or create new one (use button to the right of the Scheme Name box to bring up Color Profiles dialog).
     
    Log Viewers
    For each type of log file (HTML, Text, DBF) select one of the options:
  • Internal - use the build-in viewer
  • Associate program - use the default Windows viewer for file
  • External - use an external viewer. Define a command line to start the program that will be used as the viewer. The name of the log file to view can be passed to this program as a parameter using macro variable %LOG%. E.g. "notepad.exe %Log%"
     
  • Reports

    HostMonitor can generate HTML, DBF, WLM, and Text reports with the information about tested hosts (e.g. for publishing on your WEB or WAP site, for sending with E-Mail notification, or for analyzing). On this page you can define a list of up to 6 global reports (reports that apply to all tests in the working HML file). Just select report profile from drop-down list and specify name of a target file (you can use a naming pattern to have HostMonitor switch to a different file every day, month, year, etc., as prescribed by the date macro variables appearing in the pattern).
    Also you can bring up Report Manager dialog to configure an existing report or create a new one.

    There are two more parameters that can be specified on this page:
    Generate reports every N min
    Tells HostMonitor how often reports should be generated
    Execute action profile when complete
    With this option enabled HostMonitor will launch the specified alert profile after reports were generated (for example you may use this option to send reports by e-mail). Note: only "scheduled" actions will be executed, i.e. a condition to start action should be set to "on the schedule" (in Action Properties dialog).

    Use "Generate reports now" button to immediately create reports (for testing purposes).

  • Note #1: Additionally, each folder may have its own report list; only the tests contained in the folder will be used to generate these folder-specific reports. For more information about folder, please, refer to "Folders" section of this documentation.
  • Note #2: To exclude some tests from reports use test property "Exclude from reports".
  • Note #3: If you need to create reports every time a test changes its status add the "Generate reports" action to the Actions Profile. The other way to implement the same behavior would be to add a "Run HMS Script" action, and include a CreateReport command in the script to execute.
  • Note #4: Also reports can be generated at user request at any time through the Reports menu in HostMonitor's main window.
     
  • Mailer

    On this page define the settings for the build-in mail client.

    network monitoring: options dialog

    Primary SMTP Server

    Address
    IP address or hostname of your SMTP server.
    Port
    TCP port number of the mail server (normally all SMTP servers use port #25).
    Authentication method
    Select one of authentication methods: None, Plain, Login, Cram-MD5, or POP before SMTP
    Login
    Specify login (if authentication method is not None)
    Password
    Define password (if authentication method is not None)

    The same parameters you can define for the Backup SMTP server. When HostMonitor tries to send e-mail, at first it uses Primary SMTP server. If in consequence of some error this is impossible, HostMonitor tries to send e-mail using Backup SMTP server.

    Show status window when sending mail
    With this option enabled, HostMonitor will display a window when sending e-mail and show all requests to and answers from the mail server.

    Close on disconnect, delay closing for [N] sec
    If you enable this option, HostMonitor will close the window after a specified time interval after disconnection. Or, press the [Close] button to close the window immediately or the [Stop] button to continue displaying the window on the screen.

    Show in the last stored position
    The status window will save its coordinates and restore back to those coordinates when displayed again.
     

    Pagers

    Use this page to setup general settings for the subsystem which sends messages to pagers and beepers. Information related to specific pagers may be defined in each action profile.

    Device
    Specifies your TAPI device (modem) which will be used by the program. Select a modem from the drop-down list or select the "Auto select free TAPI device item.". In this case HostMonitor will search through all the compatible devices on the system and attempt to send the message. If one port is busy, it will try the next port until it has exhausted all the compatible TAPI ports.

    Baud rate
    Specifies the baud rate that will be used to communicate with your modem. This can be any of the following: "300", "1200", "2400", "4800", "9600", "19200".

    Modem init string
    This is the initialization string for your modem. The modem must then respond with an "OK". You can leave the default value as "AUTO" in this parameter. HostMonitor will search your Modem's INF file from Windows and prepare a string that will work with most paging carriers. If the default string does not work, you will need to search the modem's manual and figure a string that will work. Any time you need to replace the string use the tilde character (~) (i.e. AT&F~). If you need to pause, the hat character (^) will give you a one second pause. (i.e. AT&F~^^AT~). The maximum length of the modem initialization string is 80 characters.
    Specify a termination string by placing a vertical bar (|) after the modem init string. By specifying AUTO, it will use the strings specified in the modems INF settings. Examples: (AT~|ATZ~) (AUTO|AUTO)

    Modem dial string
    This is the string the program will send to the modem when it is ready to dial. The default value is "ATDT". If only a pulse dialtone is available, "ATDP" must be passed to this parameter. To control how long HostMonitor will wait for a connection before giving up, pass "TO=20" where 20 is the number of seconds desired. For example, the string to use here is: "TO=20,ATDT".

    Show status window when dialing
    HostMonitor can display a window when sending messages to a pager, displaying how it sends the message and the results of the operation (also, the program writes the result of sending the message into a log file).

    Close window on disconnect, delay before close [NN] sec
    After a specified time interval, HostMonitor will close the message window after sending the current message. Press the [Close] button to close the window immediately or the [Stop] button to keep the window onscreen indefinitely.

    If device(s) busy wait up to [xx] min
    Specify how long the program will attempt to resend messages.
     

    ICQ

    If you want to use “Send message to ICQ” action method, specify parameters of your primary and backup (optional) ICQ accounts here. For each account you should provide UIN and password.

    Why do you need backup account?
    HostMonitor utilizes message queue, uses deferred logout algorithm and some other tricks to make message delivery as reliable as possible. However ICQ servers use anti-spam technologies and may temporarily lock your account or do not accept messages for a while. When this happens HostMonitor switches to backup account.
    If you do not specify backup account, HostMonitor will utilize flow control options provided by ICQ protocol.
    Please note: we do not consider "Send message to ICQ" action as reliable way to notify network administrators about critical network problems.
     

    Jabber

    If you want to use "Send message to Jabber" action method, specify parameters of your primary and backup (optional) Jabber accounts here. For each account you should provide the following parameters:

    • JID (Jabber ID)
    • Password
    • Login server (host name or IP address of the server)
    • Port (TCP port used by the server. Normally Jabber server listens on port 5222)
     
    SMS: GSM

    If you have GSM modem (cell phone) connected to the system where HostMonitor is running and you want to use "Send SMS" action to send SMS messages to your support staff or some devices, specify parameters of your primary and optional backup GSM modems here.
    If you have 2 modems connected to the system and HostMonitor cannot send SMS through the primary modem, it will try to send messages using backup cell phone.

    For each GSM modem you should specify the following parameters:

    COM port
    Specify COM port to which GSM modem is connected.

    Baud rate
    Specify the baud rate that will be used to communicate with your modem.

    Modem type
    Choose type of the cell phone that you have connected to the system. HostMonitor supports the following devices:

    • Siemens A1
    • Siemens M1
    • Siemens M20
    • Ericsson GM12
    • Nokia 6210
    • Nokia 6650
    • Nokia 9110
    • Siemens M35
    • Siemens S25
    • Motorola T260
    • WaveCom
    • Siemens TC35
    • Wavecom Fasttrack
    • Z-text Fixed Line SMS modem
    If you do not see your phone in the list, you may try to choose similar model. For example Seimens C45 and Siemens S45 both work like Siemens M35

    Mode
    Choose the type of SMS format that should be used by your GSM modem. When the modem supports both formats (Text and PDU), the PDU mode is recommended

    PIN
    Provide PIN of the SIM card installed in your modem (cell phone)

    Service center
    The SMS center number, e.g. +17044100000 (Sprint, USA), +17057969300 (Rogers, Canada) or +491710760000 (D1, Germany)


    Logging options
    SMS module has its own logging options. Why? HostMonitor puts messages into query and does not spend its resources to manage GSM modems. Separate module, called SMS spooler, manages messages and works with the modems.

    SMS log
    Choose one of the following logging options:

    • No log
    • Failed events only
    • Failed and successful events
    • Detailed tech info

    Log file
    Provide the path to the log file. If you use .HTM or .HTML extension for the file, SMS spooler will create log file in HTML format, otherwise TEXT format will be used


    Test
    “Test” button allows you to check your settings and modems right away.
    Please note:

    1. HostMonitor will not send testing SMS when SMS spooler is busy sending messages that were initiated by “Send SMS” alert actions.
    2. SMS Test window will display technical information about your testing SMS; then it may display information about SMS messages that were initiated by “Send SMS” action started at the test execution time (if any).

     
    SMS: SMPP

    In order to use "Send SMS (SMPP)" action you should specify parameters of your primary and optional backup SMPP accounts. If you provide 2 SMPP accounts and HostMonitor cannot send SMS through the primary account, it will try to send messages using backup account.

    For each account you should specify the following parameters:

    Host
    Provide host name or IP address of the Short Message Service Centre (SMSC).

    Port
    Provide the port that SMSC is listening on for connections from SMPP clients.

    System ID
    Provide the account that should be used to login to the SMSC.

    Password
    Provide the password that should be used to login to the SMSC.

    Source Address
    Specify source address

    Source TON
    Type of the Number (TON) used for "Source Address". Choose one of the following options:

    • Unknown
    • International
    • National
    • Network Specific
    • Subscriber Number
    • Alphanumeric
    • Abbreviated
    We recommend using "International" format of the adresses (number starts with the country code followed by the national destination code and the subscriber number, e.g. +17057969345).

    Source NPI
    Source Numbering Plan Indicator (NPI) - type of numbering scheme used in telecommunications. Choose one of the following options:
    • Unknown
    • ISDN (E163/E164)
    • Data (X.121)
    • Land Mobile (E.212)
    • National
    • Private
    • ERMES
    • Internet (IP)

    Please consult with your SMPP service provider for the list of supported options.
     
    Ping/Trace

    On this page specify parameters for the Trace utility and for Ping tests.

    Packets to Send
    Specify the number of ECHO packets.

    Packet Size
    Specify the size of ECHO packets.

    Timeout
    Specify a timeout interval in milliseconds.

    Time to Live
    Specify a TTL value. TTL (Time To Live) - a technique used in best-effort delivery systems to avoid endlessly looping packets. For example, each IP datagram is assigned an integer time to live when it is created. IP gateways decrement the time to live field when they process a datagram and discard the datagram if the time to live counter reaches zero.

    Number of Hops
    Specify the maximum number of hops to reach the target. This is a measure of the distance between two points on the Internet. A hop count of n means that n gateways separate the source and destination.

    Clean old info at start
    If selected, Trace utility will clear the output window before perform new test.

    Show Host's Description
    If option is enabled, the program will display a description of the host beside host name in the Trace utility. Example:
    ... www.chat.ru        (Russia)
    ... mainboss.xaxa.BD   (Bangladesh)
    ... www.gazprom.ru     (Join-stock company GAZPROM, Moscow, Russia)


    Stop tracing when a non-responding device is encountered
    By default Trace utility stop tracing when some device does not respond. When you disable this option HostMonitor will continue trace until reach destination host.
     

    RCI (Remote Control Interface)

    RCI is a feature of the monitor that allows you to check and control HostMonitor remotely (using web browser or telnet client). RCI uses TCP/IP protocol and needs just one TCP port. On this page you may setup different parameters of the interface:

    Enable Remote Control Interface
    HostMonitor will accept remote control requests and commands only when this option is enabled. This is the main "switch" of all remote control functions of HostMonitor.

    Listen for incoming connections on port
    Here you may specify the TCP port number which HostMonitor will use to listen for incoming requests and commands from Web Service or Telnet Service. Note that both Web Service and Telnet Service should be configured to use the same TCP port number as the HostMonitor itself.

    Timeout
    This is the maximum amount of user inactivity time which HostMonitor will hold an established connection with the remote user. If the remote user after establishing the connection with HostMonitor does nothing (i.e. does not sends any control commands) HostMonitor will drop this connection after the specified amount of time expires.

    Maximum simultaneous connections
    This option specifies the maximum number of simultaneous remote connections that HostMonitor may accept from the remote users.
    It is important to note here that even just one user that connects to HostMonitor via web browser may generate several simultaneous connections. When an internet browser acquires the document from the internet it may fetch several parts of the document at once to increase performance. Thus "Maximum simultaneous connections" option of the HostMonitor's RCI interface should be set to 8 (minimum) if you plan to use web browser to control HostMonitor (even if just one user at a time will be connected to HostMonitor). Otherwise the web browser may not be able to display a web page with an interface of the HostMonitor correctly.

    User profiles button
    This button brings up a User Profiles dialog. There you can specify (for each user account separately) a list of authorized IP addresses from which a connection to HostMonitor can be accepted and a list of authorized operations (such as start/stop of monitoring, enable/disable tests, etc) that are allowed for each user. Only "Admin" and users that already have permissions to modify accounts of other users may access the User Profile dialog.

    The following group of check boxes specifies the types of events (associated with Remote Control Interface) that HostMonitor will or will not add to system log:
    Record info about accepted connections
    You may enable or disable recording the information about successful connections from the remote users.
    Record info about rejected connections
    Disable or enable recording the information about rejected (by a HostMonitor) connections from the remote users.
    Record info about accepted/executed commands
    Disable or enable logging of accepted commands.
    Record info about rejected/failed commands
    Disable or enable logging of rejected commands.
     

    Actuve RMA Server

    Options located on this page allow you to specify TCP port that will be utilized by HostMonitor to listen for incoming connections from Active RMA agents.

    Also it allows you to setup filter for IP addresses

    • Accept connections from any IP address
      Enabling this option will allow HostMonitor to accept connections from any IP address (as long as the incoming RMA request provides correct name and password)
    • Accept connections from the following IP addresses
      This option allows you to specify the list of IP addresses. After enabling this option HostMonitor will accept remote connections only from the addresses within this list (password is required as always).
    Please note:
      - to insert new address press INSERT button; to remove item press CTRL+DEL; to edit item press Enter or double-click it
      - you may specify ranges of IP addresses from which a connection may be accepted. E.g. 192.168.1.1 - 192.168.1.100

    The following options specify the types of events that HostMonitor will or will not add to system log:
    Record info about accepted connections
    You may enable or disable recording the information about successful connections from Active RMA agents.
    Record info about rejected connections
    Disable or enable recording the information about rejected (by a HostMonitor) connections from the agents.
     
    Scheduler

    HostMonitors` built in scheduler. Here you may specify which action profiles HostMonitor will execute on schedule. You have five separate entries in the list. Each of the entries has the following schedule options:

    • "None" - no action (alert) will be performed.
    • "Regular" - specify the time interval (e.g. every 60 minutes) to perform action profile.
    • "Daily" - an action profile will be executed every day at a specified time of the day. Note: the time of the day is specified in 24h format.
    • "Weekly" - an action profile will be launched once a week on specified day of the week at a specified time of the day (e.g.: weekly, every Tuesday at 22:00).
    • "Monthly" - once a month, on a specified day of the month, at a specified time of that day (e.g.: every 5-th day of the month at 7:00). Use "Last day" option to start action profile on the last day of the month (you don't have to worry how many days it is in the current month).
    • "Quarterly" - an action profile is performed once in a quarter on a specified day of the FIRST month of each quarter (1,4,7,10 month) at the specified time. Please note: if you are using "Quarterly" schedule with "Last day" option, action will be performed on the last day of the LAST month of each quarter (3,6,9,12 month).

    You may set maximum five schedules of a/m types. In each schedule you may select an action profile that will be executed accordingly. Use the drop down list to select action profiles. By clicking the button next to a drop down list you will access the Action Profiles dialog window where you may add new action profiles and actions or edit the properties of existing actions.
    Note: only "scheduled" actions will be executed by Scheduler, i.e. a condition to start action should be set to "on the schedule" (in Action Properties dialog).
     

    Miscellaneous


    Use fixed date & time formats
    By default HostMonitor gets current Windows regional settings at startup and uses these parameters until you change Windows settings and restart monitor. You can mark this option and define date & time formats. In this case, HostMonitor will use the specified formats, regardless of the system settings.

    Reports & Statistics
    ODBC related options
    RMA / Logging
    Update check

    Settings for URL tests
    Settings for UNC tests
    NT Event Log test related option
    Performance Counter test related option
    Settings for SNMP Get tests
    Settings for SNMP Trap tests
    Settings for Traffic Monitor tests


    Reports & Statistics

    Reports:

    • Show folder names
      With this option enabled HostMonitor inserts into reports additional line with the name of folder preceding the list of tests in this folder. Compact HTML and Dashboard reports always display folder name, regardless of this option.
    • Skip empty folders
      With this option enabled folders that do not contain any tests will not be included into reports. Otherwise report will display single line (row or cell - it depends on report type) with the folder name.
    Statistics:
    • Display Alive/Dead ratio of passed/failed tests
    • Display Alive/Dead ratio of alive/dead time
      This switch defines how Alive/Dead/Unknown ratio should be calculated: it is either based on quantity of passed/failed probes (HostMonitor version 3 and 4 supported this mode only) or based on alive/dead time (new mode). New mode is useful when you setup HostMonitor to change test intervals for failed tests.
    • Precision: display [N] digit(s) after decimal
      Sets precision of the Alive%, Dead%, Unknown% fields

    ODBC related options (following options have effect for ODBC tests, ODBC logging, and "SQL Query" action)

    User DSN/System DSN
    As you know Windows has system data source names (System DSN) and user data source names (User DSN). System data sources are local to a computer but not user-dedicated; any user with privileges can access a system DSN. User data sources are local to a user and accessible only by the specified user. Using "User DSN/System DSN" option you can choose which data sources list will be used by HostMonitor.
    Please note if you start HostMonitor as service, it will not be able to use User DSN. Only System DSN will be used . So, if you are planning to start HostMonitor as service and as regular application, use "System DSN" option. In this case HostMonitor will work equally in both modes.

    Do not use SQLFetchAbsolute command
    Not every ODBC driver supports SQL_FETCH_ABSOLUTE command. HostMonitor tries to use this command and if driver returns error, HostMonitor use cycle with SQL_FETCH_NEXT command.
    It works fine with most ODBC drivers. However ODBC driver which comes with Oracle client v.8 (and may be some other drivers) has bug in error handler. This bug can cause ODBC driver to crash.
    That's why this option was implemented. Use it if you experience problem with ODBC driver.

    Enable connection pooling
    This option enables an ODBC driver to reuse a connection from a pool of connections. Once a connection has been created and placed in the pool, driver can reuse the same connection without performing the complete connection process. This can increase performance of HostMonitor.
    PS.: ODBC driver manager controls the number of connections in the pool, HostMonitor cannot change it.


    RMA / Logging

    If backup agent is specified and connection to primary RMA failed
    • Set "Unknown" status, log the error, then repeat test using backup agent
    • Request backup agent without reporting error
    If you setup primary and backup agents, HostMonitor will be able to balance load between agents and use the backup agent when primary one does not respond.
    This option defines behaviour of the tests in case primary agent does not respond.

    Log: record info about inactive statuses (Disabled, Wait for Master, Paused)
    Normally HostMonitor records information about every status change. If you disable this option, HostMonitor will not record information about “inactive” test statuses.


    Update check

    This option tells HostMonitor to check for software updates at http://www.ks-soft.net/ every 3rd night. If new version detected, HostMonitor will inform logged in operator (next morning). HostMonitor also checks your license and informs operator about validity of the registration code for this new version.

    Also you may use menu item "Help" -> "Update check" to check for software updates at any time convenient for you.


    URL test related options

    Do not check Internet connection
    Normally HostMonitor checks if computer connected to Internet before "URL request" test (to avoid appearance Dial-Up dialog). With this option enabled HostMonitor will not perform this check.

    Agent name
    Some server-based scripts can check agent name and returns different information for different HTTP agents (e.g. generate different HTML pages for IE or Netscape). You can change this parameter to get correct results.

    Accept SSL/PCT certificates with invalid host name
    Disables function checking of SSL/PCT-based certificates that are returned from the server against the host name given in the request.

    Accept SSL/PCT certificates with invalid dates
    Disables function checking of SSL/PCT-based certificates for proper validity dates.


    UNC test related options

    UNC test mode
    This parameter defines behavior of UNC tests. Select 1 of 3 options:

  • Normal - HostMonitor can start many tests simultaneously.
  • OnePerServer - HostMonitor will start only 1 test per server at one time, but can start several tests for different servers at the same time.
  • OneByOne - only 1 attempt at one time (one attempt means - if "UNC test retries" value greater than 1, HostMonitor tries to get information from 1st server; if this try failed, HostMonitor will pause test for this server and will try to check another servers, after 900ms HostMonitor returns to 1st server and performs 2nd attempt).

    UNC test retries
    Define how many times HostMonitor will try to get information from server (in one test)

    Show errors description in "Reply" field when cannot access resource
    If you check this option, HostMonitor will put error description in "Reply" field in case "UNC" test cannot access to resource.


    NT Event Log test related option

    Show events description in "Reply" field for "check NT Event Log" test
    HostMonitor can show events description in field "Reply". You can use %Reply% macro in e-mail body, in message for pager, etc. Also this description will appear in reports, log file.


    Performance Counter test related option

    Test mode
    Windows implementation of performance counters has bugs. E.g., Windows 2000 (Professional, Server, and Advanced Server editions) can produce memory leak in PDH.DLL when user (application) querying performance counter that does not exist. This bug fixed in SP2. Also PDH.DLL does not work correctly with multithread applications.
    That's why in HostMonitor we have implemented several different methods to work with pdh.dll:

    • MultiThread mode: HostMonitor works almost according to Microsoft documentation with some workaround to avoid most likely problems. HM loads pdh.dll at once and uses it all the time. This method fast because HM can start several tests simultaneously. If everything will work correctly on your system, use this method (by default HostMonitor uses this method).
    • OneByOne mode: Using this method HM will start Performance Counter tests one by one This method is slow (when you setup Performance Counter test using Test Properties dialog program even can hang for 1-2 min) but using this method you may avoid some problems due to a buggy pdh.dll
    • Smart mode: With this method HM will try to detect when pdh.dll has to be reloaded.
    • External mode: HostMonitor uses external (perfobj.exe) utility to perform the tests. This is fast and most reliable method.

    PerfObj utility is included into package. Remote Monitoring Agent (RMA) can use this utility as well (utility should be located in the same directory where RMA is installed).
    If you want to change test method used by the agent, add line "PerfWorkMode=N" into [Misc] section of the rma.ini file and restart agent. N is a code of the mode:
      0 - MultiThread mode;
      1 - OneByOne mode;
      2 - Smart mode;
      3 - External mode


    "SNMP Get" test related option

    Automatically append the single instance sub-identifier (".0").
    Since the "SNMP test" is typically applied to single instance MIB objects that HostMonitor automatically appends the single instance sub-identifier (".0"). Though this has an unfortunate side effect for table instance retrieval, to retrieve correct values for the table instances disable this option.


    "SNMP Trap" test related options

    Here you may specify general settings of the SNMP Trap test method and provide special processing instructions to warn you about high SNMP traffic from network devices.

    Receive traps on UDP port #
    This option specifies the UDP port number, which HostMonitor utilizes to listen for incoming messages. Default setting is 162.

    Unlike other test methods that are performed by specified time interval, SNMP Trap test method reacts on each incoming message from remote network devices. Thus HostMonitor cannot predict how many messages will be received and how often tests/actions will be performed, as a result HostMonitor cannot balance system load.
    To prevent overload of the system (which may delay execution of other tests) we have implemented several options:

    High traffic alert if more than NN incoming messages per NN sec
    This option allows performing special actions when HostMonitor receives more than specified number of messages within specified time. The purpose is to prevent system overload caused by improper configuration of some network device or hacker's attack.

    Following options define what HostMonitor should do when high traffic is detected:

    Suspend receiving messages for NN sec
    With this option enabled HostMonitor ignores all incoming SNMP messages for next NN seconds. It reduces system load and allows performing of other (non SNMP Trap) tests.

    Execute action profile
    Here you may select action profile that will be executed when high traffic detected. E.g. it can inform network administrator by e-mail or cell phone.
    Note: only "scheduled" actions will be executed, i.e. a condition to start action should be set to "on the schedule" (see Action Properties dialog).


    Traffic Monitor related options

    This parameter allows you to specify units that should be used to report amount of network traffic. Choose one of the following options:

  • Display traffic using KB / MB units
  • Display traffic using Kbit / Mbit units
  • Select units considering test settings (threshold value)


  •  
    Command line parameters
    You can start HostMonitor using command line parameters (these parameters have priority before settings defined in the Options dialog) such as:

    /Ini=IniFileName - Read options from specified ini file, by default from "hostmon.ini".
    /List=HostsFileName - After startup load specified TestList file (HML file with tests).
    /ErrorHandler=Default - Normal startup (show error message (if one occurs) and continue).
    /ErrorHandler=Ignore - Ignore all errors during startup (do not stop and display message).
    /ErrorHandler=Quit - Quit if error (HostMonitor will display the message, wait 20 seconds and quit if operator does not press a key on the keyboard).
    /start - Start monitoring after loading.
    /stop - Do not start monitoring after loading.
    /minimized - Minimize main window after startup.
    /maximized - Maximize main window after startup.
    /normal - Display window in it normal size after startup.
    /InstallService - Install HostMonitor as Win32 interactive service.
    /UninstallService- Uninstall service

    If you install HostMonitor as a service, the program will be started by the service control manager automatically during system startup. For more information see "How to install HostMonitor as Win32 Interactive service" section.