Skip to content

Commit

Permalink
Prometheus example configuration
Browse files Browse the repository at this point in the history
Assuming that MongoosePush was started with the following command:

    MIX_ENV=integration mix do test.env.up

You can start Prometheus configured to monitor MongoosePush in container
executing the command below:

    docker-compose -f test/docker/docker-compose.prometheus.yml up -d
  • Loading branch information
michalwski committed Jun 10, 2020
1 parent f3f0285 commit 8c7be7d
Show file tree
Hide file tree
Showing 2 changed files with 21 additions and 0 deletions.
12 changes: 12 additions & 0 deletions test/docker/docker-compose.prometheus.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
# This file needs to be used along with `docker-compose.mocks.yml` and `docker-compose.mpush.yml:
# docker-compose -f test/docker/docker-compose.mocks.yml -f test/docker/docker-compose.mpush.yml -f test/docker/docker-compose.prometheus.yml ...
version: '3'

services:
prometheus:
image: prom/prometheus
container_name: mongoose-push-prometheus
ports:
- "9090:9090"
volumes:
- ./prometheus.yml:/etc/prometheus/prometheus.yml
9 changes: 9 additions & 0 deletions test/docker/prometheus.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
scrape_configs:
- job_name: 'mongoose-push'
scheme: 'https' #MongoosePush exposes encrypted endpoint - HTTPS
tls_config: #The default certs used by MongoosePush are self-signed
insecure_skip_verify: true #For checking purposes we can ignore certs verification
static_configs:
- targets: ['mongoose-push:8443']
labels:
group: 'production'

0 comments on commit 8c7be7d

Please sign in to comment.