MySQL

Supported Versions V4.1, V5.0.
Collection
Methods
JDBC Queries
Requirements
  • MySQL account with SELECT privilege on the monitored database, and permission to connect from the Longitude server.
  • The MySQL Tablespace reports only include data for tables using the InnoDB storage engine.
  • The MySQL TableSpaceFull rule functions at the MySQL Server level rather than once for each monitored instance.
Configuration
  1. Use Monitor Devices
  2. If necessary, select a Longitude Remote Agent.
  3. Select MySQL
  4. Enter the name of the MySQL server to be monitored in the Computers field.
  5. The Instance value is used by Longitude to distinguish between different MySQL databases being monitored on the same server. It is recommended to set the Instance to be the same as the MySQL Database, but any unique string may be used. Registering the same Instance twice on the same computer will overwrite the details of the first registration.
  6. Enter the name of the MySQL Database being monitored.
  7. Enter the name of the MySQL User account.
  8. Enter the Password for the MySQL User
  9. Enter the Port used to communicate with MySQL via JDBC. The default port for MySQL is 3306.
  10. Click Monitor
  11. Repeat the configuration steps with different Instance and MySQL Database values to monitor additional MySQL databases on he same server.
Troubleshooting
  • Collections fail with a Host…is not reachable or Connection timed out error:
    Longitude was unable to connect to MySQL on the configured port. Verify that MySQL allows connections from the Longitude server on port 3306. This may be tested using a Port Transaction in Longitude.

 

Netflow

Supported Versions V5, V9
Collection Methods Netflow Listener
Requirements
  • The Local Agent on the Longitude Management Console should be used as the Netflow collector.
  • The Netflow collector is a listener that receives data sent by Netflow enabled network devices.
  • Each network device monitored by the Netflow application in Longitude must be configured to export data to the Longitude Management console. Consult the documentation for the network device for the syntax needed to set up the data export.
  • By default, the Netflow listener in Longitude will listen on the default Netflow port of 2055. If you configure Netflow to export on a different port, Longitude must also be configured to use that port.
  • If multiple network devices are sending Netflow data to Longitude, each should be configured to send to a different port.
  • If there is a firewall between the Longitude Management Console and the network device sending Netflow data, verify that the firewall will allow the Netflow packets through.
Configuration
  1. Use Monitor Devices
  2. Select Netflow
  3. Make sure the Agent field is set to Local.
  4. The Instance value is used by Longitude to distinguish between different Netflow instances. If you have network devices sending data to different ports, use a different Instance name for each port.
  5. Enter the Port on which the Netflow data is being transmitted. The default Netflow port is 2055 – a different port should be associated with each instance.
  6. Click Monitor
  7. Repeat the configuration steps with different Instance and Port values to monitor additional ports for Netflow data.
Troubleshooting
  • Netflow reports do not contain data
    • Check the Longitude\ss\log\Netflow directory on the Longitude server to verify the listener collection files are populated. If the files are empty, verify that the configuration on the network devices and any firewalls is correct.
    • Restart the Longitude Stastistics Server on the Management Console and check the startup log in Longitude\ss\log\ss_startup.txt. Verify that it contains:
       
      Netflow receiver listening on port: Port#
       
      With one line for each port configured for Netflow. If these lines are not present, check for error messages in the Longitude\ss\log\yyyymmdd_ss_error_##.txt file.

 

Network Device

Supported Versions SNMP V1, V2
Collection
Methods
SNMP
Requirements
  • The Network Device should be configured to allow Longitude to request SNMP V1 or V2 data.
  • The NetworkDevice application monitors the following OIDs:
    Component OID MIB
    Buffer .1.3.6.1.4.1.9.2.1 OLD-CISCO-MEMORY-MIB
    CPU .1.3.6.1.4.1.9.2.1.58 OLD-CISCO-CPU-MIB
    Interface Status V1: .1.3.6.1.2.1.2.2
    V2: .1.3.6.1.2.1.31.1.1
    V1: RFC1213-MIB
    V2: IF-MIB (RFC2863)
    Memory .1.3.6.1.4.1.9.9.48.1.1 CISCO-MEMORY-POOL-MIB
    Mobile IP (MIP) Security Stats .1.3.6.1.2.1.44.1.2.3 RFC2006-MIB
    MIP Violations .1.3.6.1.2.1.44.1.2.2 RFC2006-MIB
    RFC 1213 ICMP .1.3.6.1.2.1.5 RFC1213-MIB
    RFC 1213 Interface V1: .1.3.6.1.2.1.2.2
    V2: .1.3.6.1.2.1.31.1.1
    V1: RFC1213-MIB
    V2: IF-MIB (RFC2863)
    RFC 1213 SNMP .1.3.6.1.2.1.11 RFC1213-MIB
    RFC 1213 TCP .1.3.6.1.2.1.6 RFC1213-MIB
    RFC 1213 UDP .1.3.6.1.2.1.7 RFC1213-MIB

  • The Component, Buffer, CPU and MIP metrics are not available on all devices. If the SNMP request does not return data for these components, they will not be registered.
Configuration
  1. Use Monitor Devices or see the Network Device instructions for Device Discovery.
  2. If necessary, select a Longitude Remote Agent.
  3. If monitoring manually, select NetworkDevice
  4. Enter the name of the Network Device to be monitored in the Computers field.
  5. Select V1 or V2 as the Platform. NetworkDevice monitoring configured via Discovery will be done in V1.
  6. Enter an SNMP V1 or V2 Community string with at least Read Only privileges in the Community field.
    Note: The community string is case sensitive.
  7. UDP port 161 is the default SNMP request port. If SNMP on the Network Device uses a different port, adjust the Portvalue.
  8. Leave the TimeoutSeconds value at 5 and the Retries value at 1. If the collection done at registration times out due to a slow connection, adjust these values and try registering again.
  9. Click Monitor
Troubleshooting
  • Collections fail with the message Error Registering…no statistic rows were returned:
    Longitude was able to contact SNMP, but the requested data was not returned. This message will only be returned for colelctions listed as required in the Network Device OID table. Verify that data can be returned for the OIDs in the table that are listed as failing.
  • Collections fail with the message Error Registering…time out after retries:
    Longitude was not able to contact SNMP on the Network Device. Verify the following:
    • SNMP is running on the Network Device.
    • The Longitude server has permission to request data via SNMP – consult the documentation for your Network Device for details on configuring this.
    • The SNMP Community string is correct.
    • The SNMP port is configured correctly, and there is nothing blocking traffic between Longitude and the Network Device.
    • If the configuration is set up correctly, and there is a slow network connection between Longitude and the Network Device, adjust the TimeoutSeconds and/or Retries properties to allow for slow or failed SNMP connections.
  • Not all interfaces are listed in the RFC1213 Interface collection:
    Interface collections are filtered to only collect data for interfaces with Input or Output KB greater than 0. Interfaces with no traffic will not be collected.
  • Clicking Test/Retry for Rfc1213IF collection produces no statistic rows were returned error:
    This error may be returned when testing interface collections if there has been no traffic since the last collection for any interfaces. The message may be disregarded.

 

OpenManage

Supported Versions OpenManage 4.5 and 5.0
Collection Methods SNMP
Requirements
  • The SNMP service must be running on the computer running OpenManage.
  • The SNMP Service on the OpenManage computer should be configured to allow Longitude to request SNMP data.
  • The OpenManage application monitors the following components:
    Component OID MIB
    Chassis .1.3.6.1.4.1.674.10892.1.300.10 10892
    Current Probe .1.3.6.1.4.1.674.10892.1.600.30 10892
    Fan Status .1.3.6.1.4.1.674.10892.1.700.12 10892
    Memory .1.3.6.1.4.1.674.10892.1.1300.10 10892
    Power Supply .1.3.6.1.4.1.674.10892.1.600.12 10892
    Processor .1.3.6.1.4.1.674.10892.1.1100.30 10892
    Storage .1.3.6.1.4.1.674.10893.1.20.130.4 dcstorag
    Temperature Probe .1.3.6.1.4.1.674.10892.1.700.20 10892
    Voltage Probe .1.3.6.1.4.1.674.10892.1.600.20 10892
Configuration
  1. Use Monitor Devices
  2. If necessary, select a Longitude Remote Agent.
  3. Select OpenManage
  4. Enter the name of the OpenManage computer to be monitored in the Computers field.
  5. Enter an SNMP V1 Community string with at least Read Only privileges in the Community field.
  6. UDP port 161 is the default SNMP request port. If SNMP on the OpenManage computer uses a different port, adjust the Portvalue.
  7. Leave the TimeoutSeconds value at 5 and the Retries value at 1. If the collection done at registration times out due to a slow connection, adjust these values and try registering again.
  8. Click Monitor
Troubleshooting
  • OpenManage registers successfully, but is not listed as a monitored application:
    All components in the OpenManage application are optional, and no errors are logged if data is not returned. If there are no registration errors, but OpenManage is not listed as monitored, verify:

    • OpenManage is configured to respond to SNMP requests for the monitored OID values.
    • The SNMP Service is running on the computer running OpenManage.
    • The Longitude server has permission to request data via SNMP – this is configured on the Security tab of the SNMP Service Properties.
    • The SNMP Community string is correct.
    • The SNMP port is configured correctly, and there is nothing blocking traffic between Longitude and the computer running OpenManage.
    • If the configuration is set up correctly, and there is a slow network connection between Longitude and the computer running OpenManage, adjust the TimeoutSeconds and/or Retries properties to allow for slow or failed SNMP connections.

 

Oracle

Supported Versions 9, 10g, 11g
Collection Methods JDBC Queries
Requirements
  • Oracle account with CONNECT and SELECT_CATALOG_ROLE privilege on the monitored instance.
  • Longitude JDBC queries to Oracle instances are not blocked by by a firewall.
Configuration
  1. Use Monitor Devices
  2. If necessary, select a Longitude Remote Agent.
  3. Select Oracle
  4. Enter the name of the Oracle server to be monitored in the Computers field.
  5. The Instance value is used by Longitude to distinguish between different Oracle instances being monitored on the same server. It is recommended to set the Instance to be the same as the Oracle Instance, but any unique string may be used. Registering the same Instance twice on the same computer will overwrite the details of the first registration.
  6. Enter the name of the Oracle Instance being monitored. This name should be resolvable through the tns_listener on the Oracle server.
  7. Enter the name of the Oracle User account.
  8. Enter the Password for the Oracle User
  9. Enter the Port used to communicate with Oracle via JDBC. The default port for Oracle is 1521.
  10. Enter the TopNQueries value – this will be used for the maximum number of results returned by the Oracle_LongQueries collector. The default value is 10.
  11. Click Monitor
  12. Repeat the configuration steps with different Instance and Oracle Instance values to monitor additional Oracle instances on he same server.
Troubleshooting
  • Collections fail with a Read timed out error:
    Longitude is unable to connect with the Oracle server on the specified port. Check the following:

    • Check the Oracle server is being resolved to the correct IP Address.
    • Check the port used by Oracle
    • If other Longitude applications are monitored on the Oracle server, check the Computer Status screen to determine the agent used for collecting data for the Oracle server. All Longitude applications will be collected by this agent, regardless of the selection in the Monitoring configuration. Verify that the Agent for the Oracle server is able to make a JDBC connection over the specified Oracle port.
    • The Oracle listener port can be checked using a Port Transaction.
  • Collections fail with a 12505 reads ‘TNS: listener could not resolve SID given in connection description error:
    Check that the Oracle Instance specified is correct.
  • Collections fail with a The Network Adapter could not establish the connection error:
    Check that the tns_listener is running on the Oracle server.
  • Collections fail with an ORA-01017: invalid username/password; logon denied error:
    Check that the username and password for the specified Oracle instance are correct.
  • Collections fail with an ORA-01045: user … lacks CREATE SESSION privilege; logon denied error:
    The Oracle user account does not have CONNECT privilege to the specified Oracle Instance.
  • Collections fail with an ORA-00942: table or view does not exist error:
    The Oracle user account does not have SELECT_CATALOG_ROLE privilege to the specified Oracle Instance.

 

SnmpTrap

Supported Versions SNMP V1, V2, V3
Collection Methods SNMP Listener
Requirements
  • The computers and network devices sending SNMP traps must be configured to send traps to Longitude. This configuration will vary depending on the application sending traps – consult your application’s documentation for configuration details.
  • Either the Longitude Management Console or a Longitude Remote Agent may be configured to listen for traps.
  • Any vendor specific MIBs for the traps should be copied to the Longitude\lib\mibs directory on the Longitude Management Console and any Longitude Remote Agents listening for traps.
  • Only one listener can function at a time for any given port. If other listeners are installed on a Longitude listener, whichever listener starts first will attach to the port and receive data. Stop all other SNMP listeners on Longitude servers listening for traps, and set any trap listener services to Manual start.
  • On Windows servers, the SNMP Trap service is an SNMP Trap listener, and should be stopped, and set to Manual or Disabled.
  • Verify that any routers or firewalls between the SNMP sender and the Longitude listener will not block SNMP Traffic.
  • If SNMP V3 Authentication or Encryption is used for traps, that information will be needed to configure Longitude so that it can decode the traps.
  • SNMP listeners do not require a Community string to listen for traps.
  • SNMP traps have a Generic Trap Number property which is set as follows:
    Generic Trap # Name Indicates
    0 coldStart Reboot has occurred
    1 warmStart SNMP has restarted
    2 linkDown Interface has gone down
    3 linkUp Interface is back up
    4 authenticationFailure Incorrect community string or SNMP V3 credentials
    5 egpNeighborLoss On a host running a gated daemon, indicates Exterior Gateway Protocol (EGP) neighbor loss
    6 enterpriseSpecific Vendor specific traps
Configuration
  1. Use Monitor Devices.
  2. Select SnmpTrap.
  3. Set the Agent to the Longitude Management Console or the Remote Agent listening for the traps.
  4. If the OID field is empty, all incoming traps will be recorded. If any OIDs are entered into this field, only OIDs that match the entries will be recorded.
  5. The Generic field will filter traps based on their generic trap number (see Generic Trap Number chart). In most cases you will only select enterpriseSpecific. If nothing is selected, all Generic trap number values will be collected.
  6. enterpriseSpecific traps also have Specific trap numbers which are assigned when the trap is generated. In most cases, this field will be left blank to accept all Specific trap numbers.
  7. The Device field may be used to filter which devices traps will be accepted from. In most cases, this field will be left blank to accept traps from all devices.
  8. The User field specifies the User name associated with SNMP V3 traps. Only one value is allowed in this field.
  9. Select the Authentication Protocol for SNMP V3 authentication, if used.
  10. Enter the Authentication Password for SNMP V3 if authentication is used. Only one value is allowed in this field. This field may be left blank if SNMP V3 authentication is not used.
  11. Select the Privacy Protocol if SNMP V3 encryption is used. The default value is 0 for DES, with the option of 1 for AES.
  12. Enter the Privacy Password if SNMP V3 encryption is used. Only one value is allowed in this field. This field may be left blank if SNMP V3 encryption is not used.
  13. Enter the Engine ID if SNMP V3 encryption is used. Only one value is allowed in this field. This field may be left blank if SNMP V3 encryption is not used.
  14. Click on Monitor button.
  15. If additional sets of SNMP V3 authentication and/or encrpytion are needed, configure additional Longitude Remote Agent listeners to receive these traps.
Troubleshooting
  • SNMP Traps are not displayed in the SNMP Traps view of the Event Monitor.
    1. Restart the Statistics Server service on the Longitude server receiving the traps and check the Longitude\ss\log\ss_startup.txt file. It should contain the lines:
      SnmpTrap receiver listening on port: 162
      and
      Waiting for traps
      If these lines are not listed, register the SNMPTrap application for the agent again, and check the Longitude\ss\log\yyyymmdd_ss_error_##.txt file on the Longitude server configured to listen for registration error messages.
    2. Check the Longitude\ss\log directory for files named yyyymmdd_snmptrap_##.txt – as traps are received, they are written to this file, and later archived. If this file is empty, the Longitude listener is not receiving any traps. Recheck the configuration of the devices sending traps, and if there are any firewalls blocking traps.
    3. If there is data in the trap receiver file, it will be written to the database and available in the Event Monitor on the next collection by the consolidator, which occurs every 5 minutes. If data is still not avialable after the interval has passed, check the Longitude\consolidator\log\yyyymmdd_consolidtor_error_##.txt file for errors parsing the collection file.
  • Collections fail with java.net.SocketException: Unrecognized Windows Sockets error: 0: Cannot bind error:
    Longitude is unable to listen on the requested port because the port is already bound to another listener. Check the Longitude server for other applications or services that are listening for traps. If the other listener is a service, set it to Disabled or Manual start to prevent it from attaching to the port before Longitude does after a reboot.
  • Traps contain OID numbers instead of text:
    As Longitude receives traps, it formats them based on the contents of the MIB files in the local Longiude\lib\mib directory.

    1. Check that the applicable vendor MIBs are in this directory on both the Longitude Management Console, and, if applicable, the Longitude Remote Agent receiving the traps.
    2. If the MIBs are in the directory, restart the Longitude Statistics Server service and check the Longitude\lib\ss\ss_startup.txt file for MIB compilation errors.

 

SQL2005, SQL2008, SQL2012, SQL2014

