github.com/m3db/m3@v1.5.1-0.20231129193456-75a402aa583b/scripts/development/m3_prom_remote_stack/prometheus-scraper.yml (about)

     1  global:
     2    external_labels:
     3      role: "remote"
     4    scrape_interval:     10s
     5    evaluation_interval: 10s
     6  
     7  # Alertmanager configuration
     8  alerting:
     9    alertmanagers:
    10      - static_configs:
    11          - targets:
    12            # - alertmanager:9093
    13  
    14  # Load rules once and periodically evaluate them according to the global 'evaluation_interval'.
    15  rule_files:
    16  # - "first_rules.yml"
    17  # - "second_rules.yml"
    18  
    19  remote_write:
    20    - url: http://m3coordinator01:7201/api/v1/prom/remote/write
    21      remote_timeout: 30s
    22  
    23  # A scrape configuration containing exactly one endpoint to scrape:
    24  # Here it's Prometheus itself.
    25  scrape_configs:
    26    # The job name is added as a label `job=<job_name>` to any timeseries scraped from this config.
    27    - job_name: 'prometheus'
    28      static_configs:
    29        - targets: ['prometheusagg:9090', 'prometheusraw:9090']
    30  
    31    - job_name: 'coordinator'
    32      static_configs:
    33        - targets:
    34            - m3coordinator01:7203
    35  
    36    - job_name: 'aggregator'
    37      static_configs:
    38        - targets: ['m3aggregator01:6002']