mounted-agent-musl

OverOps Mounted Agent Example - Alpine (musl)

This is a simple example of using OverOps to monitor an external Docker image, in this case timveil/oo-docker-event-generator:alpine-musl. 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
• agent - an instance of the event generator app monitored by the OverOps Agent mounted in the sidecar

Keep in mind the OverOps Agent could be installed on the Docker Host and exposed to the agent container as a Docker bind mount.

Getting Started

To begin, you must first create a file called overops-key.env and place it in the same directory as the Dockerfile. Below is a sample overops-key.env file.

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

• Remote Collector - timveil/oo-docker-remote-collector:rootless
• Agent Sidecar - timveil/oo-docker-agent-sidecar:alpine-musl
• Agent - timveil/oo-docker-event-generator:alpine-musl