Monitoring a Specific Application Port with Operations Manager

Question

An issue is being experienced with monitoring a specific application port using Operations Manager. When one of the servers hangs, the Agent heartbeat failure alert is not received, even though I confirm that the server is not pingable during this state. Is it expected not to receive a heartbeat failure alert in such a scenario? If so, guidance is needed on how to monitor a specific port from the Operations Manager server.

Any insights or recommendations on resolving this issue and effectively monitoring the specific application port would be greatly appreciated.

Answer 1

Hi,

It sounds like you're dealing with a tricky situation. Let's break it down:

Heartbeat Failure Alert

When a server hangs and becomes unresponsive, you should typically receive an Agent heartbeat failure alert if the server is not pingable. If you're not receiving this alert, it could be due to several reasons:

1. Network Issues: There might be network issues preventing the Operations Manager from detecting the heartbeat failure.
2. Agent Configuration: The agent on the server might not be configured correctly to send heartbeat signals.
3. Management Server Issues: The management server might not be processing the heartbeat signals correctly.

Monitoring a Specific Application Port

To monitor a specific application port using Operations Manager, you can use the TCP Port template. This template allows you to monitor the availability of an application accessible over TCP. Here’s how you can set it up:

Open the Operations Console: Start with an account that has Author credentials.

Navigate to the Authoring Workspace: Right-click on Management Pack Templates and select Add Monitoring Wizard.

Select TCP Port: Choose the TCP Port template and click Next.

Configure the Template:

• Name and Description: Provide a name and optional description.
  • Target and Port: Enter the name or IP address of the computer or device and the port number on which the application is listening.
    • Watcher Nodes: Select one or more agent-managed computers to run the monitors and rules.
      • Frequency: Specify how often the connection should be attempted.
      Test and Create: Validate your connection and create the monitor.

For more detailed steps, you can refer to the Microsoft documentation on the TCP Port template

Feel free to ask if you need further assistance or have more questions!