Live Platform
  • Introduction
  • Release Notes
    • Live 3
      • 3.59.0
      • 3.58.0
      • 3.57.0
      • 3.56.0
      • 3.55.0
      • 3.54.0
      • 3.53.0
      • 3.52.0
      • 3.51.0
      • 3.50.0
      • 3.49.0
      • 3.48.0
      • 3.47.0
      • 3.46.0
      • 3.45.0
      • 3.44.0
      • 3.43.0
      • 3.42.0
      • 3.41.0
      • 3.40.0
      • 3.39.0
      • 3.38.0
      • 3.37.0
      • 3.36.0
      • 3.35.0
      • 3.34.0
      • 3.33.0
      • 3.32.0
      • 3.31.0
      • 3.30.0
      • 3.29.0
      • 3.28.0
      • 3.27.0
      • 3.26.0
      • 3.25.0
      • 3.24.0
      • 3.23.0
      • 3.22.0
      • 3.21.0
      • 3.20.0
      • 3.19.0
      • 3.18.0
      • 3.17.0
      • 3.16.0
      • 3.15.0
      • 3.14.0
      • 3.13.0
      • 3.12.0
      • 3.11.0
      • 3.10.0
      • 3.9.0
      • 3.8.0
      • 3.7.0
      • 3.6.0
      • 3.5.0
      • 3.4.0
      • 3.3.0
      • 3.2.0
      • 3.1.0
      • 3.0.0
    • Live 2
  • Articles
    • Creating an aggregation
    • Creating a pipe
  • Theoretical Background
    • Fundamentals
    • Key Advantages
  • Platform Architecture
    • Introduction
    • Queries
    • Glossary
  • Featured plugins
    • Annotations
    • Groovy support
    • Messenger
    • Microsoft Teams
    • MongoDB
    • MongoDB Timeseries
    • MongoDB Kit
    • Purge plugin
    • SQL
    • TCP Input
    • TimescaleDB
  • Data visualization
    • Pipes widgets
      • Temporal
      • Cartesian
      • Multi-value snapshot
      • Single-value snapshot
      • Tables
      • Heatmap
      • JSX Widgets
      • Lollipop
      • Histogram
      • State Timeline
      • Boxplot
    • Pipes modifiers on Pipes charts
  • Alerts and notifications
    • Pipes modifiers on rules
  • Pipes Queries
    • Introduction
    • Dynamic filters
    • Meta parameters
    • Reducer
      • Uniform compress
      • PIP
    • Storage Hints
    • Execution Context
    • Event flow modifiers
  • Developers
    • Plugins
    • Packages
    • Backend API
      • Lookup Tables
      • Extensions
      • Settings
      • Storage Providers
      • Web Services
      • Web Setup
      • Entity Audit
    • Web application
      • Services
        • Point service
        • Menu service
      • Browser Compatibility
      • Runtime modules
        • Core Javascript modules
        • Library modules
        • Adding modules to runtime
      • Localization (i18n)
      • Date formatting
      • Dashboard and Widgets
        • Widget API
        • Custom widget editors
        • Live Event Types
        • Live Widget Configuration
        • Live Widget Packaging
        • Widget Request Interceptors
      • React Contexts
        • Dashboard
        • Dashboard widget
      • Registering Home Page options
    • Python application
    • Subscribing to Live Events
  • Administration
    • Configuration
      • Home Page Customization
      • live.properties
    • Infrastructure Monitoring
    • Storage Monitoring
    • Queries Monitoring
    • Logs Monitoring
    • Data Purging
  • Features
    • Access Permission
    • Datasources
    • Export Dashboard
    • Partial Indexes
    • WebApp Metrics
    • Entity Audit
Powered by GitBook
On this page

Was this helpful?

  1. Featured plugins

TCP Input

Enables the data ingestion through a TCP input port

PreviousSQLNextTimescaleDB

Last updated 2 years ago

Was this helpful?

The TCP input plugin is available for download on .

A brief explanation of each parameter:

  • Input port: the TCP port on which it will listen for connections.

  • type field in JSON: when "allow type to be defined in the event" is checked, the field which will have the event type, by default "__type".

  • Default type: the event type to be used if "allow type to be defined in the event" is unchecked, or if the event does not have the field with the event type.

  • Max connections (min version: 2.26.3)

  • Max connections queue size (min version: 2.26.3)

  • Allow type to be defined in the event: when checked, use the field defined as the "type field in JSON" to define the event type.

  • Skip real-time: do not send events received in this connection to real-time queries.

Each of the "allowed addresses" and "denied addresses" fields are a space-separated list of CIDR ranges, for instance, "192.0.2.0/24 198.51.100.0/24 2001:db8::/32". The "deny addresses by default" checkbox controls the order in which the IP address of the connecting peer is checked against these two lists.

If "deny addresses by default" is not checked, a connection is allowed if the IP address of the peer is in the "allowed addresses" list; otherwise, the connection is denied if it is in the "denied addresses" list; otherwise, the connection is allowed.

If "deny addresses by default" is checked, a connection is denied if the IP address of the peer is in the "denied addresses" list; otherwise, the connection is allowed if it is in the "allowed addresses" list; otherwise, the connection is denied.

Let's use this configuration as an example:

Allowed addresses: "192.0.2.0/24 198.51.100.3"

Denied addresses: "192.0.2.10 198.51.100.0/24"

IP

deny addresses by default is not checked

deny addresses by default is checked

192.0.2.10

✔️ allowed

🚫 denied

192.0.2.42

✔️ allowed

✔️ allowed

198.51.100.3

✔️ allowed

🚫 denied

198.51.100.2

🚫 denied

🚫 denied

203.0.113.1

✔️ allowed

🚫 denied

INTELIE Live Marketplace
Example of basic TCP Input configuration
Allowed/Denied addresses list