Skip to content

Latest commit

 

History

History
37 lines (30 loc) · 1.63 KB

README.md

File metadata and controls

37 lines (30 loc) · 1.63 KB

OverOps NiFi Example

This is a simple example of using OverOps to monitor an external Docker image, in this case NiFi. Instead of specifying the agentlib inside the container during as a JVM startup flag, this example uses the JAVA_TOOL_OPTIONS environment variable to auto attach to any JVM launched inside the container. The docker-compose.yml contains the following services:

  • collector - an OverOps Collector running in a dedicated container (aka Remote Collector)
  • sidecar - an OverOps Agent running in a dedicated container whose directory is exposed as a Docker volume mount
  • nifi - an instance of NiFi monitored by an OverOps Agent mounted on the Docker host

Getting Started

To begin, you must first create a overops-key.env file and place it in the same directory as the Dockerfile. Below is a sample overops-key.env file. Be sure to update the values for TAKIPI_SECRET_KEY.

overops-key.env

TAKIPI_SECRET_KEY=your-very-own-overops-secret-key

overops-agent.env

JAVA_TOOL_OPTIONS=-agentpath:/sidecar/lib/libTakipiAgent.so
TAKIPI_COLLECTOR_HOST=collector
TAKIPI_COLLECTOR_PORT=6060

Docker Compose

Start the Containers

docker-compose up

Stop and Destroy the Containers

docker-compose down

Docker Images