Install & Run StreamOps Standalone Image

This quickstart will take you though downloading, installing, and running Octal's StreamOps all the way through connecting to a Kafka streaming service and using StreamOps powerful features.

Requirements

StreamOps requires a JDBC compatible database, such as MySQL or Postgres. Create a database in this instance with write access for the StreamOps user.

Docker Images

StreamOps is published as two docker images hosted on docker hub.

The first is the main StreamOps application which includes the UI. The second is the streamops-worker application which processes pipelines and metrics. If you don't intend to use that functionality or are using the open source version then you do not need the second image.

Launch the StreamOps application using the following command:

docker run octaldata:streamops -e OCTAL_JDBC_URL=<connection string>

Where connection string is a JDBC format url pointing to your database, for example, jdbc:mysql://db.myhost:3306

Launch the StreamOps worker application using the following command:

docker run octaldata:streamops-worker -e OCTAL_JDBC_URL=<connection string>

Docker Compose

By using the below docker compose file you can run docker with a mysql instance. Save this file to docker-compose.yml

version: '3'
services:

  streamops:
    depends_on:
      - mysql
    image: octaldata/streamops:1.0.33
    environment:
      OCTAL_JDBC_URL: jdbc:mysql://mysql:3306/mysql
      OCTAL_JDBC_PASSWORD: root
    ports:
      - "39854:39854"
    expose:
      - 39854
    command: ["sleep", "60"]
    
  mysql:
    image: mysql
    environment:
      MYSQL_ROOT_PASSWORD: root

After saving this to docker-compose.yml run the following in the same directory as the docker-compose.yml

docker-compose up

You should now be able to hit your streamops instance with a browser on localhost:39854 Reminder: When using streamops this way your configuration setting stored in the mysql db will not last over a docker restart. This setup is only for testing purposes. If you are deploying a production instance please use a production mysql instance.