Run a sample pipeline

Padas UI, the console, and the Motion Engine (console: Cores; tree: core/) are already running from Install Padas Motion. This page registers the engine in the console, imports a sample registry, deploys source → task → sink, and checks traffic on a loopback TCP helper.

Lookup is optional. Do not install or enable it for this TCP loopback sample. Enrichment later: Enable lookup enrichment.

Sample source/sink script

Here's a sample Python script to act as both source and sink for demo purposes: padas_tcp_quickstart_server.py is one process: it sends synthetic syslog-style lines to the engine source listener (8080) and accepts the sink connector’s outbound TCP session (8081). Keep it running through import, assign, and validation. Until the pipeline is running, expect retry noise.

You need python3 on the engine host. Ports 8080 and 8081 are for this helper only.

1. Sign in

Open https://<host>:9000. Sign in with the administrator created at install.

If you skipped first-boot setup, the sign-in page shows System Not Initialized. Use the banner to create the administrator. Bootstrap and roles: Users, roles & permissions.

First run: create the administrator from the banner when it appears.

2. Confirm the Motion Engine in the console

If you followed Install Padas Motion, the engine is already under Services → Cores and Enroll should show Enrolled. Open that page and confirm host / port (often localhost / 8999).

If the row is missing, Create it, then Enroll code and run padas enroll on the engine host before continuing.

Services → Cores: Motion Engine inventory and enroll status.

Create New Core: name, host, and port; use Add description for operational notes.

Field	Value
Core Name	Unique, human-readable label for this Motion Engine.
Host	Address the console can reach (often localhost or 127.0.0.1 on a single-node host).
Port	8999.
Description	Optional.

Naming patterns: Naming conventions.

3. Start the TCP helper

Run this on the engine host so 127.0.0.1:8081 matches the sample sink. Copy:

• Registry: padas-registry-quickstart.json
• Helper: padas_tcp_quickstart_server.py

python3 padas_tcp_quickstart_server.py

Startup banner:

Padas TCP quickstart helper

Padas source connector (syslog TCP) should listen on:
  Host: 0.0.0.0 (or reachable bind)  Port: 8080

This script sends synthetic lines to:
  127.0.0.1:8080

Padas sink connector should connect to:
  address 127.0.0.1  port 8081  (engine process → loopback)

This script listens for sink TCP on:
  0.0.0.0:8081

If the engine is on another host, set PADAS_TCP_SOURCE_HOST and make 8081 reachable from the engine (or change connector endpoints after import). Optional: PADAS_TCP_SOURCE_PORT, PADAS_TCP_SINK_BIND, PADAS_TCP_SINK_PORT, PADAS_QUICKSTART_EVENT_INTERVAL_SEC (script header).

4. Import the registry

Open Pipelines, Upload, and select padas-registry-quickstart.json.

Pipelines → Upload: import the quickstart registry JSON.

5. Deploy

Open Management → Pipelines, select the imported pipeline, Deploy, choose your Core (the registered Motion Engine), and confirm. Deploy silent-binds membership and pushes the pipeline’s constituents to the engine.

Management → Pipelines: Deploy the quickstart pipeline to the registered Core.

6. Validate

On Home, confirm pipe-quickstart-main shows source → task → sink in a healthy state.

After Deploy: pipe-quickstart-main with source → stream → task → stream → sink healthy.

In the helper terminal, look for [SINK] lines. The sample task filters aggressively; [SOURCE] without [SINK] can mean waiting for a matching login-style event.

[SINK] <14>May 11 07:46:29 - -: {"action":"login","custom_field":"Yey, this is my first task!",...}

Troubleshooting

Troubleshooting & Logs → Run a sample pipeline

Where next

Enable lookup enrichment (optional) · Next steps