We could provide a demo/example using a small nameko service that has all the supported entrypoints (RPC, events, HTTP). The service should run as a container.
The compose stack should include RabbitMQ and Prometheus images, without any persistent volumes for simplicity. Prometheus config must include scraping our service's /metrics endpoint (we can bind-mount the config).
Our service should start and call itself regularly/randomly without any input from the user. The goal is to call docker-compose up, navigate to Prometheus UI and observe that service metrics appear there.
We could provide a demo/example using a small nameko service that has all the supported entrypoints (RPC, events, HTTP). The service should run as a container.
The compose stack should include RabbitMQ and Prometheus images, without any persistent volumes for simplicity. Prometheus config must include scraping our service's
/metrics
endpoint (we can bind-mount the config).Our service should start and call itself regularly/randomly without any input from the user. The goal is to call
docker-compose up
, navigate to Prometheus UI and observe that service metrics appear there.