Review a full list of protocols and ports required for monitoring User Activity.

This post will provide information regarding the ports, protocols, use case & configuration settings if required that is been used in general, with respect to LM platform.

Using the "<port>/<protocol>" format is a common and standardized way to indicate network ports along with the associated protocols. This format helps provide a clear and concise representation of the port and protocol being discussed below :

Inbound communication :

Port	Protocol	Use Case	Configuration Setting
162	UDP	SNMP traps received from target devices	eventcollector.snmptrap.address
514	UDP	Syslog messages received from target devices	eventcollector.syslog.port
2055	UDP	NetFlow data received from target devices	netflow.ports
6343	UDP	sFlow data received from target devices	netflow.sflow.ports
7214	HTTP/ Proprietary	Communication from custom JobMonitors to Collector service	httpd.port
2056	UDP	JFlow data received from target devices

Outbound communication :

Port	Protocol	Use Case	Configuration Setting
443	HTTP/TLS	Communication between the Collector and the LogicMonitor data center (port 443 must be permitted to access LogicMonitor’s public IP addresses; If your environment does not allow the Collector to directly connect with the LogicMonitor data centers, you can configure the Collector to communicate through a proxy.)	N/A
Other non-privileged	SNMP, WMI, HTTP, SSH, JMX, etc.	Communication between Collector and target resources assigned for monitoring	N/A

Internal communication :

Port	Protocol	Use Case	Configuration Setting
7211	Proprietary	Communication between Watchdog and Collector services to OS Proxy service (sbwinproxy/sblinuxproxy)	sbproxy.port
7212	Proprietary	Communication from Watchdog service to Collector service	agent.status.port
7213	Proprietary	Communication from Collector service to Watchdog service	watchdog.status.port
15003	Proprietary	Communication between Collector service and its service wrapper	N/A
15004	Proprietary	Communication between Collector service and its service wrapper	N/A

Destination Ports :

Port	Protocol	Use Case
135	TCP	Port 135 is used for DCOM's initial communication and RPC (Remote Procedure Call) endpoint mapping.. DCOM often uses higher port numbers in the range of 49152 to 65535 for dynamically allocated ports
22	TCP	TCP for SSH connections
80	UDP	NetFlow data received from target devices
443	UDP	sFlow data received from target devices
25	HTTP/ Proprietary	Communication from custom JobMonitors to Collector service
161	UDP	JFlow data received from target devices
1433	TCP/UDP	TCP for Microsoft SQL
1434	TCP/UDP	The protocol used by port 1434 depends on the application that is using the port. For example, SQL Server uses TCP for communication with clients, while the SQL Server Browser service uses UDP
1521	TCP/UDP	TCP/UDP to listen for database connections from Oracle clients
3306	TCP/UDP	TCP/UDP for MySQL
5432	TCP	TCP for PostgreSQL
123	NTP	Connection from the library to an external NTP server.
445	TCP	Server Message Block (SMB) protocol over TCP/IP

LM Collector's monitoring protocols support a number of other monitoring protocols that can be incorporated into this list based on your preferences. Our LM collector supports a number of different monitoring protocols, so we can add to this list as necessary.

Hopefully, through these details shared above, we will be able to understand what ports/protocols are used in LM platform. Thanks!