Supported Versions SQL2005, SQL2008, SQL2012, SQL2014
Collection Methods JDBC Queries and WMI
Requirements
  • JDBC query permissions:
    • If the SQL Server supports Windows Authentication mode, queries will be run using the credentials of the Longitude Statistics Server account. This account must have administrator privileges within the SQL Application.
    • If the SQL Server supports mixed Windows and SQL Server Authentication, the default behavior is to use Windows Authentication.
    • A SQL account may be specified for JDBC collections during configuration. If a SQL account is used, the specified account must have permission to execute select queries against the sys.dm_exec_query_stats view.
  • For WMI collections, the Longitude Statistics Server account must have Local Administrator privileges on the SQL computer.
  • For WMI collections, the Windows Management Instrumentation (WMI) service must be running on the SQL computer.
  • The SQL application will monitor SQL specific services via WMI and create an event when one of these services is not running. If a listed service is not installed, it will not be monitored. Additional services may be monitored using Service Transactions. The monitored services are:
    Service Display Name Default Instance Service Name Named Instance Service Name
    SQL Server
    Analysis Services
    MSSQLSERVEROLAPSERVICE MSOLAP$<instance>
    SQL Server Full
    Text Search
    MSFTESQL MSFTESQL$<instance>
    SQL Server
    Reporting Services
    REPORTSERVER REPORTSERVER$<instance>
    SQL Server Integration Services MSDTSSERVER MSDTSSERVER
    SQL Server Integration Services 10.0 MSDTSSERVER100 MSDTSSERVER100
    SQL Server
    Browser
    SQLBROWSER SQLBROWSER
    SQL Server Active Directory Helper MSSQLSERVERADHELPER MSSQLSERVERADHELPER
    SQL Server VSS Writer SQLWRITER SQLWRITER

     

Configuration
  1. Use Monitor Devices
  2. If necessary, select a Longitude Remote Agent.
  3. Select one of SQL2005, SQL2008, SQL2012 or SQL2014.
  4. Enter the name of the SQL server to be monitored in the Computers field.
  5. The Instance value is used by Longitude to distinguish between different SQL Server instances being monitored on the same server.
    • It is recommended to set the Instance to be the same as the NamedInstance, but any unique string may be used.
    • Registering the same Instance twice on the same computer for the same application will overwrite the details of the first registration.
    • The Instance field will be updated to the value entered into the NamedInstance field when that field is tailored, but the Instance may be modified before the collection is registered.
    • If the NamedInstance field is empty, the value for Instance will be default.
  6. The NamedInstance is the name of the SQL Server instance to be monitored. If left blank, this will monitor the default SQL instance on the server.
  7. The default Database Driver is: net.sourceforge.jtds.jdbc.Driver. Change this value only if your SQL instance requires a custom driver.
  8. The default Database URL is: jdbc:jtds:sqlserver://~host~;integratedSecurity=true;
    • During registration, Longitude will substitute the name of the monitored server for ~host~. If you need to use a host name for the SQL instance that is different than the name of the computer, modify it in the URL before registration.
    • The integratedSecurity=true; portion of the URL is preset for Windows Integrated Authentication. Set this to integratedSecurity=false; if using a SQL account for JDBC queries.
    • The JDBC url will use port 1433. If SQL uses another port, add the port after the host name, e.g. if using port 1435: jdbc:jtds:sqlserver://~host~:1435;integratedSecurity=true;
  9. Enter a SQL account name into the User field if using a SQL account for JDBC. If using Windows authentication, this field may be left blank.
  10. Enter the password for the SQL user account in the Password field if using a SQL account for JDBC. If using Windows authentication, this field may be left blank.
  11. The TopNJobs value will limit the number of jobs returned by the FailedJobs and LongestJobs collectors. The default value is 10.
  12. The TopNQueries value will limit the number of query results returned by the FrequentQueries,
    LongestQueries and WorstQueries collectors. The default value is 50.
  13. Click Monitor
  14. Repeat the configuration steps with different Instance and NamedInstance values to monitor additional SQL Server instances on he same server.
Troubleshooting
  • SQL Performance Collections fail with an Invalid Class error:
    1. Check PerfMon on the SQL Server computer to verify that the SQL Performance Monitor collectors have been installed.
    2. If the PerfMon counters are not listed, they will need to be rebuilt. In some cases, the following steps will restore the counters:
      1. Log on to the SQL server
      2. Open a command prompt with elevated privileges
      3. For the default instance run the command:
        unlodctr.exe MSSQLServer
      4. For a named instance, run the command:
        unlodctr.exe MSSQL$Instance
        where Instance is a named SQL instance
      5. Navigate to the Binn directory under the installation directory for the SQL instance
      6. Find the name of the PerfMon .ini file – this will be in the format perf-Instancesqlctr.ini
      7. Run the command: lodctr.exe perf-Instancesqlctr.ini, using the name of the Performance counter .ini file in the Binn directory
      8. Resynchronize WMI with PerfMon by running: winmgmt /resnycperf
      9. Restart the Windows Management Instrumentation service on the computer
      10. If the SQL PerfMon counters are still not present, reboot the server

      Please note that, depending on why the counters are unavailable, this method may not work to restore SQL PerfMon counters. Consult Microsoft documentation for additional methods of restoring PerfMon counters.

    3. If the SQL PerfMon counters do exist, resynchronize them with WMI:
      1. Log on to the target computer with a local administrator account.
      2. Open a command prompt and run the command: winmgmt /resyncperf.
      3. Restart the Windows Management Instrumentation service on the target computer.
  • Index collection resource usage
    The SQL Index collection runs at 6AM each day, and can be resource intensive. If you notice performance issues from this collection, contact Longitude Support at support@heroix.com for information on disabling SQL Index collections.
  • Low free memory alerts on SQL servers
    SQL instances may be configured to use most of the memory on a server, so that the server functions correctly with 100% memory used. In this case, either disable the alert, or configure the threshold for the SQL >> Resources >> LowAvailableMemory alert to AvailableMemoryMin = 0.
  • TranasctionLogsFull alerts for logs that are set to Autogrow
    Configure the threshold for the SQL >> Databases >> TransactionLogsFull alert to LogFilesUsedPctMax = 100.

 

Syslog

Supported Versions RFC5424
Collection Methods Syslog Listener
Requirements
  • The computers and network devices sending Syslog messages must be configured to send messages to Longitude. Consult your server or network device’s documentation for configuration details.
  • Either the Longitude Management Console or a Longitude Remote Agent may be configured to listen for Syslog messages.
  • Only one listener can function at a time for any given port. If other listeners are installed on a Longitude listener, whichever listener starts first will attach to the port and receive data. Stop all other Syslog listeners on Longitude servers listening for Syslog messages, and set any Syslog listener services to Manual start.
  • Longitude listens for Syslog messages on port 514. This is not configurable.
  • If the Longitude listener is a Remote Agent on a Linux server, the Statitics Server on the Agent needs to run under the root account. The Statistics Server account on the agent is set by the FIRENZE_USER value in Longitude\bin\firenze_ss. After changing this value, the Statistics server may be restarted by running:
    /etc/init.d/firenze_ss stop
    /etc/init.d/firenze_ss start
  • Verify that any routers or firewalls between the Syslog sender and the Longitude listener will not block Syslog Traffic.
  • Syslog messages have Facilties defined as follows:
    Facility Number Facility Name
    0 kernel
    1 user-level
    2 mail system
    3 system daemons
    4 authorization
    5 syslog
    6 line printer subsystem
    7 network news subsystem
    8 UUCP subsystem
    9 clock daemon
    10 security
    11 FTP daemon
    12 NTP subsystem
    13 log audit
    14 log alert
    15 clock daemon
    16 local use 0
    17 local use 1
    18 local use 2
    19 local use 3
    20 local use 4
    21 local use 5
    22 local use 6
    23 local use 7

     

  • Syslog messages have the following severities, with their Longitude equivalents:
    Syslog Severity Number Syslog Severity Name Longitude Alert Severity
    0 Emergency Critical
    1 Alert Critical
    2 Critical Critical
    3 Error Major
    4 Warning Minor
    5 Notice Warning
    6 Informational Warning
    7 Debug Warning

     

Configuration
  1. Use Monitor Devices.
  2. Select Syslog.
  3. Set the Agent to the Longitude Management Console or the Remote Agent listening for the traps.
  4. If the Device field is empty, all incoming Syslog messages will be recorded. If any servers or network devices are entered into this field, only messages from the listed devices will be recorded.
  5. Select the Facility values you would like to receive.
  6. Select the Severity values you would like to receive.
  7. Click on the Monitor button.
  8. Repeat configuration if additional listeners are used.
