How eodata/operator-setup works
Project type and purpose
• This is a container-orchestration “operator-setup” toolkit for running and monitoring an EO AVS data-validator.
• It combines a CLI wrapper (run.sh) around Docker Compose recipes for two sets of services:
– The EO data-validator microservice
– A Prometheus-Grafana-Node-Exporter-VMAgent monitoring stack
File structure
• Root:
– run.sh: shell wrapper to generate keys, encrypt, register/deregister on the blockchain, and launch containers
– README.md: operator setup guide, CLI commands, docker steps, monitoring setup
• data-validator/
– .example_env, .example_env_holesky → environment variable templates for the validator
– docker-compose.yml → defines the validator container and its dependencies (ports, volumes)
– dashboards/ → Grafana JSON dashboard definitions for validator and node-exporter
– monitoring/ → nested docker-compose.yml plus configuration for Prometheus, Grafana, VMAgent, Node-Exporter
• Key patterns:
– Docker Compose for grouping related containers
– Separate Compose files for “validator” and “monitoring” stacks
– Environment-driven configuration via .env files
Extract architectural insights from the README
• The “run.sh” scripts wrap calls to: generate/encrypt keys, invoke EO CLI, spin up/down containers
• Data-validator exposes:
– HTTP health endpoints (port 9000)
– Prometheus metrics (port 9100)
– Data port (9200, V2)
– Subscribes to external WS feeds (Coinbase, Bybit, BitMart, Gate.io)
– Posts signed transactions to the EO chain RPC endpoint
• Monitoring stack:
– Prometheus scrapes validator metrics and Node-Exporter
– Grafana reads from Prometheus (datasource on port 9090) and offers prebuilt dashboards
– VMAgent optionally aggregates and forwards metrics