Installing Trendz Analytics using Docker (Linux, macOS)

This guide explains how to install and run Trendz Analytics using Docker on Linux or macOS.

Hardware: Minimum 4 GB of RAM and 2 CPU cores. In small and medium deployments, Trendz can be installed on the same server as ThingsBoard.

Software:

• ThingsBoard 4.3.0 or newer. For older versions see Connecting to ThingsBoard 4.2 and Older.
• Active Trendz Analytics add-on. See the Self-Managed Activation guide.

• Docker CE and Docker Compose installed.

Trendz Analytics can be installed in two ways:

• Run alongside ThingsBoard PE — recommended. Trendz shares the same docker-compose.yml and PostgreSQL instance as ThingsBoard PE.
• Standalone — Trendz runs independently with its own PostgreSQL. Use this if you are not running ThingsBoard PE on the same host or prefer a fully isolated setup.

nano docker-compose.yml

services:
  trendz:
    restart: always
    image: "thingsboard/trendz:1.15.1"
    ports:
      - "8888:8888"
    environment:
      SPRING_DATASOURCE_URL: jdbc:postgresql://trendz-postgres:5432/trendz
      SPRING_DATASOURCE_USERNAME: postgres
      SPRING_DATASOURCE_PASSWORD: postgres
      SCRIPT_ENGINE_DOCKER_PROVIDER_URL: trendz-python-executor:8181
      SCRIPT_ENGINE_TIMEOUT: 30000
    volumes:
      - trendz-conf:/trendz-config-files
      - trendz-data:/data
    depends_on:
      - trendz-postgres
  trendz-python-executor:
    restart: always
    image: "thingsboard/trendz-python-executor:1.15.1"
    ports:
      - "8181:8181"
    environment:
      EXECUTOR_MANAGER: 1
      EXECUTOR_SCRIPT_ENGINE: 6
      THROTTLING_QUEUE_CAPACITY: 10
      THROTTLING_THREAD_POOL_SIZE: 6
      NETWORK_BUFFER_SIZE: 5242880
    volumes:
      - trendz-python-executor-conf:/python-executor-config-files
      - trendz-python-executor-data:/data
  trendz-postgres:
    restart: always
    image: "postgres:16"
    ports:
      - "5432:5432"
    environment:
      POSTGRES_DB: trendz
      POSTGRES_PASSWORD: postgres
    volumes:
      - trendz-postgres-data:/var/lib/postgresql/data
volumes:
  trendz-conf:
    name: trendz-conf
    driver: local
  trendz-data:
    name: trendz-data
    driver: local
  trendz-python-executor-conf:
    name: trendz-python-executor-conf
    driver: local
  trendz-python-executor-data:
    name: trendz-python-executor-data
    driver: local
  trendz-postgres-data:
    name: trendz-postgres-data
    driver: local

docker compose up -d && docker compose logs -f trendz

After installation, verify that Trendz has successfully connected to ThingsBoard. This step is required regardless of how you installed Trendz.

Log in to ThingsBoard as a Sysadmin and open the Trendz Settings page.

If you see “Synchronization completed successfully”, no further action is needed.

Log in to ThingsBoard as a Sysadmin. Open the Trendz Settings page. If you see "Synchronization completed successfully", no further action is required.

If you see an error message:

1. Make sure Trendz is running.
2. Enter the correct Trendz internal URL (must be reachable from ThingsBoard).
3. Enter the correct ThingsBoard internal URL (must be reachable from Trendz).
4. Click Save configuration.
5. Click Retry discovery.

If you see an error message, follow these steps. Enter the correct Trendz internal URL and ThingsBoard internal URL. Click Save configuration. Click Retry discovery. Once "Synchronization completed successfully" appears, the synchronization is complete.

Access Trendz UI at http://localhost:8888.

Trendz uses ThingsBoard as its authentication provider — log in with your Tenant Administrator credentials from ThingsBoard.

After the first login, discover the topology so Trendz can learn about your assets, devices, profiles, and relations:

Click the Discover Topology button to start the topology discovery process. Click the Finish button to close the topology discovery page and unlock the main Trendz functionality.

See Business Entities for more on how Trendz uses this topology.

Detach from the log stream without stopping the container: press Ctrl-p then Ctrl-q.

See the Upgrade Instructions for detailed steps.

If you see errors like:

127.0.1.1:53: cannot unmarshal DNS message

Configure your system to use Google public DNS. See the Linux or macOS instructions.