User Guide Contents

This User Guide provides detailed instructions for configuring and using Longitude v10.0. The “quick start” steps for implementing Longitude are available in the Longitude Quick Start Guide. Additional resources are available in the Longitude Video Tutorials. If you experience any problems installing or configuring Longitude, please contact Heroix support by email at:

Port Requirements Ports required to use Longitude
Permissions Permissions needed to monitor servers
License Types Different License Types
Data Collection
Discover Devices Scan subnets to automatically detect and monitor Windows, Unix, and Network devices
Monitor Devices Set up monitoring for devices without using discovery
Remote Agents Install and use a Longitude Remote Agent
Collection Status Detect if there are problems collecting monitoring data
User Defined Groups User defined groups of monitored computers
Collection Management Modifying, Removing, or Suspending Application Monitoring
Mail Configuration Change SMTP settings for Longitude
User Accounts Add and Modify Longitude User accounts
Component Status View status of Longitude components
Upgrade Download and apply Longitude upgrade patches
Events and Alerts
Status Dashboard Graphic overview of detected performance events
View Events Detail listing of detected performance events
Suppressing Events Temporarily disabling performance events.
Disabling Events Permanently disabling performance events
Configure Events Adjust thresholds for events and configure alerts
Performance Reports Longitude performance metric reporting
Virtualization Reports Hyper-V and VMware host and VM reporting
VMware Capacity Planning VMware capacity planning and “What If” analysis
Report Scheduler Automated report generation and distribution
Real Time Monitor Real time display of Key Performance Indicators



For a step by process on how the installation works please take a look at our Quick Start Guide.

Here is some additional configuration information:


Port Requirements

The Longitude Management Console requires network access for the protocols used for data collection. For example, Network Device collections require UDP access to SNMP (default port = 161), and Unix collections require access to SSH (default port = 22). WMI data collection from Windows computers requires RPC, which assigns a random, high numbered port to the WMI connection – as a result, firewalls often block RPC connections by default.

Any applications which require a connection to a specified port will include the port number as part of the configuration information – see Application help for details on specific applications.

In addition to the ports needed for data collection, Longitude uses the following ports:

Port Use
7220 Statistics Server Component Port; if a Remote Agent is behind a firewall, this port will need to be opened to the Longitude Management Console.
7221 Consolidator Component on Longitude Management Console. External access not required.
7222 Engine Component on Longitude Management Console. External access not required.
7223 SSL communication from Management Console to Remote Agent statistics collection service.
7228 Longitude Web UI HTTP port.
7229 Upgrade Manager Component Port; if a Remote Agent is behind a firewall, this port will need to be opened to the Longitude Management Console
7238 Longitude Web UI HTTPS port.



Longitude collects data without the need to install a Longitude agent on the monitored computers or network devices, but Longitude will require permission to connect to the devices it is monitoring. Please make sure you have the following information available before trying to monitor devices with Longitude:

Device Type Method Permissions Needed
Windows WMI Windows account with local Administrator
privileges on target device*
Unix/Linux SSH Unix user account with SSH connection privileges
Network Devices SNMP SNMP V1 Community string with read privileges

* Longitude is designed to operate in a Windows domain for the purpose of WMI data collection. If Longitude is installed in a workgroup, it will be able to collect WMI data only for the Longitude Management Console server itself. To collect WMI data for additional machines, see the Troubleshooting article “Longitude installed on a Workgroup computer”.

Some applications require further configuration – please refer to Application Help for further details.


License Types

