This is a simple example of an OverOps SaaS deployment using a Remote Collector and load balancing those collectors internally. The docker-compose.yml
contains the following services:
collector-1
- an OverOps Collector running in a dedicated container (aka Remote Collector)collector-2
- an OverOps Collector running in a dedicated container (aka Remote Collector)agent
- an OverOps Agent and sample event generator app
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 value for TAKIPI_SECRET_KEY
.
TAKIPI_SECRET_KEY=your-very-own-overops-secret-key
TAKIPI_MASTER_ENDPOINTS=collector-1:6061,collector-2:6062
docker-compose up
docker-compose down
- Remote Collector - timveil/oo-docker-remote-collector
- Agent - timveil/oo-docker-agent