Communication link

The communication between lmio-collector and lmio-receiver is named "commlink", short for the Communication Link.

The websocket is used as a primary communication protocol but HTTPS calls from the collector are also utilized. The collector keeps the websocket connection to the receiver open for a long period of a time. When the communication link from the collector is terminated, the collector tries to reconnect periodically.

Note

Websocket connection utilizes server-side generated PING packets to keep the websocket open.

The Communication Link is protected by the mutual SSL authorization. It means that each lmio-collector is equipped by the private key and the client SSL certificate. The private key and the client SSL certificate is generated automatically during provisioning of the new collector. The private key and the client SSL certificate are used to authenticate the collector. This mechanism also provide a strong encryption of the traffic between the collector and the central part of the LogMan.io.

Production setup

The production setup is that LogMan.io Collector (lmio-collector) connects over HTTPS via NGINX server to LogMan.io Receiver (lmio-receiver).

graph LR
  lmio-collector -- "websocket & SSL" --> n[NGINX]
  n[NGINX] --> lmio-receiver

Diagram: Production setup

For more info, continue to the NGINX section.

Non-production setup

The direct connection from lmio-collector to lmio-receiver is also supported. It is suitable for non-production setups such as testing or development.

graph LR
  lmio-collector -- "websocket & SSL" --> lmio-receiver

Diagram: Non-production setup