Troubleshooting
  • Syslog Messages are not displayed in the Syslog view of the Event Monitor:
    • As Syslog messages are received, they are written to files in the Longitude\ss\log directory named yyyymmdd_syslog_##.txt. If these files do not exist or are empty, the Longitude listener is not receiving any Syslog messages. Recheck the configuration of the devices sending Syslog messages, and if there are any firewalls blocking Syslog messages.
    • If there is data in the Syslog receiver file, it will be written to the database and available in the Event Monitor on the next collection by the consolidator, which occurs every 5 minutes. If data is still not available after the interval has passed, check the Longitude\consolidator\log\yyyymmdd_consolidtor_error_##.txt file for errors parsing the collection file.
  • Collections fail with java.net.SocketException: Unrecognized Windows Sockets error: 0: Cannot bind error:
    Longitude is unable to listen on the requested port because the port is already bound to another listener. Check the Longitude server for other applications or services that are listening for traps. If the other listener is a service, set it to Disabled or Manual start to prevent it from attaching to the port before Longitude does after a reboot.

 

Transactions

Supported Versions Longitude Transactions are tests for the availability of specified protocols. When a test fails, a Critical severity Longitude event will be created, and updated at each collection interval for as long as the problem occurs. When the problem has been resolved, the first interval with a successful test will generate a Cleared severity event.

Please see individual protocol descriptions for version restrictions, if they exist. Transactions test the following protocols:

Transaction Description
DNS The DNS transaction enables you to test whether a DNS server can resolve the IP address of a fully qualified host name.
FileContent The FileContent transaction enables you to check a file for undesired content, such as an error message recorded in a log file.
FileExistence The FileExistence transaction enables you to monitor for the existence of a file. The transaction can be configured so that the absence of the file will generate an event or so that the existence of the file will generate an event. The transaction can also be configured to consider only files that have been modified during the current day, or to consider files regardless of the modification date.
FTP The FTP transaction enables you to test whether a user can connect to an FTP server.
HTTPConnect The HttpConnect transaction enables you to test whether Longitude can connect to an HTTP site.
HTTPUrl The HTTPUrl transaction enables you to test whether the text on a web page matches the expected content.
NNTP The NNTP transaction enables you to test whether an NNTP server is accessible and able to reply with a list of newsgroups.
Ping The Ping transaction enables you to test for a response to echo requests.
PingCritical The PingCritical transaction enables you to test for a response to echo requests at a more frequent interval than the default Ping transaction. The PingCritical transaction is tested on a one minute interval, while the Ping transaction is tested on a 5 minute interval. The PingCritical transaction is recommended for monitoring critical servers, so that you are notified more quickly when they become unreachable. For less critical servers the Ping transaction is recommended because it will reduce the amount of unnecessary data that is collected and reduce the workload on the Longitude components.
Port The Port transaction enables you to test whether a connection can be made to a port.
Service The Service transaction enables you to test whether a particular service is running. The Longitude Windows application monitors services that are set to a start mode of ‘Auto’, ‘Boot’ or ‘System’, and the Longitude Exchange, IIS and SQL applications will also monitor application specific services. The Service Transaction may be used to monitor additional services, or to set up alerts that include a Cleared update when the service is back online.
SMTP The SMTP transaction enables you to test whether a connection can be made to an SMTP server.
SQLConnect The SQLConnect transaction enables you to test whether a connection can be made to a database server.
SQLQuery The SQLQuery transaction enables you to test whether a SQL query completes successfully and evaluate the return from the query.
SSH The SSH transaction enables you to test whether an SSH connection can be made to a server.
Telnet The Telnet transaction enables you to test whether an Telnet connection can be made to a server.
UnixConnect The UnixConnect transaction enables you to test whether a connection can be made to a Unix/Linux server using either SSH or rexec. It also allows the connection to be made using public-key authentication, if desired.
UnixProcess The UnixProcess transaction enables you to test whether a particular process exists on a Unix or Linux computer. A Critical severity event will be generated for each interval the process is not found on the monitored server, followed by one Cleared severity event when the process restarts.
UnixScript The UnixScript transaction enables you to evaluate the output of a script or command on a Unix or Linux server.
WinProcess The WinProcess transaction enables you to test whether a particular process exists on a Windows computer. A Critical severity event will be generated for each interval the process is not found on the monitored server, followed by one Cleared severity event when the process restarts.
WinScript The WinScript transaction enables you to monitor the output of a script run from a Windows Longitude server.
WinShare The WinShare transaction tests whether a Windows share exists.
WMIConnect The WmiConnect transaction enables you to test whether Longitude can connect to WMI on a computer.

 

Regular expressions may be used for transactions which evaluate text. Please note that regular expressions are case-sensitive.The following table contains a brief list of commonly used metacharacters in regular expressions – additional information on regular expression syntax can be found onine.

Metacharacter Description
. Wildcard match for a single character.
.* Wildcard matching any number of characters. For example, .*Heroix.* would be a case-sensitive match for “Heroix” anywhere in the scanned text.
[] Range of characters allowed to match for a single character. For example, [hH]eroix would match “Heroix” or “heroix”.
\ Escape character. The character following \ will be treated literally. For example, .*Longitude\..* would match “Longitude.”, where the \. matches a “.” rather than using the . as a wildcard.
\d Matches any number, 0-9
\D Matches any character that is not a number.
\s Matches any whitespace character.
\S Matches any character that is not whitespace.
\w Matches any number or letter.
\W Matches any character that is not a number or letter (e.g. punctuation).
^ Anchors expression to front of line.
$ Anchors expression to end of line.
{} Specifies number of occurrences to expect, for example, \w{8} matches 8 letters or numbers.

 

The SQLQuery, UnixScript and WinScript transactions are evaluated as successful when they return data that satisfies a comparison condition. The comparison operators are:

