Recently, a system of the company was recommended by users to expand the scope of use, which was originally a good thing, but I did not expect that the number of system users skyrocketed in a short period of time, making the problems of the original system frequent, and the problems that had never been heard of when used in a small range showed explosive growth. More deadly is user of the system is deployed in Intranet, development and operations teams to access it is very difficult, several times is a response to a user in the group, our development and operations staff realized, plus access server is not very convenient, need special approval, head of the user to obtain the corresponding permissions, spent a long time to locate and fix the problem, Customer satisfaction has also decreased. So in order to solve the current predicament, on the one hand, to arrange the r&d team ruled out potential problems, on the one hand, considering the user’s special situation and system expansion, sure it is time to set up a set of monitoring system, the purpose is to happen in the system or impending problems immediately notified in action, maximum limit reduce problems brought about by the impact. So the monitoring system construction action began, the first is to analyze the status quo. 1) The system is deployed on the user Intranet and cannot connect to the Internet. 2) All the machines of the legacy system are Windows. 3) The application of the legacy system should avoid modification as far as possible, because the R&D team has already engaged in another line of fire.

1. Download Prometheus from the download address
2. Unpack the
3. Modify the Prometheus. Yml,
4. Run Prometheus. exe –config.file=prometheus.yml as an administrator

Prometheus. Yml example

# 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).

# Load rules once and periodically evaluate them according to the global 'evaluation_interval'.
rule_files:
  # - "first_rules.yml"
  # - "second_rules.yml"

# 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']
Copy the code

The schematic diagram of normal startup is as follows:

The data collection component is up to you

Mysql-half is a mysql monitoring terminal. You need to set the account and permissions of mysql to operate normally.

1. Download the exporter, url
2. Configure database users and permissionsCREATE USER 'exporter'@'localhost' IDENTIFIED BY 'XXXXXXXX' WITH MAX_USER_CONNECTIONS 3; GRANT PROCESS, REPLICATION CLIENT, SELECT ON *.* TO 'exporter'@'localhost';
3. Set environment variable DATA_SOURCE_NAME= ‘user:password@(hostname:3306)/’
4. Start the exporter,./mysqld_exporter <flags>The default port looks like 9104

Update Prometheus configuration based on your monitoring items

# 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).

# Load rules once and periodically evaluate them according to the global 'evaluation_interval'.
rule_files:
  # - "first_rules.yml"
  # - "second_rules.yml"

# 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: 'mysql-metrics'
   #   metrics_path: '/actuator/prometheus'
    scrape_interval: 5s
    static_configs:
      - targets: ['localhost:9104']
        labels:
          instance: db1
  - job_name: pushgateway
    static_configs:
      - targets: ['localhost:9091']
        labels:
          instance: pushgateway
  - job_name: jmx
    static_configs:
      - targets: ['localhost:9092']
Copy the code

Then you can go to LocalHost :3000 and create a dashboard to tap into Prometheus data and customize your interface with your own ideas. Not to say the least, it’s a good idea to start by looking for templates, deleting, deleting, and editing. As shown below.