You are hereManage Monitoring / Manage Monitoring
Manage Monitoring
6.3: Adding application fails with "Failed to canonicalize name" error.
When you add application monitoring for a server, Longitude checks the name of the supplied server in DNS and attempts to resolve the supplied name to a fully qualified domain name (FQDN).
We have seen instances in Longitude 6.3 where the call to get the FQDN has taken longer than expected, causing the Web UI to time out and produce a pop-up message with the error that Longitude "Failed to canonicalize" the requested name.
If you receive this error, do the following:
- Verify that you can ping the server by the supplied name
- Dismiss the error pop up message
Using the HttpUrl transaction to check a web page
The HttpUrl transaction will scan the content of a web page for a specified regular expression, and send an alert if the content isn't found. To set this up, you will need to enter the following information in Manage Monitoring for the Transaction/HttpUrl:
- Computer - enter the web server name or ip address
- Path - the path to the page at the specified web server
- Port - if not specified: 80 for http and 443 for https
- Protocol - http (default) or https
- ExpectedContentPattern - regular expression to find on the page
No servers listed in Manage Applications after collections have been suspended.
In Longitude 6.2, if you suspend all collections in Manage Monitoring, the MONITOR APPLICATION, REMOVE APPLICATIONS, and SUSPEND APPLICATIONS buttons are not available on the page, and you will see the following message:
Data is not loaded. Please try again in a few minutes.
To display the suspended servers and the management buttons:
- Go to the main Monitoring page.
- In the Manage Applications menu, click the Add link
- Register a ping transaction for a server that is not suspended
6.2: 64 bit Windows Agent displays unavailable status and is unable to collect data.
The full Management Console installation kit has an agent installation option. Some agents installed using this option in the 64 bit installation kit may have the following problems:
- In Administration >> Component Management >> Display Status, the agent status is displayed as red
- In Manage Monitoring, a test connection to the agent is successful, but you are unable to register collections
The following steps will fix this problem:
- Log on to the agent computer with a Local Administrator account
- Stop the Longitude services
kb61: Configuring WebSphere for the Longitude WebSphere application
Please follow the steps listed below to configure WebSphere for the Longitude WebSphere application:
- From the Administration Console, expand the Servers menu on the left hand side.
- Click “Application Servers”.
- Click the name of your server.
- Click “Performance Monitoring Service”.
- Click on the Configuration tab.
- Check the checkbox next to “Startup” to have the performance monitoring service start at startup.
- Click “Custom” and change all “N” to “X” - or the minimum required settings are below:
kb59: Exchange 2007 agent prerequisites
Longitude uses the Exchange Management Shell (EMS) to monitor Exchange 2007. EMS itself requires the .NET Framework and PowerShell. Install the software in the following order:
- .NET Framework
- Windows Powershell
- Exchange 2007 Management Tools - after unpacking the management installation files, install with the command:
setup.com /mode:install /role:T
The .NET Framework, Powershell and EMS can all be downloaded from Microsoft Downloads.
How do I select a specific agent to use for monitoring?
***Note::
Once an agent is associated with a managed device, all collections for that device will be made through that agent regardless of the agent selected when you register application monitoring. Each managed device can only have one agent associated with it.
****
If you need to use a specific Longitude agent to monitor a managed device, do the following when you register an application:
- If using the 2.0 UI, Click on the Advanced option
- Go to Monitoring >> Manage Applications and select the MONITOR APPLICATION button
How do I monitor Windows on an Active Passive Cluster?
- If you want to monitor Windows on an Active Passive Cluster you should Monitor the Windows Application on the nodes and on the Virtual Server.
- Set up Disk Filters by going to Manage Monitoring and clicking on the gear for windows.
- Then click modify on the Disk Collection. You should now see an Add Filter Button.
- You want to only monitor the shared drives on the virtual server and on the nodes monitor the physical drives.
Computer selection inconsistancy in webui
Running Heroix Longitude 6.1.2 (build 337)
This inconsistency in the webui leaves me confused as well as making it difficult to /delete/ Monitored computers though I can easily /add/ Computers to be Monitored:
Where Computers are to be selected for Monitoring, the comma-delimited field is blank though Computers are being monitored, and in the Monitored Computers drop-down, the monitored computers are not checked according to the "Gears" view where I do see all monitored Computers by Application. See Home | Monitoring | Manage Monitoring | Monitor Application
When my Ping transaction fails, why does it still have a green icon in Manage Monitoring?
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.