This page describes the steps to setup set up a Prometheus monitoring server to obtain metrics data from your deployment.
...
Download the latest LTS release of Prometheus for your operating system from Download | Prometheus.
Extract the binaries. Please For more information, refer to Getting started | Prometheus docs for details.
Setup with example Prometheus configuration file
Go to the extracted Prometheus directory.
Code Block cd prometheus-*
Create a yaml file named
prometheus_mz.yaml
as follows.Code Block # my global config global: scrape_interval: 15s # Set the scrape interval to every 15 seconds. Default is every 1 minute. evaluation_interval: 15s # Evaluate rules every 15 seconds. The default is every 1 minute. # scrape_timeout is set to the global default (10s). # A scrape configuration containing exactly one endpoint to scrape: # Here it's Prometheus itself. scrape_configs: # The job name is added as a label `job=<job_name>` to any timeseries scraped from this config. #- job_name: 'prometheus' # # metrics_path defaults to '/metrics' # # scheme defaults to 'http'. # static_configs: # - targets: ['localhost:9090'] - job_name: 'mz' static_configs: - targets: ['localhost:8888'] # port defined in the topo STR config labels: pico: 'platform' - targets: ['localhost:9090'] # port defined in the topo STR config labels: pico: 'ec1'
...
Create a yaml file named
jmxExport.yml
as follows.
For more information on the yaml file, refer to jmx_exporter/docs at main · prometheus/jmx_exporter (github.com).Code Block startDelaySeconds: 0 ssl: false lowercaseOutputName: false lowercaseOutputLabelNames: false
Add the following
jvmargs
to theplatform topo
configuration:.Code Block $ mzsh topo set topo://container:main1/pico:platform/obj:config.jvmargs.args \ '["-javaagent:common/lib/jmx_prometheus_javaagent.jar=8888:<path>/jmxExporter.yaml"]'
Restart the Platform.
Code Block $ mzsh restart platform
...