Transaction

If you try to create a SLA and add a computer for a Transaction other than Ping it does not give you the list of computers to select:

Please follow the steps below, this will then give you the option to select the appropiate computers and instances.

1. Download the index-all.js file
2. Go to Longitude\tomcat\webapps\webui\web2.0\javascripts and rename the existing file to index-all.js to index-all.orig and save the new file to this location
   

The Manage Monitoring display shows that status of collections, not the results of those collections. Since the Statistics Server is successfully running the "Ping", "PingCritical", etc. test, the icon is still green, because you're able to run the transaction test. Any failures for transactions will create Longitude events, and these events can be viewed in the Event Monitor.

You can not change the schedule of a specific transaction that runs a specific computer. For example if you want to change the schedule of a specific WinScript Transaction running on one computer you can not. If you want to change the schedule of all WinScript transactions running on all of your machines we can do this.

If you would like to change the schedule of a specific transaction running on a specific computer then a custom solution would have to be created by Heroix Support for a charge.

Longitude can run scripts using the WinScript and UnixScript transactions, but the two scripting transactions work differently due to the difference in how Longitude connects to Windows and Unix computers.

Windows collections are made via WMI - for Windows Scripts, the script needs to be on the agent running the collection for the script. To refer to a remote computer, configure your script either with the name of the computer within the script, or as an argument for the script.

Longitude can be configured to collect data through an agent installation - this is useful if you need to collect data from devices at a remote site, on the other side of a firewall, or where you would need to use an alternate set of Windows credentials. However, especially for agents at remote sites, there can be a delay in collecting monitored data if the Management Console loses contact with the Longitude agent.

Longitude 6.0 and higher has the ability to collect Response Time for Transactions in milliseconds. To make this change please do the following:

1. Go to Administration >> Component Management >> Manage Longitude Properties
2. Click on the WebUI, then click Advanced
3. Change the ResponsetimeinMilliseconds property from no to yes
4. Click SAVE CHANGES

***Note: