tcp-logger

Description

The tcp-logger Plugin can be used to push log data requests to TCP servers.

This provides the ability to send log data requests as JSON objects to monitoring tools and other TCP servers.

This plugin also allows to push logs as a batch to your external TCP server. It might take some time to receive the log data. It will be automatically sent after the timer function in the batch processor expires.

Attributes

NameTypeRequiredDefaultValid valuesDescription
hoststringTrueIP address or the hostname of the TCP server.
portintegerTrue[0,…]Target upstream port.
timeoutintegerFalse1000[1,…]Timeout for the upstream to send data.
log_formatobjectFalseLog format declared as key value pairs in JSON format. Values only support strings. APISIX or Nginx variables can be used by prefixing the string with $.
tlsbooleanFalsefalseWhen set to true performs SSL verification.
tls_optionsstringFalseTLS options.
include_req_bodybooleanFalsefalseWhen set to true includes the request body in the log.

This Plugin supports using batch processors to aggregate and process entries (logs/data) in a batch. This avoids the need for frequently submitting the data. The batch processor submits data every 5 seconds or when the data in the queue reaches 1000. See Batch Processor for more information or setting your custom configuration.

Metadata

You can also set the format of the logs by configuring the Plugin metadata. The following configurations are available:

NameTypeRequiredDefaultDescription
log_formatobjectFalse{“host”: “$host”, “@timestamp”: “$time_iso8601”, “client_ip”: “$remote_addr”}Log format declared as key value pairs in JSON format. Values only support strings. APISIX or Nginx variables can be used by prefixing the string with $.
tcp-logger - 图1IMPORTANT

Configuring the Plugin metadata is global in scope. This means that it will take effect on all Routes and Services which use the tcp-logger Plugin.

The example below shows how you can configure through the Admin API:

  1. curl http://127.0.0.1:9180/apisix/admin/plugin_metadata/tcp-logger -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
  2. {
  3.     "log_format": {
  4.         "host": "$host",
  5.         "@timestamp": "$time_iso8601",
  6.         "client_ip": "$remote_addr"
  7.     }
  8. }'

With this configuration, your logs would be formatted as shown below:

  1. {"@timestamp":"2023-01-09T14:47:25+08:00","route_id":"1","host":"localhost","client_ip":"127.0.0.1"}

Enabling the Plugin

The example below shows how you can enable the tcp-logger Plugin on a specific Route:

  1. curl http://127.0.0.1:9180/apisix/admin/routes/5 -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
  2. {
  3.       "plugins": {
  4.             "tcp-logger": {
  5.                  "host": "127.0.0.1",
  6.                  "port": 5044,
  7.                  "tls": false,
  8.                  "batch_max_size": 1,
  9.                  "name": "tcp logger"
  10.             }
  11.        },
  12.       "upstream": {
  13.            "type": "roundrobin",
  14.            "nodes": {
  15.                "127.0.0.1:1980": 1
  16.            }
  17.       },
  18.       "uri": "/hello"
  19. }'

Example usage

Now, if you make a request to APISIX, it will be logged in your TCP server:

  1. curl -i http://127.0.0.1:9080/hello

Disable Plugin

To disable the tcp-logger Plugin, you can delete the corresponding JSON configuration from the Plugin configuration. APISIX will automatically reload and you do not have to restart for this to take effect.

  1. curl http://127.0.0.1:9180/apisix/admin/routes/1 -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
  2. {
  3.     "methods": ["GET"],
  4.     "uri": "/hello",
  5.     "plugins": {},
  6.     "upstream": {
  7.         "type": "roundrobin",
  8.         "nodes": {
  9.             "127.0.0.1:1980": 1
  10.         }
  11.     }
  12. }'