Longitude has the following types of license units:

  • Base:
    One unit required per monitored device. Allows monitoring for Windows, WindowsEventLog, Unix, or NetworkDevice.
  • Layered Application:
    Allows use on a monitored device of predefined Longitude software
    application monitors, e.g. Exchange2010, SQL2012, IIS.
  • VMware CPU Sockets and Hyper-V CPU Sockets:
    The Longitude Virtualization application is licensed by the number of CPU sockets in either the VMware or Hyper-V environment. VMware socket licenses cannot be applied to the Hyper-V application, and Hyper-V socket licenses cannot be applied to the VMware application. Please contact Heroix Support ( to convert between VMware and Hyper-V socket licenses.
  • Transaction:
    Transactions are connectivity tests for basic protocols, e.g. Ping, SSH, SMTP.


Data Collection

How Longitude Collects Data

After installation, the Longitude Management Console must be configured to collect data for the devices and applications in your environment. After the data has been collected, it is analyzed for performance problems, and archived for use in reports. The sequence of events for monitoring an application is:

  1. Select an Application to monitor (e.g. Unix, SQL2014, Ping Transaction).
  2. Select a Remote Agent, if needed. If no agent is selected, data will be collected by the Longitude Management Console.
  3. Select the Computer or Network device to be monitored.
  4. Click on the Monitor button to begin monitoring.
  5. Scheduled data collections will be done either by the Management Console or the Remote Agent.
  6. After the data has been collected, it will be written to the database on the Management Console computer and will be available for reports.
  7. New records in the database are checked against application rules. If any problems are found (e.g. CPU usage is too high, disk space is too low), an Event will be created in the Longitude Dashboard.
  8. If Actions have been configured for the Event, they will be run. For example, sending email or an SMS message.


Configuring Data Collections

Data collection for any application can be configured manually, or data collection for Windows, Unix or Network Devices can be configured using the Discovery wizard to browse your network.

The following components in Longitude’s Web UI are used to configure data collections:


Discover Devices

The initial steps to set up data collection can be automated through Discovery. Using the Discover Wizard, Longitude can scan a specified subnet for Windows or Unix servers, or Network Devices. The Discover button in the upper left of the Monitoring tab will launch the Wizard.

  1. Select the application to be monitored (Windows, Unix or Network Device).
  2. Select IP Address to start scan
  3. Select IP Address to end scan (note: you can only scan one class C subnet at a time)
  4. Provide requested application properties:
    • Windows:
      No additional properties are needed for Windows. The permissions for the Windows account specified during install will be used to collect data.
    • Unix/Linux:
      Enter a Username and Password that can connect to the servers via SSH. Root access is not required. The default SSH port is 22 and may be modified.
    • Network Device:Enter an SNMP V1 community string – only read access is required. The default SNMP port is 161 and may be modified.
      Please note: Network device discovery uses SNMP V1. For SNMP V2 network monitoring, see details for the Network Device application.
  5. Click Next
  6. When Longitude has finished scanning the requested IP range, you will be presented with a list of computers or network devices that can be monitored with the selected application:
    Select the devices you would like to monitor. You will be able to monitor devices up to the number of license units you have available.
  7. Click Next
  8. The final discovery step will display the monitoring
    results, including any monitoring errors:
    If there are any errors reported, you can click on the error link to determine the cause of the monitoring error and how to remedy the problem.
  9. After you click Done, you will see the additional computers you are monitoring:


Monitor Devices


  1. Click the Monitor button in the upper left of the Web UI to open the Monitor an Application Window
  2. Select the application to monitor from the drop down list.
    Select application from drop down list
  3. When you select an application, the configuration screen may display an Application Properties section which will contain fields for additional information needed to monitor the application.
    • Further details on specific information needed for each application can be found in the Application help section.
    • Fields marked with a red asterisk (*) are required.
    • Hovering over the information icon to the right of a property field will display details about the property configuration.

    Monitor VMware

  4. Either manually enter the computer to monitor in the Computers field, or select the button to the right of the Computers button to display of list of computers you are already monitoring.
    Computer selection
  5. Click on the Monitor button. Longitude will test data collection for the application using the supplied Application Properties, and a result window will display either that the collections succeeded, or list any errors that were found.
    Monitoring results


Remote Agents

Data collection from the Longitude Management Console may have the following limitations:

  • WMI collections have one specific set of credentials, which may not work in all Windows domains
  • Firewalls may block ports needed for data collection
  • Slow links may cause collection requests to timeout
  • Connectivity may need to be tested over a different network route
  • For large networks, it may be more efficient to spread the load of data collection over multiple agents.

A Longitude Remote Agent can be used to collect data from a different network location, or with a different set of Windows credentials. The Remote Agent does not install the database or web server components used for the Management Console, and does not require a dedicated server.

The recommended operating system and hardware for an agent is:

  • Server OS:
    • Windows 2008 Server
    • Windows 2012 Server
    • Windows 2016 Server
  • 2+ GHz processor
  • 4 GB memory
  • 60 – 95 MB free disk space, depending on installed collectors


Longitude Remote Agent installation kits are available for download. Please email Heroix Support for download instructions.


The steps to configure data collection with an agent are:

  1. Install the Longitude Remote Agent software on the target computer.
  2. If a firewall is in place between the Longitude Management Console and the Remote agent, verify that TCP ports 7220 and 7229 are open from the Management Console to the Remote agent.
  3. Click the Monitor button in the upper left of the Web UI to open the Monitor an Application Window.
  4. Click on the New Remote Agent button in the lower left of the Application Monitoring window.
    Create New Remote Agent
  5. Enter the name or IP address of the Remote Agent in the blank New Agent field, and click the Test Remote Agent button to verify that the Longitude Management Console can connect to the Remote Agent.
  6. Enter in the remaining application monitoring details for the collection.
  7. Click Apply.
  8. After a Remote Agent has been entered, a new Agent field will be listed in the Application Monitoring Window – this will allow you to select the agent to be used for data collection.
    Multiple agent display
  9. The status screen will list which agent is collecting data for which computer. Only one agent can be assigned to a computer at a time. To change agents for a computer, remove all monitoring for that computer, and then re-add the monitoring using the new agent.
    Multiple collection agents
  10. After a Remote Agent has been added, the Discovery wizard will add an Agent selection field which will allow you to discover servers using the Remote Agent.
    Discovery using agent


Collection Status

When you monitor an application on a computer or device, one or more collections are performed. The status of these collections is displayed on the Monitoring tab. The Computers tab displays an alphabetical list of all devices being monitored, the Applications tab groups collections by Application monitored, and the Groups tab displays devices in user defined groups.

Collection Status

The color of the icons in the tree indicates the collection status:

Green All collections are successful
Yellow Some non-critical collections have failed
Red Some or all collections have failed

If an icon in the status display is red or yellow, you can drill down to the specific collection that is failing, and use the details in the Messages field to diagnose the problem. When the condition causing the collection error is fixed and Longitude is able to successfully run a scheduled collection, the status icon’s color will be set to green. The Test/Retry buttons can be used to update the status icons manually, or to refresh the text in the Messages field.


Display Transactions

Transaction Display

Display Transactions will open an Enterprise level view of Transactions monitored over all devices. This option is available by clicking on Monitoring >> Computers, Applications, or Groups >> Enterprise .

Transaction Display


User Defined Groups

The Computers and Applications tabs are automatically populated based on the applications Longitude has been configured to monitor. The Groups tab can be used to organize computers and other managed devices into user defined Computer Groups with the following features:

  • Computer Groups may be used to do the following:
    • Monitoring – Groups: View collection status by group
    • Dashboard – Status: Configure status dashboards by group
    • Dashboard – Events: View Events by computer group
    • Dashboard – Configure >> select Rule >> Actions:
      Configure alert actions by group
    • Dashboard – Configure >> select Rule >> Suppression:
      Suppress events by group
    • Dashboard – Configure >> select Rule >> Thresholds:
      Change rule thresholds by group
    • Reports – Groups: View reports by group
    • Reports – Scheduler: Schedule reports by group
  • Dashboards, actions, suppressions and scheduled reports will be dynamically updated if the computers in a group are changed. Thresholds will not be updated if the membership of a group changes.
  • Computer group definitions are user account specific. Administrators can copy their groups to other users which will overwrite that user’s existing groups.
  • All computers start in the Default group. The Default group cannot be deleted. Computers will return to the default group if they have been removed from all the the existing groups.
  • Computers can belong to multiple groups. Please note: Computers could only be assigned to one group in previous Longitude versions.
  • Groups can be configured in the Monitoring – Groups and Dashboard – Events – Groups tabs:
    • Right-click on an existing group, or on the Enterprise icon at the top of the group list. The Group Management menu will provide options to Create a new group, Manage this group, or Remove this group.Manage Group Options
    • Selecting Create a new group… opens a form with a field for the new group name, an alphabetized list of all computers in the left pane, and a list of computers in the group in the right pane. Mark the box next to the computers to be moved and then click on the Add>> or <<Remove buttons to update the list of computers in the new group.
      Manage Group Options
    • Selecting Manage this group… opens a form that will allow you to add or remove servers from the group for which the option was selected. Mark the box next to the computers to be moved and then click on the Add>> or <<Remove buttons to update the list of computers in the selected group.
      Manage Group Options
    • Selecting the Remove this group… option will delete the group. If a computer is a member of only one group and that group is deleted, then that computer will be moved back in to the Default group
    • To copy groups to other users, right-click on the Enterprise icon at the top of the Groups list in the Monitoring – Groups or Dashboard – Events – Groups tabs and select Copy groups to other users:

      First step copy groups

    • Select the users who will receive a copy of your groups. Please note that all your groups will be copied and will overwrite all existing groups for the target users.

      Second step copy groups


Collection Management

Collection management provides the ability to modify application properties, to remove applications from computers, or to suspend or resume monitoring for all applications on a computer.


Modify Application Properties

Some Longitude applications require that Application Properties be configured in order to collect data. For example, the Username and Password or SSHKey information
for Unix based collections, or the Database Instance for MS SQL Server collections. These properties may be modified for existing collections using the Modify Properties of this application in this computer menu item, available by clicking on an application listed under a computer in the Monitoring >> Computers tab,

Modify properties by computer tab

or by clicking on a computer listed under an application in the Monitoring >> Applications tab.

Modify properties by application tab

Modify Properties of this application in this computer will only modify the properties for one application on one computer. To modify all the properties for an application across multiple computers use Monitor Devices to reconfigure monitoring.

Please note that data collection for an application will be re-tested after the application’s properties are updated. If the data collection fails, application monitoring will be removed.


Remove Applications

Please note that you will be asked to confirm that you want to remove monitoring before the change is applied since removing monitoring for an application will delete all historical data for the application on the selected computer.

Application monitoring may be removed for all applications on a computer, for an individual application on a computer, or for all instances of an application across all computers.

  • Clicking on a computer in the Monitoring >> Computers or Monitoring >> Groups tab provides the option to Remove monitoring of all applications from this computer.
    Remove all applications on a computer
  • If you expand the monitored application list under a computer and click on an application, you can select to Remove monitoring of this application from this computer.
    Remove one application on a computer
  • If you select an application that supports instances (e.g. Transactions or Database applications), clicking on the application will provide the option to Remove monitoring of all instances of this application for this computer.
    Remove all instances of an application
  • Expanding the list of instances under an application provides the option to Remove monitoring of this application instance from this computer.
    Remove all instances of an application
  • Clicking on an application in the Monitoring >> Applications tab provides the option to Remove monitoring of this application from all computers.
    Remove all applications on a computer
  • Expanding the list of computers under an application provides the option to Remove monitoring of this application from this computers.
    Remove one application on a computer


Suspend or Resume Monitoring

If a computer is temporarily unavailable, all the collections for that computer should be suspended to prevent false alerts and to prevent data collection timeouts from using excess resources. Suspending collections will temporarily halt data collection for all applications on a computer, but will not delete previously collected data for the computer. Collections can be resumed when the computer is available again without the need to
reconfigure any properties or groups for the computer.

In Monitoring computers that are suspended will be displayed with a blue icon, and computers that are being monitored will have green, yellow or red icons:

Suspended computer Suspended
Monitored computer Monitored – no collection failures
Collection non-critical failures Monitored – non-critical collection failures
Collection critical failures Monitored – critical collection failures

To suspend or resume monitoring on an individual computer, click on the computer in the Monitor >> Computers or Groups tab.

  • To suspend monitoring on a computer on a computer with a green, yellow, or red icon, select Suspend monitoring of applications on this computer.

    suspend monitoring for one computer

  • To resume monitoring on a suspended computer, select Resume monitoring of applications on this computer.

    Resume monitoring for individual computer

  • To suspend or resume monitoring for multiple computers, click on the Enterprise icon in any of the Monitoring tabs and select Suspend or Resume Multiple Computers. Please note all computer icons in this option are blue and do not reflect the computer’s monitoring status.

    suspend monitoring for multiple computers

    • In the Group tab, computer groups may be used to select computers to suspend or resume.
      suspend monitoring by group
    • In the Computer or Applications tabs, computers may be selected individually to suspend or resume.
      suspend monitoring for one computer



The following Longitude Administration tasks are located in the Admin dropdown menu in the upper right of the Web UI:


Mail Configuration

Mail configuration

Longitude defaults to sending mail using a built in SMTP server. Longitude’s internal SMTP server will use DNS to look up the MX record for the domain of mail recipients, and contact the server specified as the MX server for that domain. Depending on your SMTP security settings, the Longitude SMTP server may not be able to send mail to your domain. If the Longitude SMTP server does not work for your domain, Longitude can be configured to send mail through a specified SMTP server. To specify an SMTP server, click on the Specify a mail server check box, and enter your SMTP server’s name or IP address in the Mail server: field. If you need to specify a username to connect to your SMTP server, enter this information in the Mail server user: field.

The default From Address used for Longitude mail is – this may be changed.

Longitude uses the email address provided during installation as the default for all Contact addresses. The Contact addresses are notified when Longitude needs to send out an administrative notification – e.g. if a database maintenance task fails.

The Test mail button will test all the Contact addresses, and can be used to verify that Longitude is able to send mail using either Longitude’s internal SMTP server, or the user specified Mail server, if that has been configured.


User Accounts

List of Longitude users

The Users item in the Admin menu will display a window listing Longitude
Current Users. The initial account created during Longitude installation will be the only account listed on this screen by default. Existing accounts may be edited or deleted in this window, but it is recommended that you do not delete the initial user account.

User accounts may be deleted by clicking on the cancel icon Delete icon or modified by
clicking on the modify icon Modify icon.

Add internal user

Longitude authenticates users internally, independently of Windows, and the default Add a User window will create an internal Longitude account. The Longitude user field is the account name used for login, and the Display name is the name displayed in the upper right of the Web UI.

The Password field for internal Longitude accounts will store the password as an encrypted string within Longitude.

The Optional password hint is available only for internal accounts.

Add AD user

Selecting the Authenticate via Active Directory checkbox will create a Longitude account which will contact Active Directory for authentication. Active Directory authentication requires at least one Domain controller, and the User name to send to the domain controller. Multiple domain controllers may be entered in a comma separated list.

To log in to Longitude using Active Directory authentication, provide the Longitude user name, and the password for the account listed as the Active Directory User name. The Longitude user can be configured to match the Active Directory User name but it is not required that they match.


Read Only User

Longitude user accounts may be configured with Read Only access by checking the Read only user box in the Add a User or Modify User applets. To configure Groups or Dashboards for Read Only Users, an Admin user will need to create the Group or Dashboard under an Admin account and then copy it to the Read Only User account. Please note that copying Dashboards or Groups will completely overwrite any existing configuration.

Modify user


Component Status

The Component Status window displays the state for the 5 Longitude component services, and the state for the Statistics Server component on any Remote Agents the Management Console is using for collections. The Longitude Components are:

  • Statistics Server
    The Statistics Server corresponds to the Heroix Longitude Statistics Server Service. It is installed on the Management Console and Remote Agents. This service connects to monitored computers and collects data from them – the permissions used for the collections are the permissions for ther Statistics Server service account. This service listens for
    Management Console requests on port 7220.

  • Consolidator
    The Consolidator corresponds to the Heroix Longitude Consolidator Service, and is installed only on the Management Console. This service uses the Local System account and is primarily used for connections to the Longitude database. If a Remote Agent is used, the Consolidator service configures and retrieves data from the Remote Agent.

  • Rule Engine
    This Rule Engine corresponds to the Heroix Longitude Engine Service, uses the Local System account, and is installed only on the Management Console. This service checks the data written to the database for problem conditions based on Application rules. If problems are found, the Rule Engine will create Application Events, and will run any actions configured for Application Events.

  • Web UI
    The Web UI corresponds to the Heroix Longitude Web UI Service, is installed only on the Management Console, uses the Local System account, and runs the Longitude Web UI. This component runs the Web UI on port 7228, or 7238 for HTTPS, and also runs scheduled reports.

  • Upgrade Manager
    The Upgrade Manager corresponds to the Heroix Longitude Upgrade Manager Service, uses the Local System account, and runs on both the Management Console and Remote Agents. The Management Console contacts the Upgrade Manager on a remote agent over port 7229. The upgrade manager checks the Heroix Longitude upgrade URL for new Longitude versions, and can automatically download upgrade patches. The Upgrade Manager also checks the status of other Longitude components, and will email the Contact Address for a component that is not running.



Contact Heroix Support before upgrading.

The Upgrade item in the Admin menu displays the Upgrade Manager Information window, listing the upgrade status for both the Management Console and any Remote Agents.

Upgrade configuration

Click on the edit icon Edit Upgrade Settings Icon to update the Upgrade server, Check Any Time or Check for Upgrade Minutes settings for the Longitude Management Console or any Longitude Remote Agents used by the Management Console.

Upgrade options

The Upgrade Manager component will check the specified URL for Longitude upgrades based on the number of minutes specified in the Check for Upgrade Minutes setting, with a default interval of 1440 minutes (1 day). New patches will be downloaded when they are available and the Upgrade Manager Information screen will be updated to indicate that a new version is available along with an option to run the upgrade. If Check Any Time is set to “no” then Longitude will not check for patches between 9am and 5pm.


Events and Alerts

Longitude checks the data it collects for problem conditions using rules built in to Longitude applications. Each rule applies to a specific component in an application, and checks that component against a condition. For example, the Windows application has a CPU component, and rules check the CPU usage against a threshold. If that threshold is exceeded, an Application Event is created.

The Dashboard >> Events tab displays a sortable and filterable list of all Application Events. The Dashboard >> Status tab displays an overview of Application Events indicating the severity and percentage of effected computers through user configurable pie charts.


Status Dashboard

The Status Dashboard is displayed under the Dashboard >> Status tab. An application overview dashboard is created by default for Windows, Unix, Network Devices, Hyper-V, or VMware when these applications are monitored. The default dashboards display the status for all monitored computers for the application’s key metrics – for example, the Unix dashboard has a pie chart widget for each of CPU, FileSystem, Page Scan Rate and Swap Space. The Dashboard home page displays an overview for all dashboards with each dashboard’s icon displaying the most severe current event status.

Dashboard home page

Clicking on an icon in the dashboard list or on a status icon in the left pane will display the details for the dashboard. In the example below, no problems have been detected for CPU, Page Scan Rate or Swap Space, but 63% of the monitored FileSystems have Critical severity storage space problems and 19% have major severity storage space problems.

Hover over dashboard

Hovering over a widget displays the details of the problems for that section of the widget. In the example above, the detail display was produced by hovering over the Red (i.e. Critical) section of the FileSystem widget.

Right click on event widget

Right-clicking on a widget displays options for displaying detailed metric information:

Problem items only Metrics for Critical and Major problems
All Metrics for all monitored computers
First 25 Metrics for 25 worst performing computers
First 10 Metrics for 10 worst performing computers

Summary event display

The Problem items only report above displays the metrics for computers for which critical or
major severity problems have been detected. Hovering over the data columns lists the value of the metric and any available additional information

Click on the Back button to return to the Widget display.

Existing dashboards can be modified by right-clicking on the dashboard name in the left pane and selecting Modify this dashboard, and new dashboards can be created by right clicking on Enterprise and selecting Create a new dashboard. The Modify Dashboard window will allow you to modify pre-existing widgets, or add in new widgets.

Modify widgets

Adding or editing a widget is done through a widget definition form. Each drop-down menu in the form will be populated based on previous selections. For example, selecting Windows as the Application populates theComponent list with only the components found in the Windows application. Selecting the CPU component restricts the Event list to only Events that are produced for Windows CPU.


The Computer group can be set to either All, or a previously defined Computer Group. If a user defined Computer Group is selected and members are subsequently added to or removed from the Computer Group the computers displayed in the Dashboard will be updated to reflect the change in the Group.


Copy Dashboard

Copy Dashboard

Status Dashboards are user specific. Admin users can copy their own dashboards to other users by right clicking on Enterprise and selecting Copy dashboards to other users…. Please note the following:

  • Copying a dashboard to another user will overwrite existing dashboard definitions.
  • If a dashboard has been configured based on a Computer Group, the Computer Groups will need to be copied as well.
  • Read Only users will only see the default Application overview dashboards until custom dashboards are copied to their account.


View Events

Events are detailed text descriptions of problems detected by Longitude applications. Events can be viewed by selecting Events in the Dashboard tab. The tree display in the left pane can be configured to view applications by Computers, Applications or Groups.

The color of the icon in these trees represents the most severe event
for that computer, application or group:

Icon Highest Event Severity
Green Critical
Yellow Major
Yellow Minor
Red No Events Found

Check or uncheck the box next to the icon to include or exclude events for the computer, application or group. For information on configuring groups, refer to the section on configuring Groups.


Events are listed in the following sections:

Section Events
Application Events Generated by Longitude rules scanning collected data
Windows Event Log Data collected from the Longitude Windows Event Log application
Syslog Data received by Longitude Syslog listener
SNMP Traps Data received by Longitude SNMP Trap listener
SLA Events Events generated by a change in status for a user defined Service Level Agreement

If you are not monitoring these applications, the section will not be displayed. There is no tree display associated with the Syslog, SNMP Trap and SLA Events tabs.


Event Details

Event Monitor

  • The left pane of the Events display contains icons displaying the highest severity event found for the computer.
  • The right pane displays the events found for the servers checked in the left pane – by default the display shows events for the last hour.
  • The Count column is the number of times the event has occurred in the interval being displayed – clicking on the + icon to the left of the Count displays all the events for the interval.
  • Clicking on an Event in the right pane displays the text of the event in the bottom pane.
  • The Windows Event Log, Syslog, and SNMP Traps tabs will only be displayed if these applications are being monitored.


Sorting and Filtering Events

Event Monitor filters

  • Most of the columns in the Event Monitor can be filtered and sorted.
  • Click on the column title to sort by that column.
  • Click on the arrow to the right of a column menu to display additional filtering options.
  • The Columns filter is the same for all columns and allows you to remove columns from the display.
  • Filtering options vary depending on the context of the column, e.g.:
    Event Monitor context filter


Suppressing Events

The Longitude rule engine can be configured to suppress Application Events for specific entities. For example, the Windows application will create events for services which are set to autostart but which are not running – to prevent events from being created for services which are not running for a known reason, the event can be suppressed for up to 48 hours. Please note that suppressing events will only apply to the specific item selected – suppressing n event for one service on a computer will not affect events created for other services on that computer.

For recurring problems, events may be suppressed through configuring a suppression action.


Disabling Events

If a specific event is not needed on a server, and will not be needed in the future, that event can be disabled. Disabled events are configured in the same way that suppressed events are configured, but they do not expire. An event would be disabled for known problems that will not be addressed. For example, low free memory alerts on an MS SQL database server configured to use maximum available memory.

Configure, Suppress and Delete Events Menu

Right-clicking on an event will display the Configure, Suppress and Disable options for the event. Right-clicking anywhere in the Application Events window will display the options to options to configure or view all suppressed or disabled events. The available menu options are:

  • Configure
    Configure will bring you directly to the configure page for thresholds and/or actions for the selected event. See Configure Events for more detail.

  • Suppress this event
    Suppressing an event will prompt you for how long the event should be suppressed. After this period has expired, the event will be created if the problem condition still exists. During this period, data will still be collected, but it will not be checked against application rules. To suppress events for a known computer maintenance window, suspend monitoring of applications to prevent collection timeouts while the server is unavailable.
    Scheduled event suppression may be configured using Configure Suppression in the Configure tab.
  • View all suppressed events
    This option will display a pop up window listing all the events that are currently suspended, and when the suspension expires.
  • Disable this event
    Disabling an event will disable it until it is manually resumed. When you are prompted to disable an event, you will be given the option to disable it for all computers or only for the selected computer. For example, the ServiceDown alert can be disabled for the service you’re viewing either for all computers, or for only the computer in the current event.

  • View all disabled events
    This option will display a pop up window listing all the events that are currently disabled. Right-clicking on an event in this window will allow you to Enable the event again.


Configure Events

With the Configure button depressed, you will be able to:

The Status and Events tabs are linked to the Events pane in the Configure tab, so that an event selected in Events, or a widget selected in Status will be loaded into the Events tree in the Configure tab. Alternately, you can browse through the Events tree to adjust thresholds and actions directly.


Adjusting Thresholds

Configure Thresholds

  • Thresholds can either be a Global Value or an Override Value.
  • The Thresholds tab will display content appropriate to the Event being tailored. For devices with multiple entities (e.g. Disks, Network Interfaces), you will have the option to set Override Values for each individual entity. Some events will have more than one trigger – for example, Unix >> FileSystem >> FileSystemSpaceCritical will alert if the free space is below a specified number of Megabytes, or below a percentage of free space. Status events, such as ping failure or service stopped, will not have thresholds.
  • To change an event’s Global Value threshold, select the event in the left pane, enter a new Global Value on the right, and select Apply.
  • To change an Override Value threshold, enter the value you would like to use in the Override Value field, select the objects that will use this threshold instead of the Global Value, and select Apply.
  • If an Override Value has been set for an object, it will be listed to the right of the object in the Computers tree.
  • Only computers monitored by an application will be displayed, and they are displayed by Computer Group.
  • Override Values are assigned to computers and objects belonging to a computer.
    If a Computer Group is selected, the Override values will be applied to every
    computer in the Group. Moving computers to a different Computer Group will not change Override Values


Configuring Actions

Application Events can trigger alert Actions such as Email or SMS text messages. Each Action can include multiple types of alerts (Email, Text to pager, SMS text to phone, SNMP trap, Execute OS Command) and up to 5 Actions can be created for each Event. After the first Action is configured, a + icon will appear to the right of the Action 1 tab, and allow you to create an additional action.

  1. Click on the Dashboard tab.
  2. Click on the Events button, and select the Event you want to generate an alert.
  3. Click on the Configure button – the Event selected in the previous screen will be selected in this screen. Alternately, if you know which Event you want to alert on, you can browse to the Event in the left pane.
  4. In the right pane, select the Actions button.
  5. Actions can be configured by Computer or by Computer Group. In the right pane, in the Action Filters field, click on the radio button for either Groups or Computers. The default value for both Groups and Computers is *, selecting all Computer Groups or all Computers.
    Computer or Computer Group alert selection

    • Clicking on the expand icon for Computer Groups will present a list of all user defined groups. Computer Groups are user specific, and actions can include groups from multiple users. Selected groups will be displayed as a comma separated list in the format User:Group.

      Expanded list of Groups in alert selection

    • To select specific Computers, click on the expand icon and check the Computers for this Action. Computers may also be entered as a comma separated list.
      Expanded list of Computers in alert selection
    • Either Computer Groups or Computers may be used for an action, not both. To create actions for both Computer Groups and Computers configure an additional action.
    • If a computer is added to or removed from a Computer Group, the actions used for that computer will be updated accordingly. Note that since Computer Groups are user specific, in order to remove an action for a Computer it must be removed from all of the selected user groups.
  6. Some alerts will contain additional Action Filters – for example, filtering for Disk IDs or Processes. These may be left as * to select all.
  7. Select the number of consecutive events to alert on. For example, if you are alerting on a PingCritical Event, which has a 1 minute interval, selecting a count of 3 would delay the alert for 3 minutes, but would eliminate false alerts for intermittent network problems. However, Disk Space rules have a 1 hour interval, so a count of 3 would delay alerts for 3 hours.
  8. Select one or more alert actions, and provide the following additional properties for the selected actions:
    Email Comma separated list of recipients
    Text to pager Pager Provider and Number
    Text to phone Cell Phone Provider and Number
    SNMP Trap Specific Trap Number
    Execute Command to Execute (Windows Computers only)

    Alert displaying all available actions

  9. The Enter Times of Day and Days of the Week field sets the time when the alert is active – alerts will only be executed during the selected days and times.
  10. The Cool Off Period is the number of minutes between alert updates. Once an alert is sent, if the problem has not been resolved, additional alerts will only be sent after the Cool Off Period has expired.
  11. Click on the Apply button to create the alert action. This button will be available after one or more fields in the Select Actions section have been completed.
  12. You will receive a Notice that the Action has been successfully applied.
  13. After the action has been assigned, the Configure window will display a different icon for events with actions.
    Display with action notation
  14. Actions may be removed by using the Remove button next to the apply button.


Configure Suppression

Application events may also be suppressed for a specified schedule through the
Suppression tab under Dashboard >> Configure This can be used to suppress recurring alerts that are known problems – e.g. high disk queue alerts during a nightly backup. To set up a scheduled event suppression:

  1. Click on Dashboard and then select Configure
  2. In the Events tree in the left pane, select the event to be suppressed
  3. Select the Suppression tab at the top of the right pane
  4. Configure the Suppression Filters to cover the Computers or Computer Groups to be suppressed, and any entities that should be suppressed, e.g. Disk ID or Process Name
  5. Adjust the Times of Day and Days of the Week for the period the event should be suppressed
  6. Click Apply
  7. With a scheduled event suppression configured, the icon for the event will be colored yellow in the left Events pane
  8. To remove a scheduled suppression, make sure no days are selected for the schedule, and click Apply



Data collected by Longitude is available for historical reports. Reports on performance metrics collected by Longitude are available in both graphic and tabular formats. Events displayed by Longitude can also be used to generate text reports. The length of time data is kept will vary by application, but performance data is generally kept longer than event data.

Performance Reports

Longitude reports are produced by the data collected from monitoring, and from Events created through analyzing the data. Reports can either be Summary reports, comparing data across computers, or detail reports, looking at the data on a specific computer over time. To run reports:

  1. Click on the Reports tab.
    Reports with notes
  2. Select an Application from the Select an application… drop down list. This list will only include applications for which Longitude is collecting data.
  3. The available reports for the selected application are listed as tabs in the right pane.
  4. Reports are either Summary reports, comparing the same metrics across a group of computers, or Detail reports, displaying metrics on an individual computer over time. To produce a summary report, select Enterprise for all computers, or a specific Computer Group in the Groups tab. To produce a detail report, select an individual computer in either tab. The labels for each computer name in a Summary report are links to the Detail report for the selected computer for the same metrics and time range.
  5. Hovering over the graph will generate a tool tip displaying the value of the graph at that location.
  6. The left pane of the report can be collapsed or expanded through a button on the frame separating the two panes.
  7. Expand the Report Options section in the left pane for options on filtering data and changing the format of the report. The options avialable on this tab will vary depending on the selected report:
    Report options for summary disk report Report options for summary disk report Report options for summary disk report
    Windows Disk Summary Report Options Windows Disk Detail Report Options Windows Network Detail Report Options
    • Report Display Buttons:
      • Timeline and Hourly options are available for Detail reports only.
      • Timeline reports will show the metric over the selected time period. Timeline reports are useful for looking at data trends over time.
      • Hourly reports will show the average value of the metric vs. hour of the day for the selected time period. Hourly reports are useful for identifying specific times of the day when problems recur.
      • Reports for items with multiple devices on a server will also display an icon for the devices in Report Options. For example, Disk reports will display a Disk button, or Network reports will display an Interface button.
      • Graph and Table formats are available for both Summary and Detail reports.
    • Options
      • By default Table reports will display values in the same colors used in the Graph. Uncheck the Show table colors check box to display all values in black.
      • Some reports will display more than one metric – e.g. CPU displays System % and User %. Checking the Sum usage checkbox will display the total value rather than the component value. Sum usage is only visible on reports which display multiple metrics.
      • Summary reports for multpiple devices will have the option to display individual items – e.g. summary disk reports will provide the option to view all the disks averaged over a device, or to view all the disks for a device.
    • Items
      • In Summary reports, the options are to view:
        • All computers
        • Top 25 computers
        • Top 10 computers
        • Select computers to be included in summary

        The Top computer lists are sorted based on the item reported – e.g. a CPU report will sort based on highest CPU usage.

      • Detail reports will only have an Items section if there are entities to select (Disks, Network Interfaces, etc.). If there are no entities, the Items section is not listed.
  8. Expand the Date & Time section in the left pane for controls to adjust the time period covered by the report
    Time options Calendar Time options
    Time/Date selections Calendar selection
    • Expanding the Date & Time tab will collapse the Report Options tab – only one tab can be open at a time.
    • The default Date Range is Today, and the default Hours of the Day setting is All.
    • Selecting the Today, Yesterday, or This Week tabs will populate the values for the Date Range field. This Week is calculated as starting on Monday.
    • Removing a selection in Days of the Week, or setting a time range in Hours of the Day will remove samples in those time periods from both Summary and Detail reports. In Summary reports, the values removed from the selections will not be used in calculating the reported averages. In Detail reports, data points before and after the excluded period will be connected by a line.
    • The Date Range values may be typed in manually, or may be selected from a calendar by clicking on the icon to the right of the date range field.

    Report menu options

  9. The Print and Email buttons are only available for Graphs.
  10. The Export button will provide the numeric values for the report in comma separated format.
  11. See the Report Scheduler documentation for instructions on
    how to configure automated reporting.


Virtualization Reports

Virtualization reports are available under Hyper-V and VMware – Standard Reporting.
Virtualization reports provide timeline performance reporting for both hosts and VMs, and summary comparison reports between VMs or between hosts. To use these reports, go to Reports and select Hyper-V or VMware – Standard Reporting from the drop down list.

Virtualization reports are divided into VM reports and host reports:

VMware VM reports

  • VM CPU%
  • VM CPU Ready
  • VM Memory
  • VM Disk
  • VM Network
  • VM Storage
  • VM File
  • VM Zombies

VMware Host Reports

  • Host CPU
  • Host Memory
  • Host Disk
  • Host Network
  • Datastore Storage
  • Datastore File
  • Cluster CPU
  • Cluster Memory

Hyper-V VM reports

  • VM CPU%
  • VM Memory
  • VM Memory Pressure
  • VM Disk I/O
  • VM Queue Length
  • VM Network Data
  • VM Network Packets

Hyper-V Host Reports

  • Host CPU%
  • Host Processor CPU%
  • Host Memory
  • Host Mem Pressure
  • Host Disk I/O
  • Host Queue Length
  • Host Disk Storage
  • Host Network Data
  • Host Network Packets

If you select Enterprise in the Computers tab, or a group in the Groups tab, the right pane will display a summary comparison of hosts to other hosts or VMs to other VMs. If multiple entities are available for a summary report, such as multiple processors for a host or multiple virtual NICs for a VM report, there will also be an option to display individual entities or the total value.


Hyper-V host summary report:

Vmware Standard VM CPU Summary Report

VMware VM summary report:

Vmware VM Network detail summary

For VMware – Standard Reporting selecting an individual vCenter server in the Computers or
Groups tab will display reports for the hosts and VMs managed by that vCenter server.

Vmware Standard CPU summary by VM


VMware Capacity Planning

NOTE: VMware capacity planning reports run much faster in Chrome or Firefox than in Internet Explorer.

As with VMware Standard reports, VMware Capacity Planning uses the data collected by Longitude from monitoring vCenter servers and ESX hosts. VMware Capacity Planning may be run by selecting the VMware – Capacity Planning option in the drop down list on the Reports tab.

To run a capacity planning report, select the vCenter server you want to use for capacity planning, navigate through the Real Data Centers tree located in the left panel and click on a host, resource pool, datastore, or virtual machine. Use the tabs above the center panel to view different types of reports.

Run Report

You can change the format of the reports by clicking the Timeline or Hourly Average buttons, located in the Report Options window at the bottom of the left panel. Reports can also be viewed as graphs or tables by clicking the Graph or Table buttons.

Change Format

Clicking an item in the legend on the right side of the chart will show or hide the item. If you mouse over a point on the chart, a tooltip will be displayed giving information about that data point.

Tool Tip

The Report Options window also contains additional customization for each report. To change the settings for the currently displayed report, check or uncheck one of the configuration boxes. Note that some reports will have no options.

Report Options

The Date & Time window, located underneath the Report Options window, allows you to change the time range of the reports.

Date and Time Options

When viewing a host or datastore report, the values for the host or datastore (ie the black line) are always visible, no matter which boxes in the Report Options window are checked. However, when viewing a resource pool report, if any of the virtual machine boxes in the Report Options window are checked, the report will not show the resource pool values. Instead, it will only show the virtual machine values for that resource pool.

Resource Pool VMs Checked

To see the actual resource pool values, uncheck all virtual machine checkboxes in the Report Options window.

Resource Pool VMs Unchecked


Capacity Planning Scenarios

Scenarios are modifiable copies of the current vCenter structure. They allow you to try out different configurations and determine the effects of adding or deleting virtual machines. To create a new scenario, click the plus sign button in the top right corner of the left panel (make sure that with Scenarios is checked).

New Scenario

Items in scenarios can be moved around by dragging and dropping. The following example shows what would happen if we moved virtual machine CRM from host vmprod1 to host vmprod2:

Before move:

Before Move

After move:

After Move

Right clicking an item in a scenario brings up a menu with a number of options:

  • Rename – Change the name of the item.
  • Properties – View and/or change various properties of the item.
  • Clone – Create a copy of the current item.
  • Alphabetize – Orders the items underneath the current item by name.
  • Revert – Restore the item to its real configuration.
  • Delete – Remove the item from the tree.

Right Click Menu

You can change the CPU, memory, disk, and network usage of a virtual machine by modifying the Multiplier field in the Properties menu (right click the item, then select Properties). Setting the multiplier greater than 1.0 will increase usage values, setting the multiplier less than 1.0 will decrease usage values, and setting the multiplier equal to 1.0 will leave usage values unmodified. For example, a multiplier of 2.0 will double all values, while a multiplier of 0.5 will cut all values in half.


Note that all changes made to scenarios are automatically saved.


Report Scheduler

The Scheduler button will allow you to automatically produce the report you are
currently viewing, email the report, and write it out to a specified directory.


The available report schedules and retention times are:

Schedule Report Runs Retention Period
Hourly Hourly, 8am to 6pm 3 days
Daily 00:00, Daily 1 month
Weekly 23:59, Sunday 3 months
Monthly 23:59, 1st day of Month 6 months
Quarterly 23:59, 1st day of Quarter 1 year


To Schedule a Report:

  1. Click on Scheduler >> Add Scheduled Report
  2. Modify the Description – this will be the label used for the report under Scheduler >> Manage Scheduled Reports.

    Scheduling a report
  3. Select a Report Schedule from the Schedule drop down list – refer to the schedule table for report times and retention periods.
    Scheduled report times
  4. To automatically email the report, check the Email Report box and enter a comma separated list of addresses. There should not be any spaces between the addresses in the list.
  5. To automatically write the report out to a file:
    • If the report destination is on a network share, check that the account used by the Heroix Longitude Web UI Service has write permission for the share. By default, the Web UI service runs under the LocalSystem account, and this account will need to be changed to an account that has permissions to write to the destination folder, and the Web UI service will need to be restarted for the new permissions to be effective.
    • Check the Export Report box.
    • Enter the destination folder.
    • Enter the File Name for the report, without a file extension. The report will be saved as a “.xhtml” file.
  6. Select the number of Days of Data for the report. The default is 1 day.
  7. Select the hours of the day the report will cover. The default is All Hours.
  8. Click Save to save the report.


To Manage Reports:

  • Click on Scheduler >> Manage Scheduled Reports
  • The Count column lists the number of reports that have been produced for each
    Description. Click on the Plus icon to view the list of available archived
  • The Date column lists when the reports were generated. Reports created by the Scheduler will
    display a Date only. Reports that have been run manually will display both Time and Date.
  • The Description is the text entered when the report was created. Editing the Description field will also change the description for archived reports. The Description may be edited by using the Edit icon.
  • The View Archive icon to the right of the archived reports creates a pop up window with the archived report.
  • The Delete archived report icon removes the archived report. Before deleting the report, a pop up window will ask you to confirm that you want to delete the report.
  • The Edit icon brings up the Modify Scheduled Report form,
    which will provide the option to change the Scheduled report settings and Description. In order to view report modifications, click on the Refresh button in the lower right of the Manage Scheduled Reports window.
  • The Delete Scheduled Report icon will remove the report from the Scheduler. Before removing the report, a pop up window will ask you to confirm that you want to remove the report. Removing a scheduled report will remove all the previously archived reports it produced.
  • The Run Report icon will manually run the scheduled report, including
    emailing or exporting the report if those options have been configured. In order to view newly run reports, click on the Refresh button in the lower right of the Manage Scheduled Reports window.

Managing Scheduled Reports


Real Time Monitor

Click the Real Time tab to run a real time performance monitor. A real time performance monitor graphs the current values of preselected Network Device, Unix or Windows metrics at a 10 second interval.

To display the Real Time Monitor select the computer or network device in the Real Time Performance Monitors panel.

The real time performance monitor performs multiple collections at a 10 second interval for as long as the monitor is running. This display can be resource intensive. It should not be left running if it not being interactively viewed. To stop a real time performance monitor, click another computer or device in the tree to start another one, click Enterprise or one of the application names in the tree, or click another tab.

Real Time Windows


Longitude Command Line

The Longitude Command Line tool can be used to configure Heroix Longitude to start, stop, suspend and resume application monitoring, to add computers to groups, and to list computers by group or by monitored application.

The Longitude Command Line tool has limited error checking so we strongly recommend verifying command syntax by viewing command results in the Longitude Web UI before using Longitude commands in scripts intended to automate monitoring actions.


  1. Install Longitude 10.1 or upgrade to Longitude 10.1.
  2. Longitude commands can be run from either the Longitude Management Console, or from a remote computer. If you would like to run Longitude commands from a remote computer, the computer requires:
    • Windows computer
    • Java version 7 or higher
    • Ability to make an RPC connection to the Longitude Management Console. Generally, this means that there should be no firewall between the Longitude command line computer and the Longitude Management Console.
  3. Copy the entire Longitude\LongitudeCommand folder on the Longitude Management Console to c:\LongitudeCommand on the computers you will be using to run the Longitude commands. This folder must be copied to c:\ regardless of whether you are running commands on the Longitude Management Console or a remote computer.
  4. (Optional): Longitude commands must include the name of the Longitude server, a Longitude user with Admin rights, and that user’s password. Default settings for these values can be specified in the c:\LongitudeCommand\longitude_command.defaults file.

Technical Notes

  1. Argument values are case sensitive.
  2. The longitude command is a .bat file, so if you are scripting with a batch file you will need to execute it using “CALL”, e.g. “CALL longitude monitor /a Windows /c”.

Longitude Command Syntax

longitude <action>   <arguments>   <server>

Longitude <actions> are one of the following with additional action specific <arguments>:

monitor Monitor an application on a computer/group
remove Remove monitoring of an application for a computer/group
remove_all Remove all application monitoring for a computer/group
suspend Suspend all application monitoring for a computer/group
resume Resume application monitoring for a computer/group
group Add a computer to a group and create the group if it does not exist
list_in_app List all computers being monitored by a specified application
list_suspended List all suspended computers
list_groups List all group names
list_in_group List all the computers in a group


This section specifies the Longitude Management Console being updated, a Longitude admin account, and the password for that account. Note that these arguments may be omitted if their values are specified in c:\LongitudeCommand\longitude_command.defaults

/s     <Longitude server>
/u     <Longitude username>
/p     <Longitude password>


Monitor – Monitor a Longitude application on a computer or group.

SYNTAX:     longitude monitor [arguments]


/c <computer> or /g <group>

Specify either the computer (/c) or group (/g) on which the application will be monitored. Both /c and /g cannot be used in the same command.

/a <application>

The name of the application to be monitored (see Application Properties document for full list of applications)

/i <instance>

Specify the instance for applications that can include multiple instances, e.g. SQL2016 or UnixScript Transactions.

/t <transaction type>

If the command is registering a Transaction then the type of transaction must be specified.

/props <application properties>

  • See Application Properties document for required and optional properties for each application.
  • The format for the application properties is:
    /props “Name1:Value1,Name2:Value2,…,NameN:ValueN”
  • Property names and values are case sensitive.
  • Only use commas between properties – spaces are not allowed.
  • Values containing commas must be enclosed by parenthesis, e.g.:
    /props “LogFile:Application,Type Allow List:(Error,Warning),Event Allow List:(5,100,3000)”

/r <remote agent>

(Optional) Specifies a Longitude remote agent which will collect data for the computer being monitored. If /r is not used, data will be collected by the Longitude server. Note that when an application is first monitored on a computer the agent used for that application will be used for all other applications and the /r option will be ignored.


(Optional) When setting up monitoring Longitude will attempt to resolve specified computer names to fully qualified domain names. Specifying /suppress_dns will register the computer under the name specified in the /c argument.


NOTE: For details on required application properties, consult the Longitude Command Line Application Properties document.

  1. Monitor Windows on computer
    longitude monitor /a Windows /c
  2. Monitor Unix on computer with username “service” and password “pwd” using remote agent “”:
    longitude monitor /a Unix /c /r
    /props “Username:service,Password:pwd”
  3. Monitor PingCritical transaction for group UnixComps:
    longitude monitor /a Transaction /t PingCritical /g UnixComps
  4. Monitor HttpUrl transaction for computer
    longitude monitor /a Transaction /t HttpUrl /i mainurl /c
    /props “URL:,Path:/,Protocol:https”
  5. Monitor SQL2014 application for SQL instance named “Heroix” on computer
    longitude monitor /a SQL2014 /c /i Heroix
    /props “NamedInstance:Heroix,Database Driver:net.sourceforge.jtds.jdbc.Driver,Database URL:jdbc:jtds:sqlserver://;integratedSecurity=true;instance=Heroix;”
  6. Monitor SQL2016 application for default SQL server 2016 instance on computer
    longitude monitor /a SQL2016 /c
    /props “Database Driver:net.sourceforge.jtds.jdbc.Driver,Database URL:jdbc:jtds:sqlserver://;integratedSecurity=true;”
  7. Monitor Oracle instance inst1 on
    longitude monitor /a Oracle /c /i inst1
    /props “Oracle Instance:inst1,Oracle User:admin,Password:password”
  8. Monitor Windows Application Event Log for all computers in group “test” using instance name “Application”. Only collect Error and Warning events with Event ID 5:
    longitude monitor /a WindowsEventLog /g test /i Application
    /props “LogFile:Application,Type Allow List:(Error,Warning),Event Allow List:5”
  9. Monitor Windows Application Event Log for all computers in group “test”, using instance name “Application”. Only collect Error events for Event IDs 5,100, and 3000.
    longitude monitor /a WindowsEventLog /g test /i Application
    /props “LogFile:Application,Type Allow List:Error,Event Allow List:(5,100,3000)”

Remove – Remove monitoring for a Longitude application from a computer or group.

SYNTAX:     longitude remove [arguments]


/c <computer> or /g <group>

Specify either the computer (/c) or group (/g) on which the application will be removed. Both /c and /g cannot be used in the same command.

/a <application>

The name of the application to be removed (see Application Properties document for full list of applications)

/i <instance>

Specify the instance for applications that can include multiple instances, e.g. SQL2016 or UnixScript Transactions. If you are removing a transaction, specify only the transaction’s unique instance name instead and do not specify the Transaction Type (/t). For example, to remove the Ping transaction for the group “test”:

longitude remove /a Transaction /i Ping /g test

Remove_all – Remove all Longitude application monitoring from a computer or group.

SYNTAX:     longitude remove_all [arguments]


/c <computer> or /g <group>

Specify either the computer (/c) or group (/g) on which the applications will be removed. Both /c and /g cannot be used in the same command.

Suspend – Suspend all Longitude application monitoring for a computer or group.

SYNTAX:     longitude suspend [arguments]


/c <computer> or /g <group>

Specify either the computer (/c) or group (/g) on which all application monitoring will be suspended. Both /c and /g cannot be used in the same command.

Resume – Resume Longitude application monitoring for a computer or group.

SYNTAX:     longitude suspend [arguments]


/c <computer> or /g <group>

Specify either the suspended computer (/c) or group (/g) of suspended computer on which application monitoring will be resumed. Both /c and /g cannot be used in the same command

Group – Add a computer to a group and create the group if it does not exist.

SYNTAX:     longitude group [arguments]


/c <computer>

The computer to be added to the group.

/g <group>

The group to which the computer will be added. If the group does not exist, it will be created.

List In App – List all computers being monitored with a specified Longitude application.

SYNTAX:     longitude list_in_app [arguments]


/a <application>

The application to be scanned for monitored computers.

/t <transaction-type>

The transaction-type to scan for monitored computers when the application is Transaction.

List Suspended – List all suspended computers.

SYNTAX:     longitude list_suspended

List Groups – List all group names.

SYNTAX:     longitude list_groups

List in Group – List all computers in a group.

SYNTAX:     longitude list_in_group [arguments]


/g <group>

Group name to scan for member computers.




Unable to monitor Windows 2012 server using local admin account

If receiving Access Denied errors while trying to monitor Windows 2012 with a local admin account, the following configuration of the Windows 2012 server will enable monitoring to properly function:

  • Go to Local Security Policy
  • Go to Local Policies -> Security Options
  • Go to User Account Contol: Run all Administrators in Admin Approval Mode, then set this to Disabled
  • Reboot the 2012 server so this takes effect
  • Then to monitor the server again


How to fix Collections failing with “Invalid Class” errors

If WMI collections fail with an error referencing Invalid Class (example at the end of this topic), resynchronizing the performance counters may correct the issue.

To resynchronize the performance counters, run the following from the command line on the computer that you are trying to monitor:

  • winmgmt /resyncperf
  • After running the winmgmt command, restart the WMI service on the target computer.

Example of a Longitude Invalid Class error:

This collection is not registered. Collection registration failed.
Resolve cause of inner exception
Registration failed for new collection.
Registration to SS failed.
The Statistics Server could not complete the request.
Error when registering a collection. Check Error Log for more details.
Failed to collect from WmiV2: retVal=0x80041010, computer=xxxxxxxx, The enumerator terminated with an ‘Invalid Class’ error for query Select * from Win32_PerfRawData_PerfOS_System, HRESULT=0x80041010
A general error occurred: Failed to collect from WmiV2: retVal=0x80041010, computer=xxxxxxxxx, The enumerator terminated with an ‘Invalid Class’ error for query Select * from Win32_PerfRawData_PerfOS_System, HRESULT=0x80041010
No remedy is available.


How does Longitude SMTP server work?

Heroix Longitude can send e-mail through two mechanisms: an internal SMTP engine and through a user-configured, external SMTP server. This dual approach is taken to minimize initial configuration and to provide additional flexibility and resiliency. The default SMTP engine will continue to function and send email independent of the health and availability of the existing external SMTP server.

Heroix Longitude uses SMTP to mail:

– Administrative notices from the Web UI (e.g. new user notifications, password change notifications)
– Reports
– Alert Notifications from Longitude events (go to Dashboards >> Configure >> Actions to enable mail notification for individual events).

By default, Heroix Longitude uses an internal SMTP engine, called Aspirin, to send e-mail. The internal SMTP engine does not require any configuration from the user. The internal SMTP engine functions as a mini send-only SMTP server running inside Heroix Longitude. Since it is not registered as a real SMTP server, some spam filters may interpret the e-mail Longitude sends as spam. This may be the problem if you do not receive any e-mail from Heroix Longitude.

The Limitations section on the Aspirin website ( notes a potential problem sending mail to a server using Sender Policy Framework mail authorization, along with a link to the SPF website ( for more details.

More information about configuring e-mail settings in Longitude is available in the online help Longitude Help

How do I backup my Longitude Server?

  1. On the Longitude server, go to \Program Files\Longitude\appman\config.
  2. Open the backupDefintion.xml file with a text editor i.e. WordPad.
  3. Note that the backup schedule is initially disabled by the early end date. Modify the EndDate property to a date in the future to enable the backup.
  4. A list of days of the week may be entered for daily backups.
    (ex. Sunday,Monday,Tuesday,Wednesday,Thursday,Friday,Saturday)
  5. You may also edit this file to add additional files to the backup or change the destination to a different drive. If you have any customized files for Longitude – e.g. applications or scripts – please include these files in the backup.
  6. Enter a backup destination – make sure the destination has enough free space for the backup files. The size for these files will vary depending primarily on the database size – review the size of the Longitude\sapdb\indep_data\wrk\FZEDB1\DATA* files – the sum of the size of these files will provide an estimate of the maximum space needed.
    The destination location must be a local drive, and you cannot use any spaces when you specify it. For example: c:\program files\Longitude\backup should be specified as c:\progra~1\Longitude\backup
  7. When all changes to the backupDefinition are complete, save & close the file.
  8. Restart the Heroix Longitude Upgrade Manager service.
  9. When a backup time specified by the file occurs, the Upgrade Manager will backup the specified files and the database, and send an email when the backup is completed to the MailToForLongitudeProblems address.
  10. To run an on-demand backup, go to Admin >> Advanced >> Administration >> Component Management >> Manage Longitude Properties >> Upgrade Manager >> Advanced and change the AdHocBackupTime value to a time you would like for the next backup. For example, setting it to 13:15 would schedule an ad hoc backup the next time 1:15 PM occurs. After the backup has been started, this setting will revert to the default “HH:mm” value, so the backup will only be done once when this setting is modified.


Configuring public-key authentication for SSH based collections

The Statistics Server supports SSH authentication via public key exchange. Password authentication is always attempted first, and if that fails then key based authentication is used.

Longitude installs keys under Longitude/ss/config/sshKeys. The appropriate public key needs to be configured on the monitored computer before key based authentication will succeed.

The instructions for configuring the keys will vary based on the version of SSH and the operating system of the agent. In general, the following steps can be used for setting up Public Key Authentication to monitor a Unix/Linux server:

  1. The public key goes on the monitored Unix/Linux computer, in the .ssh/authorized_keys file in the home directory for the account being used in the ssh connection.
  2. The private key goes on Longitude agent, in Longitude\ss\config\sshkeys\{filename}, where {filename} is either OpenSshRsa1024 or OpenSshDsa1024, depending on whether an RSA or DSA key is being used.
  3. If using the keys provided with Longitude, copy the text from the Longitude\ss\config\sshKeys\{keyname}.pub file and write it into the authorized_keys file for the appropriate account.
  4. If you generate your own key, and you set up a password for the key, the password is entered in the field for the password for the account.


Using a trusted SSL certificate with Longitude’s Web UI

Longitude provides a self-signed certificate when it is installed for basic site encryption. Since this certificate is not signed by a trusted certificate authority, Firefox 3.x may not allow you to view the Longitude Management Console in SSL using the default certificate, and other browsers may display security warnings.

To resolve these issues, you will need to configure the Longitude Management Console to use an SSL certificate from a trusted authority. Heroix is not a certificate provider, and cannot provide a trusted certificate – you will need to create a certificate site request (CSR) and provide this to a certification authority. The authority you purchase the certificate from will usually provide you with specific instructions for creating an acceptable CSR. Longitude uses a Tomcat web server, with a home directory of Longitude\tomcat. The default files used to configure SSL are all in Longitude\tomcat\conf, and are:

keyStore default keystore, password = “changeit”
httpsKeys.pkcs12 keyfile containing self signed certificate
server.xml server definition file

In general, the sequence of steps to install a new certificate is:

  1. Create a keystore to hold the certificate information
    • Go to a command prompt in the Longitude\tomcat\conf directory, and use the “keytool” command. The syntax would be:keytool -genkey -alias {aliasForEntryInKeystore} -keyalg RSA -keysize 2048 -keystore {nameOfKeystore}.jks
    • for example:keytool -genkey -alias longitude -keyalg RSA -keysize 2048 -keystore longitude.jks
    • Remember the alias used to create the keystore – you will need to import the server certificate using the same alias.
  2. After entering this command, you will be prompted for information about the web server:
    • You will be asked to create a password – remember this, you will need it later
    • You will be asked for your “first and last name” – this is the FQDN for the longitude server, and should be the address used to access the Longitude Web UI (e.g.
    • You will be asked for you organizational unit (becomes a property of the certificate – not critical)
    • You will be asked for your organization (becomes a property of the certificate – not critical)
    • You will be asked for your City or Locality (becomes a property of the certificate – not critical)
    • You will be asked for your State or Province (becomes a property of the certificate – not critical)
    • You will be asked for your two letter country code (becomes a property of the certificate – not critical)
    • It will repeat the information you’ve entered, and ask if it’s correct – if it’s not, take the default “no”, and re-enter the information.
    • You will be asked for a key password – the default is the same password you used previously.
  3. After running this command, you will now have a keystore file (with a .jks extension).
  4. Use the information in the keystore file to create a certificate site request (CSR)
    • run this from the same directory you created the keystore.jks file:keytool -certreq -alias {aliasForEntryInKeystore} -file {outputfile}.txt -keystore {nameOfKeystore}.jks
    • from our previous example:keytool -certreq -alias longitude -file csr.txt -keystore longitude.jks
    • you will be prompted for the keystore password (the first one you entered above – the one I told you you would need later). The certificate site request will be the csr.txt file.
  5. Find a trusted certificate authority, and send them the csr.txt file. They will send you back a certificate.
  6. Save your certificate file and any additional root and intermediate certificates to the Longitude\tomcat\conf directory.
  7. Back up your keystore file before importing any certificates.
  8. Certificates may be imported with the following command:
    keytool -import -alias {aliasForEntryInKeystore} -file {certificateFile} -keystore {nameOfKeystore}.jks
    Please note that root and intermediate certificates will use a different alias than the server certificate, and the server certificate must use the alias that was used to generate the keystore. If your certificate authority provides alternate instructions for loading certificates into the keystore, please follow their directions.
  9. Keytool has an option to delete certficates. If you make a mistake when importing the server certificate, do NOT delete the certificate for the server’s alias as it will delete the private key for the server. Restore the keystore from backup and begin the import again.
  10. MAKE A BACKUP COPY OF Longitude\tomcat\conf\server.xml!!!!!!!! Keep it someplace safe. You may need to back out of this.
  11. Edit the Longitude\tomcat\conf\server.xml file to use your keystore.
      • The SSL section of the file has the following default values:<Connector port=”7238″ maxThreads=”150″ minSpareThreads=”25″ maxSpareThreads=”75″ enableLookups=”false” disableUploadTimeout=”true” acceptCount=”100″ debug=”0″ scheme=”https” secure=”true” clientAuth=”false” sslProtocol=”TLS” keystoreFile=”./conf/httpsKeys.pkcs12″ keystorePass=”changeit” keystoreType=”PKCS12″ />
      • Modify this file to change this section to:
        <Connector port=”7238″ maxThreads=”150″ minSpareThreads=”25″ maxSpareThreads=”75″ enableLookups=”false” disableUploadTimeout=”true” acceptCount=”100″ debug=”0″ scheme=”https” secure=”true” clientAuth=”false” sslProtocol=”TLS” keyAlias=”{yourAlias}” keystoreFile=”./conf/{yourFile}” keystorePass=”{yourPasswrd}” />
      • From our example:
        <Connector port=”7238″ maxThreads=”150″ minSpareThreads=”25″ maxSpareThreads=”75″ enableLookups=”false” disableUploadTimeout=”true” acceptCount=”100″ debug=”0″ scheme=”https” secure=”true” clientAuth=”false” sslProtocol=”TLS” keyAlias=”longitude” keystoreFile=”./conf/longitude.jks” keystorePass=”myPasssword” />

    ***Please note:
    When you purchase a certificate from a trusted authority, they will usually provide instructions for applying that certificate. Please modify Longitude’s server.xml file as they specify.

  12. Restart the Web UI
  13. After the Web UI has initialized, try to access the Longitude management console using https over port 7238.


Longitude installed on a Workgroup computer

If Longitude is installed on a server in a workgroup, Longitude will generate the following message during installation:

Heroix Longitude is being installed in a workgroup. Workgroup installations are for evaluation purposes only. After installation, you will be able to collect data for this machine only.
To collect data for additional machines, consult the Heroix Community web site for knowledge book articles on workgroup configuration.
To continue the installation, click OK, otherwise click Cancel.

The installation will configure Longitude to use Local System account permissions for Windows collections, and in this configuration, Longitude will only be able to collect Windows data from the computer it is installed on. To configure Longitude to collect data from other Windows Servers, you will need to set up authentication to those computers.

Authentication is configured by setting up corresponding local accounts on the Longitude computer and any computers to be monitored. The account should have the same username and password on each computer, be a member of the local administrators group on each computer, and be used as the Statistics Server service account. The Statistics Server account can be accessed through the Windows Services Applet (Control Panel >> Administrative Tools >> Services >> Heroix Longitude Statistics Server Service, log on information is set in the Log On tab).

For example, if you install Longitude on computer Workgroup1, you could set up local account “longitude”, with password “heroix”, make it a member of the Local Administrator group, and configure the Heroix Longitude Statistics Server service to log in as “.\longitude”, with password “heroix”. On monitored computer Workgroup2, you would also set up a local “longitude” account, with password “heroix”, and make it a member of Workgroup2’s Local Administrator group.

*****Please note:
Depending on your computer’s security settings, this authentication may not work. Consult with your System Administrator to determine your local settings.

Alerts from Longitude for Component Problems

ongitude will monitor each of its components for performance and connectivity.

The 5 Longitude components are:

  • Consolidator
  • Rule Engine
  • Statistics Server
  • Upgrade Manager
  • Web UI

If a Longitude component experiences a problem that Longitude cannot repair on its own, an email alert will be sent to the address or addresses specified in Admin >> Mail. Each component has its own Contact property and the default value is the email address entered during installation.

The following alerts may be generated by Longitude:

  • Subject: Longitude Component running out of memory
    This alert may be generated for any of the Longitude Components. Usually restarting the service for the named component will resolve the error. If you continue to get out of memory alerts, please submit the issue to Heroix Support or post your issue to the Community.
  • Subject: Statistics Server is not reachable
    This alert may be generated for either the Statistics Server on the Management Console, or for a remote agent. For either the local or remote server, first confirm that the Heroix Longitude Statistic Server Service is running on the server.
    If the service is running, and the alert is for a remote Statistics Server, check the firewall and confirm that port 7220 is open, or port 7223 is open if using SSL.
    If this problem persists, please submit the \Longitude\ss\log\ss_startup.txt to Heroix Support or post the contents of the file to the Community.
  • Subject: One or more Longitude components are not running
    This alert may be generated for any of the Longitude Components. Please confirm the appropriate Heroix Longitude service is running. If this problem persists, submit the related component startup.txt to Heroix Support or post the contents of the file to the Community. The startup.txt files can be found in the following directories:

    Consolidator Longitude\consolidator\logs\consolidator_startup.txt
    Rule Engine Longitude\engine\log\engine_startup.txt
    Statistics Server Longitude\ss\log\ss_startup.txt
    Upgrade Manager Longitude\appman\log\appman_startup.txt
    Web UI Longitude\tomcat\webapps\webui\log\webui_startup.txt


Installation fails with “SysWOW64” error

Longitude is supported on 64-bit Windows servers, and the installation checks registry values to determine that the operating system is a supported Windows version. One of the checks is for the following “SystemDirectory” value:


if this value is set to “C:\Windows\SysWOW64” or “%SystemRoot%\SysWOW64”, the installation will stop with a SysWOW64 warning. If you receive this warning but the SystemDirectory key is set to “C:\Windows\system32” or “%SystemRoot%\system32”, please contact Heroix Support.


Unable to monitor a URL

If you are trying to monitor a URL and the error returns an error code with the following “Received fatal alert: handshake_failure”, please contact Heroix Support. We have a script which can be used to monitor this site.


Release Notes


The Release Notes document includes a list of new features introduced in this release of Heroix Longitude®, a list of known issues, and information about upgrading Longitude.

Product Packaging

Heroix Longitude can be packaged to exclude certain product capabilities. However, the documentation will include a description of the full capabilities of the product. If you have installed a package containing less than the full product, some of the capabilities described in the documentation will not be available to you.

Other Heroix Longitude documentation

Quick Start Guide

The Heroix Longitude Quick Start Guide gives a basic overview of the product, including instructions for installing and configuring the product. For more detail about Heroix Longitude, please see the online help. You can access the Quick Start Guide from the Help menu in the Heroix Longitude Web UI or by opening the following web page:

Online help

You can access the online help from the Heroix Longitude Web UI, by selecting How to from the Docs menu.

The online help is context-sensitive – when you open the help, the page that is displayed will depend on what page of the Web UI you were on when you opened the help.

New Features

Heroix Longitude V10.1

  • Longitude Command Line Interface (CLI)
    • The Longitude CLI provides the ability to:
      • Add or Remove monitoring for computers or groups.
      • Suspend or Resume monitoring for computers or groups
      • Create groups, add computers to groups, and list computers in group.
      • List computers monitored by an application and list suspended computers
    • The Longitude CLI can be incorporated into user-written scripts to automate monitoring tasks.
    • For additional details see the Longitude Command Line help and Application Properties reference sheet
  • Monitoring Enhancements
    • The Longitude SQL2016 application is now available.
  • Other Enhancements
    • The right-click menu for Events in the Event Monitor now includes a direct link to the Event’s Configure page.

Heroix Longitude V10.0

  • Enhancements in the primary user interface in V10.0
    • The user interface uses Apache tomcat V8 in Longitude V10.0
    • The definition of computer groups has been changed, allowing computers to exist in multiple groups.
    • The summary of all Status dashboards now contains a colored icon representing the worst state of each dashboard.
    • Several schedules are available when defining scheduled reports.
    • Monitoring can be suspended or resumed on multiple computers with a single operation.
  • Monitoring Enhancements
    • The NetworkDevice solution has been enhanced to support SNMP V2 64-bit counters.
  • Other Enhancements
    • Longitude V10.0 uses Java 8.

Product notes

  • Install may fail on Windows if logged in with an account with non-alphanumeric characters

    The install on Windows may fail if you are logged in with an account that includes non-alphanumeric characters. If this occurs, try logging in to the machine with an account that only includes alphanumeric characters and run the install again.

  • Email stops working using the internal SMTP server

    By default, Heroix Longitude uses an internal SMTP engine, called Aspirin, to send email and does not require any configuration from the user. In many sites, this has worked correctly in a production environment, but some sites have experienced problems sending email. If you experience problems with the internal SMTP server, follow the instructions in the online help under “Configuring a User-Defined SMTP Server” to configure Heroix Longitude to use a different SMTP server.

  • Monitoring the Internet Application

    The Internet application enables you to emulate the experience of a web site by executing synthetic transactions against a web site and evaluating the response time and content of the site. Firefox 44.0 or higher is required on the Longitude Statistics Server to record and execute the internet macros.

  • Statistics Dashboard for VMware statistics

    Several of the VMware statistics can not be collected at the very short intervals used by the Statistics Dashboard (such as 10 seconds). If you create a Statistics Dashboard that includes VMware statistics, and the dashboard is not updated with new values each interval, you should use a longer interval.