Create a TCP or UDP resource monitor
- Last Updated: March 30, 2020
- 2 minute read
- OpenEdge
- Version 12.2
- Documentation
OpenEdge Management supports setting up individual TCP and/or UDP monitors. The TCP monitor attempts to connect to a TCP port and reports status and response time. The TCP monitor can be useful in determining the status and response times for servers that listen on a TCP port. This includes servers such as mail, FTP, and Web servers.
Note: OpenEdge Management supports a default
operator e-mail TCP monitor identified as a Simple Mail Transfer
Protocol (SMTP) SMTP_Mail. You can set host, port, and default e-mail
recipient values in the Default alert recipient section
of the OpenEdge Management Configuration page. However,
you can edit values as you would any user-defined TCP resource monitor.
The UDP monitor attempts to communicate with a UDP port and reports status and response time.
Note: Monitoring a NameServer
using UDP resource monitors is not recommended. If you set up a
UDP monitor to monitor a NameServer UDP listener port, the NameServer
will detect the UDP messages. However, the NameServer will inspect
the UDP messages and reject them because they do not follow the
convention expected by the NameServer. Consequently, the NameServer
will log error messages to indicate that invalid message requests
are being received.
To define a TCP resource monitor: