github.com/m3db/m3@v1.5.0/scripts/development/m3_prom_remote_stack/README.md (about)

     1  # Local Development
     2  
     3  This docker-compose file will setup the following environment:
     4  
     5  1. 1 ETCD
     6  2. 1 M3Coordinator node
     7  3. 1 M3 Aggregator node
     8  4. 2 Prometheus instances with `remote-write-receiver` feature enabled in order to accept remote writes.   
     9  5. 1 Grafana node (with a pre-configured Prometheus source)
    10  6. 1 Prometheus node that scrapes the M3 Components and Prometheus instances. 
    11     In addition, it scrapes CAdvisor /metrics endpoints exposed by using `kubectl proxy`.
    12  
    13  The environment variables that let's you configure this setup are:
    14  - `BUILD_M3AGGREGATOR=true`: forces build of local M3 Aggregator.
    15  - `BUILD_M3COORDINATOR=true`: forces build of local M3 Aggregator.
    16  - `WIPE_DATA=true`: cleans up docker state when using `stop_m3.sh`.
    17  
    18  ## Usage
    19  
    20  Use the `start_m3.sh` and `stop_m3.sh` scripts.
    21  
    22  If you want to scrape CAdvisor metrics from Kubernetes cluster:
    23  - Run `port_forward_kube.sh`
    24  - Run `start_m3.sh`
    25  
    26  ## Grafana
    27  
    28  Use Grafana by navigating to `http://localhost:3000` and using `admin` for both the username and password. The M3DB dashboard should already be populated and working.
    29  
    30  To pickup latest grafana Docker build remove existing image `docker image rm m3grafana --force`.
    31  
    32  ## Containers Hanging / Unresponsive
    33  
    34  Running the entire stack can be resource intensive. If the containers are unresponsive try increasing the amount of cores and memory that the docker daemon is allowed to use.