Operator Data Type Description
>
>=
<
<=
Numeric Numeric comparison
= Numeric or Text Exact Match
!= Numeric or Text Not an Exact Match
between[a,b]
between(a,b]
between[a,b)
between(a,b)
Numeric Between numbers a and b, with [ indicating the number is included, and ( indicating the number is not included. For example, between [1,6) means >= 1 and <6.
like Text Comparisons with regular expressions using wildcards
likein Text Comma separated list of “like” comparisons
not like Text String returned does not match a comparison with regular expressions using wildcards
in Text Comma separated list of exact text matches. Extra whitespace is not removed before comparison, and should not be part of the entered list.
not in Text Comma separated list of text that should not be matched. Extra whitespace is not removed before comparison, and should not be part of the entered list.

 

DNS Transaction
The DNS transaction enables you to test whether a DNS server can resolve the IP address of a fully qualified host name.
Collection Methods NSLookup
Requirements None
Configuration
  1. Use Monitor Devices.
  2. Select Transaction.
  3. Select DNS.
  4. If necessary, select a Longitude Remote Agent.
  5. Enter the name of one or more DNS servers to be queried in the Computers field. Multiple server names should be separated by a comma.
  6. The Instance value is used by Longitude to distinguish between different DNS Transactions being monitored on the same server. Registering the same Instance twice for the same computer and transaction type will overwrite the details of the previous registration.
  7. Enter in a name to resolve via the specified DNS server. Please note that the DNS transaction will resolve one name for each transaction.
  8. Click on the Monitor button.
  9. Repeat configuration to monitor additional DNS server or names.
FileContent Transaction
The FileContent transaction enables you to check a file for undesired content, such as an error message recorded in a log file.
Collection Methods WMI or SSH
Requirements
  • The file being monitored is accessed from a Longitude agent through a shared filesystem.
    Longitude Agent OS OS for server with monitored file File accessed through
    Windows Windows Windows Share
    Windows Unix/Linux Samba Share
    Linux Unix/Linux NFS Share
  • For Windows and Samba shares on Windows Longitude agents, the Statistics Server account must have permission to access the share.
  • For Linux Longitude agents monitoring files through NFS shares, the NFS share must be mounted, and the Longitude User account must have permission to read files on the mountpoint.
  • During the initial registration, all matching files will be parsed for the requested UndesiredContent value. After the initial registration, only new lines in matching files will be checked.
Configuration
  1. Use Monitor Devices.
  2. Select Transaction.
  3. Select FileContent.
  4. If necessary, select a Longitude Remote Agent.
  5. Enter the name of the computer hosting the file in the Computers field. This will be used as part of the path constructed to find the file.
  6. The Instance value is used by Longitude to distinguish between different FileContent transactions being monitored on the same server. Registering the same Instance twice for the same computer and transaction type will overwrite the details of the previous registration.
  7. Enter the ShareName needed to access the file. If the file is in a directory under the share, include any directories in the path to the file. The ShareName should not have a trailing \ or /. For example, to specify a “logs” directory under the d$ admin share, you would use: d$\logs
  8. Enter the FileName to be monitored. Wildcards may be used for files with variable names. For example, the regular expression for 20130101_error_log.txt may be specified as \d{8}_error_log.txt, where \d specifies that a number is expected, and {8} specifies 8 total digits are expected.
  9. The UndesiredContent field should contain a regular expression for the text for which you would like to receive alerts. For example .*[eE]rror.* or ^CRITICAL
  10. Click on the Monitor button.
  11. Repeat configuration to monitor additional files or patterns.
Troubleshooting
  • FileContent transactions takes too long to register:
    After the FileContent transaction has been registered, it will only collect data that has been created since the
    last collection. However, during the initial collection the file content transaction will examine all data that
    matches the specified file name. If there is a large amount of data in the initial collection, it is possible the
    the registration will timeout. In this case, try a more specific file name, or move older files out of the log
    directory.
  • Undesired content does not produce alerts:
    Verify that the regular expression used to match the pattern is not too strict. In most cases, the match should start
    and end with a .*, allowing the content to be anywhere in the file.
FileExistence Transaction
The FileExistence transaction enables you to monitor for the existence of a file. The transaction can be configured so that the absence of the file will generate an event or so that the existence of the file will generate an event. The transaction can also be configured to consider only files that have been modified during the current day, or to consider files regardless of the modification date.
Collection Methods WMI or SSH
Requirements
  • The file being monitored is accessed from a Longitude agent through a shared filesystem.
    Longitude Agent OS OS for server with monitored file File accessed through
    Windows Windows Windows Share
    Windows Unix/Linux Samba Share
    Linux Unix/Linux NFS Share
  • For Windows and Samba shares on Windows Longitude agents, the Statistics Server account must have permission to access the share.
  • For Linux Longitude agents monitoring files through NFS shares, the NFS share must be mounted, and the Longitude User account must have permission to read files on the mountpoint.
Configuration
  1. Use Monitor Devices.
  2. Select Transaction.
  3. Select FileExistence.
  4. If necessary, select a Longitude Remote Agent.
  5. Enter the name of the computer hosting the file in the Computers field. This will be used as part of the path constructed to find the file.
  6. The Instance value is used by Longitude to distinguish between different FileExistence transactions being monitored on the same server. Registering the same Instance twice for the same computer and transaction type will overwrite the details of the previous registration.
  7. Enter the ShareName needed to access the file. If the file is in a directory under the share, include any directories in the path to the file. The ShareName should not have a trailing \ or /. For example, to specify a “logs” directory under the d$ admin share, you would use: d$\logs
  8. Enter the FileName to be monitored. Wildcards may be used for files with variable names. For example, the regular expression for 20130101_error_log.txt may be specified as \d{8}_error_log.txt, where \d specifies that a number is expected, and {8} specifies 8 total digits are expected.
  9. Set FileShouldExist to yes if you want to be alerted when the file is not found. Set this field to no if you want an alert when the file is found.
  10. Set TodaysDate to yes if you only want to look at files modified within the last day. Set this field to no if you want to consider all matching files in the directory.
  11. Click on the Monitor button.
  12. Repeat configuration to monitor additional files.
FTP Transaction
The FTP transaction enables you to test whether a user can connect to an FTP server.
Collection Methods FTP
Requirements None
Configuration
  1. Use Monitor Devices.
  2. Select Transaction.
  3. Select FTP.
  4. If necessary, select a Longitude Remote Agent.
  5. Enter the name of the FTP Server in the Computers field.
  6. The Instance value is used by Longitude to distinguish between different FTP transactions being monitored on the same server. Registering the same Instance twice for the same computer and transaction type will overwrite the details of the previous registration.
  7. Enter the Username needed to connect to the FTP server.
  8. Enter the Password for the FTP Username.
  9. Enter the Port for the FTP server. The default FTP port is 21.
  10. Click on the Monitor button.
  11. Repeat configuration to monitor additional FTP servers.
HttpConnect Transaction
The HttpConnect transaction enables you to test whether Longitude can connect to an HTTP site.
Collection Methods Port check
Requirements None
Configuration
  1. Use Monitor Devices.
  2. Select Transaction.
  3. Select HttpConnect.
  4. If necessary, select a Longitude Remote Agent.
  5. Enter the name of the Web Server in the Computers field.
  6. The Instance value is used by Longitude to distinguish between different HttpConnect transactions being monitored on the same server. Registering the same Instance twice for the same computer and transaction type will overwrite the details of the previous registration.
  7. Enter the Port the Web Server is listening on. If left blank, port 80 will be used for http, and port 443 will be used for https.
  8. Click on the Monitor button.
  9. Repeat configuration to monitor additional Web Servers.
HttpUrl Transaction
The HTTPUrl transaction enables you to test whether the text on a web page matches the expected content.
Collection Methods HTTP or HTTPS download.
Requirements The HttpUrl transaction registers an associated HttpConnect transaction. If the HttpConnect transaction fails during registration, the HttpUrl transaction will not be registered. It is possible for this transaction to fail if host headers are used by the Web Server. Contact Longitude support at support@heroix.com for assitance in registering the HttpUrl transaction without an HttpConnect transaction.
Configuration
  1. Use Monitor Devices.
  2. Select Transaction.
  3. Select HttpUrl.
  4. If necessary, select a Longitude Remote Agent.
  5. Enter the URL to be monitored into the URL field. The Computers, Path, Port and Protocol values will be extracted from the URL and copied to the appropriate fields.
  6. The Instance value is used by Longitude to distinguish between different HttpUrl transactions being monitored on the same server. Registering the same Instance twice for the same computer and transaction type will overwrite the details of the previous registration.
  7. Enter a regular expression for the ExpectedContentPattern. This expression should match a pattern in the source code for the page.
  8. Optionally, enter a MeasuredObject for the page. The MeasuredObject is a user defined field that can be used for filtering and sorting events and as a variable in Execute actions.
  9. Click on the Monitor button.
  10. Repeat configuration to monitor additional URLs.
Troubleshooting
  • Registration fails with the url is unavailable: Http access error 404:
    Longitude could not open the requested page. Check the URL and verify that it is available from the Longitude server being used as the agent.
  • Registration fails with Url content did not match error:
    Verify the string described in the regular expression is on the web page. In most cases you will need to place a .* before and after the regular expression to specify that the string can be found anywhere on the page.
  • Registration fails with Error registering Transaction HttpConnect:
    Try to register an HttpConnect Transaction for the web server specified in the URL. If this registration fails, contact Longitude Support at support@heroix.com for assitance in registering the HttpUrl transaction without an HttpConnect transaction.
NNTP Transaction
The NNTP transaction enables you to test whether an NNTP server is accessible and able to reply with a list of newsgroups.
Collection Methods NNTP
Requirements The NNTP transaction also registers a Port Transaction for the specified NNTP port. If the NNTP transaction fails to retrieve a list of newsgroups from the server, but the Port transaction determines that it cannot connect to the NNTP port, an event will be created that the NNTP port on the server is unreachable, rather than that the NNTP server is failing to reply with a list of newsgroups.
Configuration
  1. Use Monitor Devices.
  2. Select Transaction.
  3. Select NNTP.
  4. If necessary, select a Longitude Remote Agent.
  5. Enter the name of the NNTP Server in the Computers field.
  6. The Instance value is used by Longitude to distinguish between different FTP transactions being monitored on the same server. Registering the same Instance twice for the same computer and transaction type will overwrite the details of the previous registration.
  7. Enter the Port used by the NNTP Server. The default port is 119.
  8. Click on the Monitor button.
  9. Repeat configuration to monitor additional FTP servers.
Ping Transaction
The Ping transaction enables you to test for a response to echo requests.
Collection Methods ICMP Ping, TCP Port Echo
Requirements
  • Ping packets must be allowed through any firewall between the Longitude server and the server or device being pinged.
  • Longitude uses ICMP packets for ping tests.
  • Ping transactions have a 5 minute interval.
  • By default, any server or network device monitored by the Unix, Windows, or NetworkDevice application will also
    have a Ping transaction registered to it.
Configuration
  1. Use Monitor Devices.
  2. Select Transaction.
  3. Select Ping.
  4. If necessary, select a Longitude Remote Agent.
  5. Enter the name of the Server or Network Device in the Computers field.
  6. The Instance value is used by Longitude to distinguish between different Ping transactions being monitored on the same server. Registering the same Instance twice for the same computer and transaction type will overwrite the details of the previous registration.
  7. Click on the Monitor button.
Ping Critical Transaction
The PingCritical transaction enables you to test for a response to echo requests at a more frequent interval than the default Ping transaction. The PingCritical transaction is tested on a one minute interval, while the Ping transaction is tested on a 5 minute interval. The PingCritical transaction is recommended for monitoring critical servers, so that you are notified more quickly when they become unreachable. For less critical servers the Ping transaction is recommended because it will reduce the amount of unnecessary data that is collected and reduce the workload on the Longitude components.
Collection Methods ICMP Ping, TCP Port Echo
Requirements
  • If there is a firewall between the statistics server and the target, incoming echo requests must not be blocked.
  • Longitude uses ICMP packets for ping tests.
  • By default, any server or network device monitored by the Unix, Windows, or NetworkDevice application will also
    have a Ping transaction registered to it. It is recommended that Ping and PingCritical are not used for the same
    computer or network device.
Configuration
  1. Use Monitor Devices.
  2. Select Transaction.
  3. Select PingCritical.
  4. If necessary, select a Longitude Remote Agent.
  5. Enter the name of the Server or Network Device in the Computers field.
  6. The Instance value is used by Longitude to distinguish between different PingCritical transactions being monitored on the same server. Registering the same Instance twice for the same computer and transaction type will overwrite the details of the previous registration.
  7. Click on the Monitor button.
Port Transaction
The Port transaction enables you to test whether a connection can be made to a port.
Collection Methods Port Check
Requirements None
Configuration
  1. Use Monitor Devices.
  2. Select Transaction.
  3. Select Port.
  4. If necessary, select a Longitude Remote Agent.
  5. Enter the name of the Server or Network Device in the Computers field.
  6. The Instance value is used by Longitude to distinguish between different Port transactions being monitored on the same server. Registering the same Instance twice for the same computer and transaction type will overwrite the details of the previous registration.
  7. Enter the Port to be monitored.
  8. Optionally, enter a MeasuredObject for the port. The MeasuredObject is a user defined field that can be used for filtering and sorting events and as a variable in Execute actions.
  9. Click on the Monitor button.
Service Transaction
The Service transaction enables you to test whether a particular service is running. The Longitude Windows application monitors services that are set to a start mode of ‘Auto’, ‘Boot’ or ‘System’, and the Longitude Exchange, IIS and SQL applications will also monitor application specific services. The Service Transaction may be used to monitor additional services, or to set up alerts that include a Cleared update when the service is back online.
Collection Methods WMI
Requirements
  • Longitude Statistics Server account must have local administrator privileges on the server being monitored.
  • The Windows Management Instrumentation service must be running on the server being monitored.
Configuration
  1. Use Monitor Devices.
  2. Select Transaction.
  3. Select Service.
  4. If necessary, select a Longitude Remote Agent.
  5. Enter the name of the Server in the Computers field.
  6. The Instance value is used by Longitude to distinguish between different Service transactions being monitored on the same server. Registering the same Instance twice for the same computer and transaction type will overwrite the details of the previous registration.
  7. Select the ColumnName used to specify the service. The DisplayName is the user friendly name for the service, and the Name is the service name as specified for the service in the registry. Both DisplayName and Name can be found in the Services applet in the General tab for the service properties.
  8. Enter the Name for the service.
  9. Optionally, enter a MeasuredObject for the Service transaction. The MeasuredObject is a user defined field that can be used for filtering and sorting events and as a variable in Execute actions. If a net start action will be used to restart the service, it is recommended that the MeasuredObject be set to the service Name.
  10. Click on the Monitor button.
SMTP Transaction
The SMTP transaction enables you to test whether a connection can be made to an SMTP server.
Collection Methods SMTP
Requirements None
Configuration
  1. Use Monitor Devices.
  2. Select Transaction.
  3. Select SMTP.
  4. If necessary, select a Longitude Remote Agent.
  5. Enter the name of the Server in the Computers field.
  6. The Instance value is used by Longitude to distinguish between different SMTP transactions being monitored on the same server. Registering the same Instance twice for the same computer and transaction type will overwrite the details of the previous registration.
  7. Select the Port used by the SMTP server. The default value is 25.
  8. Click on the Monitor button.
SQL Connect Transaction
The SQLConnect transaction enables you to test whether a connection can be made to a database server.
Collection Methods JDBC
Requirements
  • Longitude includes JDBC drivers for the following databases:
    • MySQL
    • Oracle
    • MS SQL 2000 and higher
  • DB2 and Sybase are listed as options under Vendor in SQLConnect’s Application Properties. Selecting these options will configure the DatabaseURL in the correct format, but the drivers for DB2 and Sybase are not installed by default.
  • You may install additional drivers using the following steps:
    1. Obtain a JDBC driver from the database vendor
    2. Copy the driver to the Longitude\lib\ext directory on any Longitude server using the driver for collections
    3. Restart the Longitude Statistics Server Service
  • Longitude will configure the JDBC connection to use the database’s default port. If the database is using a nonstandard port, configure the Port in the Application Properties appropriately.
  • If you are monitoring MS SQL databases using integrated authentication, the Longitude Statistics Server Service account must have permission to connect to the database. If the account is a local administrator account on the SQL server, or a domain administrator account, it will have permission to connect to the database by default.
  • For MS SQL not using integrated authentication and other database servers, you will need a database user account and password.
Configuration
  1. Use Monitor Devices.
  2. Select Transaction.
  3. Select SQLConnect.
  4. If necessary, select a Longitude Remote Agent.
  5. Enter the name of the Database Server in the Computers field.
  6. Select the Vendor – this will populate the Instance, DatabaseDriver, DatabaseURL, and Port fields. If Generic is selected, all configuration information will need to be entered manually.
  7. Enter the DatabaseInstance. This will update the Instance and DatabaseURL. If monitoring a default MS SQL instance, this may be left blank.
  8. The Instance value is used by Longitude to distinguish between different SQLConnect transactions being monitored on the same server. Registering the same Instance twice for the same computer and transaction type will overwrite the details of the previous registration. The field may be changed from the value pre-configured by the application properties values.
  9. Enter the DatabaseUser and DatabasePassword. If monitoring an MS SQL server using integrated authentication, these fields may be left blank. If using a SQL account for MS SQL, update the database URL from integratedSecurity=true to integratedSecurity=false
  10. Check the configuration settings and verify that any values that were automatically populated are correct.
  11. Click on the Monitor button.
SQL Query Transaction
The SQLQuery transaction enables you to test whether a SQL query completes successfully and evaluate the return from the query.
Collection Methods JDBC
Requirements
  • The SQLQuery transaction will also register a SQLConnect transaction. The SQLConnect transaction will run before SQLQuery, and if it fails an event will be created for SQLConnect instead of SQLQuery. The SQLQuery transaction will not run if SQLConnect fails.
  • Longitude includes JDBC drivers for the following databases:
    • MySQL
    • Oracle
    • MS SQL 2000 and higher
  • DB2 and Sybase are listed as options under Vendor in SQLConnect’s Application Properties. Selecting these options will configure the DatabaseURL in the correct format, but the drivers for DB2 and Sybase are not installed by default.
  • You may install additional drivers using the following steps:
    1. Obtain a JDBC driver from the database vendor
    2. Copy the driver to the Longitude\lib\ext directory on any Longitude server using the driver for collections
    3. Restart the Longitude Statistics Server Service
  • Longitude will configure the JDBC connection to use the database’s default port. If the database is using a nonstandard port, configure the Port in the Application Properties appropriately.
  • If you are monitoring MS SQL databases using integrated authentication, the Longitude Statistics Server Service account must have permission to connect to the database. If the account is a local administrator account on the SQL server, or a domain administrator account, it will have permission to connect to the database by default.
  • For MS SQL not using integrated authentication and other database servers, you will need a database user account and password.
  • When entering a ComparisonOperator and ComparisonValue, define the values expected for a successful return.
Configuration
  1. Use Monitor Devices.
  2. Select Transaction.
  3. Select SQLQuery.
  4. If necessary, select a Longitude Remote Agent.
  5. Enter the name of the Database Server in the Computers field.
  6. Select the Vendor – this will populate the Instance, DatabaseDriver, DatabaseURL, and Port fields. If Generic is selected, all configuration information will need to be entered manually.
  7. Enter the DatabaseInstance. This will update the Instance and DatabaseURL. If monitoring a default MS SQL instance, this may be left blank.
  8. The Instance value is used by Longitude to distinguish between different SQLConnect transactions being monitored on the same server. Registering the same Instance twice for the same computer and transaction type will overwrite the details of the previous registration. The field may be changed from the value pre-configured by the application properties values.
  9. Enter the DatabaseUser and DatabasePassword. If monitoring an MS SQL server using integrated authentication, these fields may be left blank. If using a SQL account for MS SQL, update the database URL from integratedSecurity=true to integratedSecurity=false
  10. Check the configuration settings and verify that any values that were automatically populated are correct.
  11. Enter the query to be run against the database. The query should return one or more rows of data, and the first column in the first row must not be NULL.
  12. Optionally, enter a MeasuredObject for the SQLQuery transaction. The MeasuredObject is a user defined field that can be used for filtering and sorting events and as a variable in Execute actions.
  13. Select a ComparisonOperator and enter a ComparisonValue to evaluate the return from the query. See the regular expression and comparison operator notes for details on configuring the comparison. If the configured match succeeds, the transaction will succeed. If the configured match fails, the transaction will fail, and an Critical event will be generated.
  14. Click on the Monitor button.
SSH Transaction
The SSH transaction enables you to test whether an SSH connection can be made to a server.
Collection Methods SSH
Requirements Username and password with permission to log in via SSH.
Configuration
  1. Use Monitor Devices.
  2. Select Transaction.
  3. Select SSH.
  4. If necessary, select a Longitude Remote Agent.
  5. Enter the name of the Server in the Computers field.
  6. Enter a Username with permission to make an SSH connection.
  7. Enter the Password for the Username.
  8. The Port is set to the SSH default port of 22. Change this if necessary.
  9. The Instance value is used by Longitude to distinguish between different SSH transactions being monitored on the same server. Registering the same Instance twice for the same computer and transaction type will overwrite the details of the previous registration. The field may be changed from the value pre-configured by the application properties values.
  10. Click on the Monitor button.
Troubleshooting
  • If the SSH connection is using a port other than 22 and fails to register, restart the Longitude Statistics Server Service and try to register the collection again.
  • If SSH is using port 22 and fails to register, test the SSH connection from the Longitude Server directly using the specified account. Verify that the account can log on and open an interactive shell.
  • On some systems, the root account is blocked from making an SSH connection for security reasons. The SSH Transaction does not require root permission – specify a different user account in the configuration.
Telnet Transaction
The Telnet transaction enables you to test whether an Telnet connection can be made to a server.
Collection Methods Telnet
Requirements
  • Username and password with permission to log in via Telnet.
  • If monitoring Telnet on Windows, the Longitude Server must be on Windows, and the Longitude Statistics Server account must have local administrator privileges on the Telnet Server.
  • Telnet monitoring is only supported for Windows and Unix/Linux servers.
Configuration
  1. Use Monitor Devices.
  2. Select Transaction.
  3. Select Telnet.
  4. If necessary, select a Longitude Remote Agent.
  5. Enter the name of the Server in the Computers field.
  6. Select either Unix or Windows as the Telnet server Platform. If the Telnet server is Linux, select Unix.
  7. Enter a Username with permission to make a Telnet connection.
  8. Enter the Password for the Username.
  9. The Port is set to the Telnet default port of 23. Change this if necessary.
  10. The Instance value is used by Longitude to distinguish between different Telnet transactions being monitored on the same server. Registering the same Instance twice for the same computer and transaction type will overwrite the details of the previous registration. The field may be changed from the value pre-configured by the application properties values.
  11. Click on the Monitor button.
Troubleshooting On some systems, the root account is blocked from making a Telnet connection for security reasons. The Telnet Transaction does not require root permission – specify a different user account in the configuration.
UnixConnect Transaction
The UnixConnect transaction enables you to test whether a connection can be made to a Unix/Linux server using either SSH or rexec. It also allows the connection to be made using public-key authentication, if desired.
Collection Methods SSH or rexec
Requirements
  • Username and password with permission to log in via either SSH or rexec.
  • Password authentication is attempted first. If password authentication fails, public-key authentication is attempted.
  • If there is a password expiration policy for Unix, it is recommended that the account used to monitor Unix either be exempted from that policy, or that the account use public-key authentication.
  • Instructions on configuring Longitude for public-key authentication can be found in Configuring public-key authentication for SSH based collections.
  • The SSH connection is attempted first. If that fails, an rexec connection is attempted.
Configuration
  1. Use Monitor Devices.
  2. Select Transaction.
  3. Select UnixConnect.
  4. If necessary, select a Longitude Remote Agent.
  5. Enter the name of the Server in the Computers field.
  6. Enter a Username with permission to make an SSH or rexec connection.
  7. Enter the Password for the Username.
  8. The SshPort is set to the SSH default port of 22. Change this if necessary.
  9. If public-key authentication is being used, select the SshPrivateKey configured for the specified account. If password authentication is used, this field will be ignored.
  10. The Instance value is used by Longitude to distinguish between different UnixConenct transactions being monitored on the same server. Registering the same Instance twice for the same computer and transaction type will overwrite the details of the previous registration. The field may be changed from the value pre-configured by the application properties values.
  11. Click on the Monitor button.
Troubleshooting On some systems, the root account is blocked from making an SSH or rexec connection for security reasons. The UnixConnect Transaction does not require root permission – specify a different user account in the configuration.
UnixProcess Transaction
The UnixProcess transaction enables you to test whether a particular process exists on a Unix or Linux computer. A Critical severity event will be generated for each interval the process is not found on the monitored server, followed by one Cleared severity event when the process restarts.
Collection Methods SSH or rexec
Requirements
  • Username and password with permission to log in via either SSH or rexec.
  • Password authentication is attempted first. If password authentication fails, public-key authentication is attempted.
  • If there is a password expiration policy for Unix, it is recommended that the account used to monitor Unix either be exempted from that policy, or that the account use public-key authentication.
  • Instructions on configuring Longitude for public-key authentication can be found in Configuring public-key authentication for SSH based collections.
  • The root account is not needed for this collection. The specified user account should have permission to run the command: ps -eo pid,args
  • The name configured for the process will be checked against the output from ps -eo pid,args. The configured process name should be case sensitive, should be unique enough to select only the desired process, should not use wildcards, and can include spaces.
  • A UnixConnect transaction will be registered in addition to the UnixProcess collection. If the UnixConnect
    transaction fails, an event will be created for that, and the UnixProcess collection will not be exected.
Configuration
  1. Use Monitor Devices.
  2. Select Transaction.
  3. Select UnixProcess.
  4. If necessary, select a Longitude Remote Agent.
  5. Enter the name of the Server in the Computers field.
  6. Enter the Name of a process to be monitored.
  7. Enter a Username.
  8. Enter the Password for the Username. If this field is left blank, public-key authentication will be tried.
  9. The SshPort is set to the SSH default port of 22. Change this if necessary.
  10. If public-key authentication is being used, select the SshPrivateKey configured for the specified account. If password authentication is used, this field will be ignored.
  11. Optionally, enter a MeasuredObject for the UnixProcess transaction. The MeasuredObject is a user defined field that can be used for filtering and sorting events and as a variable in Execute actions.
  12. The Instance value is used by Longitude to distinguish between different UnixProcess transactions being monitored on the same server. Registering the same Instance twice for the same computer and transaction type will overwrite the details of the previous registration. The field may be changed from the value pre-configured by the application properties values.
  13. Click on the Monitor button.
Troubleshooting On some systems, the root account is blocked from making an SSH or rexec connection for security reasons. The UnixProcess Transaction does not require root permission – specify a different user account in the configuration.
UnixScript Transaction
The UnixScript transaction enables you to evaluate the output of a script or command on a Unix or Linux server.
Collection Methods SSH or rexec
Requirements
  • Username and password with permission to log in via either SSH or rexec.
  • Password authentication is attempted first. If password authentication fails, public-key authentication is attempted.
  • If there is a password expiration policy for Unix, it is recommended that the account used to monitor Unix either be exempted from that policy, or that the account use public-key authentication.
  • Instructions on configuring Longitude for public-key authentication can be found in Configuring public-key authentication for SSH based collections.
  • The account specified should have permission to run the command or script specified.
  • If a script is specified, it should already exist on the Unix/Linux server, and should be specified with a
    full path.
Configuration
  1. Use Monitor Devices.
  2. Select Transaction.
  3. Select UnixScript.
  4. If necessary, select a Longitude Remote Agent.
  5. Enter the name of the Server in the Computers field.
  6. Enter a Username.
  7. Enter the Password for the Username. If this field is left blank, public-key authentication will be tried.
  8. The SshPort is set to the SSH default port of 22. Change this if necessary.
  9. If public-key authentication is being used, select the SshPrivateKey configured for the specified account. If password authentication is used, this field will be ignored.
  10. Enter the Command the transaction will run. Use the full path, and verify that the specified Username has permission to run the command.
  11. Select a ComparisonOperator and enter a ComparisonValue to evaluate the return from the Command. See the regular expression and comparison operator notes for details on configuring the comparison. If the configured match succeeds, the transaction will succeed. If the configured match fails, the transaction will fail, and a Critical event will be generated.
  12. The Instance value is used by Longitude to distinguish between different UnixProcess transactions being monitored on the same server. Registering the same Instance twice for the same computer and transaction type will overwrite the details of the previous registration. The field may be changed from the value pre-configured by the application properties values.
  13. Click on the Monitor button.
Troubleshooting On some systems, the root account is blocked from making an SSH or rexec connection for security reasons. If root permission is required to run the script, configure public key authentication or SSH access for root.
WinProcess Transaction
The WinProcess transaction enables you to test whether a specified process exists on a Windows computer. A Critical severity event will be generated for each interval the process is not found on the monitored server, followed by one Cleared severity event when the process restarts.
Collection Methods WMI
Requirements
  • The account used for the Longitude Statistics Server service should have local administrator permission on the Windows server.
  • The Windows Management Instrumentation service should be running on the monitored server.
  • The process name is not case senstive, and does not allow for wildcards. The process name should match the full name of the process, without a .exe extension. For example, the Print Server would be monitored with process name “spoolsv” instead of “spoolsv.exe”.
  • A WMIConnect transaction will be registered in addition to the WinProcess collection. If the WMIConnect transaction
    fails, an event will be created for that, and the WinProcess collection will not be executed.
Configuration
  1. Use Monitor Devices.
  2. Select Transaction.
  3. Select WinProcess.
  4. If necessary, select a Longitude Remote Agent.
  5. Enter the name of the Server in the Computers field.
  6. Enter the Name of a process to be monitored.
  7. Optionally, enter a MeasuredObject for the WinProcess transaction. The MeasuredObject is a user defined field that can be used for filtering and sorting events and as a variable in Execute actions.
  8. The Instance value is used by Longitude to distinguish between different WinProcess transactions being monitored on the same server. Registering the same Instance twice for the same computer and transaction type will overwrite the details of the previous registration. The field may be changed from the value pre-configured by the application properties values.
  9. Click on the Monitor button.
WinScript Transaction
The WinScript transaction enables you to monitor the output of a script run from a Windows Longitude server.
Collection Methods WMIC
Requirements
  • The Computer selected for the WinScript transaction does not run the script, but will be listed as the source of any events generated by the WinScript transaction. The Longitude agent assigned to the computer configured for the WinScript transaction will run the script. The name of the computer may be passed to the script using the variable {MANAGEDDEVICE}.
  • The script should exist on the Windows Longitude Server. If the script is in the Longitude directory, it may be called with a path relative to the Longitude root directory, otherwise the script location should be specified by a full path.
  • Interactive scripts (e.g. FTP login scripts) are not supported.
  • Scripts may use any scripting language installed on the Longitude server – e.g. VBScript, Perl, Python, etc.
  • Scripts support UNC paths as arguments. The account assigned to the Statistics Server Service should have permission to access any UNC path specified in the script.
Configuration
  1. Use Monitor Devices.
  2. Select Transaction.
  3. Select WinScript.
  4. If necessary, select a Longitude Remote Agent.
  5. Enter the name of the Server in the Computers field.
  6. Enter the path to the script on the Longitude server in the Command field.
  7. Select a ComparisonOperator and enter a ComparisonValue to evaluate the return from the Command. See the regular expression and comparison operator notes for details on configuring the comparison. If the configured match succeeds, the transaction will succeed. If the configured match fails, the transaction will fail, and an Critical event will be generated.
  8. The Instance value is used by Longitude to distinguish between different WinScript transactions being monitored on the same server. Registering the same Instance twice for the same computer and transaction type will overwrite the details of the previous registration. The field may be changed from the value pre-configured by the application properties values.
  9. Click on the Monitor button.
Troubleshooting
  • Registration fails with The system cannot find the file specified error:
    The Longitude server assigned to the Computer was not able to find the command specified. Check that the agent used for the Computer has the file in the correct path.
WinShare Transaction
The WinShare transaction tests whether a Windows share exists.
Collection Methods WMI
Requirements
  • The Statistics Server Account on the Longitude server should have administrative privileges on the computer hosting the share.
  • The Windows Management Instrumentation Service should be running on the computer hosting the share.
  • The name of the share should be specified using the share name as it appears in the Sharing tab of the folder’s property sheet.
  • If the share name include a single quote, it should be escaped with a backslash – e.g. admin\’s folder.
  • The share name is not case sensitive
  • The Longitude Statsitics Server account does not need permission to access the share, it uses WMI to test for the existence of the share.
  • A WMIConnect transaction will be registered in addition to the WinShare collection. If the WMIConnect transaction
    fails, an event will be created for that, and the WinShare collection will not be exected.
Configuration
  1. Use Monitor Devices.
  2. Select Transaction.
  3. Select WinShare.
  4. If necessary, select a Longitude Remote Agent.
  5. Enter the name of the Server in the Computers field.
  6. Enter the name of the Windows Share in the Name field.
  7. The Instance value is used by Longitude to distinguish between different WinShare transactions being monitored on the same server. Registering the same Instance twice for the same computer and transaction type will overwrite the details of the previous registration. The field may be changed from the value pre-configured by the application properties values.
  8. Click on the Monitor button.
WMIConnect Transaction
The WmiConnect transaction enables you to test whether Longitude can connect to WMI on a computer.
Collection Methods WMI
Requirements
  • The Statistics Server Account on the Longitude server should have administrative privileges on the computer hosting the share.
  • The Windows Management Instrumentation Service should be running on the computer hosting the share.
Configuration
  1. Use Monitor Devices.
  2. Select Transaction.
  3. Select WMIConnect.
  4. If necessary, select a Longitude Remote Agent.
  5. The Instance value is used by Longitude to distinguish between different WinShare transactions being monitored on the same server. Registering the same Instance twice for the same computer and transaction type will overwrite the details of the previous registration. The field may be changed from the value pre-configured by the application properties values.
  6. Click on the Monitor button.

 

Unix

Supported Versions
OS Versions
RedHat Linux 9, AS 3.0, RHEL 3 +
SuSE Linux 8.2 +
Sun Solaris 8, 9, 10, 11
HP-UX 11, 11i
AIX 4.3.3, 5.1, 5.2, 5.3,6.1,7.1,7.2
Collection Methods SSH or rexec
Requirements
  • Username and password with permission to log in via either SSH or rexec.
  • Password authentication is attempted first. If password authentication fails, public-key authentication is attempted.
  • If there is a password expiration policy for Unix, it is recommended that the account used to monitor Unix either be exempted from that policy, or that the account use public-key authentication.
  • Instructions on configuring Longitude for public-key authentication can be found in Configuring public-key authentication for SSH based collections.
  • On Linux servers, the sysstat package should be installed to provide the OS commands used to collect data.
  • The account specified should have permission to run the following commands:
    Platform Commands
    AIX iostat, ps, df, vmstat, lsattr, lsps, netstat
    HP-UX iostat, ps, df, vmstat, swapinfo, netstat, “grep Physical /var/adm/syslog/syslog.log”
    Linux iostat, ps, df, sar, free, ip
    Solaris iostat, ps, df, sar, prtconf, vmstat, swap, netstat
Configuration
  1. Use Monitor Devices or see the Unix instructions for Device Discovery.
  2. Select Unix.
  3. If necessary, select a Longitude Remote Agent.
  4. If monitoring manually, enter the name of the Server in the Computers field.
  5. Enter a Username.
  6. Enter the Password for the Username, the passphrase for public key authentication, or blank for public key authentication without a passphrase.
  7. The SshPort is set to the SSH default port of 22. Change this if necessary.
  8. If public-key authentication is being used, select the SshPrivateKey configured for the specified account. If password authentication is used, this field will be ignored.
  9. Click on the Monitor button.
Troubleshooting
  • On some systems, the root account is blocked from making an SSH or rexec connection for security reasons. The commands Longitude runs to collect data do not require root access – please specify a user account for data collection.
  • AIX servers may require that Longitude server collecting data be in the local /etc/hosts file.
  • SuSE Linux may have password authentication disabled for SSH connections:
    1. Check /etc/ssd/sshd_config for the line: PasswordAuthentication no
    2. Change the line to PasswordAuthentication yes
    3. Restart sshd
  • If memory collections fail during registration for HP-UX:
    • Check that /usr/sbin/swapinfo can be executed by the account used for collections.
    • Check the output from head -n 100 /var/adm/syslog/syslog.log | grep Physical. If this does not contain the total memory on the server, contact Longitude support at support@heroix.com for additional options on collecting the total memory for HP-UX servers.
  • -1 is returned for collections:
    Some collections are not supported on all platforms, and will return a default value of -1. The following collections are not supported:

    Platform Collector Collection
    AIX Memory SWAP_OUT_RATE
    AIX Processor RUNNABLE_PROCESSES
    Linux Memory PAGE_SCAN_RATE
  •  

  • Linux MEM_FREE_PCT is higher than expected:
    Longitude’s value for MEM_FREE_PCT on Linux is calculated to include the amount of free memory in the cache. Longitude runs the free -k command and uses the memory listed on the -/+ buffers/cache: line. This line displays all the memory that is usable, regardless of whether or not if has been allocated. The top line of the free -k output displays allocated memory, some of which may be cached and still available for processes.