autodock based Docker Compose for Prometheus monitoring

docker-compose.yml

autodock:
    image: prologic/autodock
    ports:
        - "1338:1338/udp"
        - "1338:1338/tcp"
    volumes:
        - /var/run/docker.sock:/var/run/docker.sock
    restart: always

autodockhipache:
    image: prologic/autodock-hipache
    links:
        - autodock
        - hipache:redis
    restart: always

promserver:
    image: prom/prometheus
    volumes:
        - /home/prologic/etc/prometheus.yml:/prometheus.yml
    environment:
        - PORT=9090
        - VIRTUALHOST=prometheus.vz1.bne.shortcircuit.net.au
    command: -config.file=/prometheus.yml
    restart: always

promexporter:
    image: prom/container-exporter
    volumes:
        - /sys/fs/cgroup:/cgroup
        - /var/run/docker.sock:/var/run/docker.sock
    environment:
        - PORT=9104
        - VIRTUALHOST=metrics.vz1.bne.shortcircuit.net.au
    restart: always

hipache:
    image: hipache:0.2.8
    ports:
        - "80:80"
        - "443:443"
    restart: always

promesthesus.yml

global:
  scrape_interval: 15s
  evaluation_interval: 15s
  labels:
    monitor: exporter-metrics

scrape_configs:

  - job_name: prometheus
    scrape_interval: 5s

    target_groups:
        - targets: ["localhost:9090", "metrics.vz1.bne.shortcircuit.net.au"]

Based on what I learnedd from: http://rancher.com/docker-monitoring-continued-prometheus-and-sysdig/