[转帖]prometheus数据采集exporter全家桶

prometheus数据采集exporter全家桶

Rainbowhhy1人评论2731人阅读2019-04-06 15:38:32

https://blog.51cto.com/13053917/2374734

1. exporter介绍

exporter是prometheus监控中重要的组成部分，负责数据指标的采集。上篇文章介绍了prometheus server的相关内容，本文将介绍数据采集插件。官方给出的插件有node_exporter、blackbox_exporter、mysqld_exporter、snmp_exporter等，第三方的插件有redis_exporter，cadvisor等。
下面我将结合实际工作中的使用到的插件来分别介绍。

2. node_exporter

node_exporter主要用来采集机器的性能指标数据，包括cpu，内存，磁盘，io等基本信息。上边文章介绍promehteus server时已详细介绍了node_exporter，这里就不在赘述。

3. mysqld_exporter

mysqld_exporter主要用于监控采集mysql数据库服务器相关指标。
#下载二进制文件

[email protected]100-51:~# cd /data/
[email protected]100-51:/data# wget https://github.com/prometheus/mysqld_exporter/releases/download/v0.10.0/mysqld_exporter-0.10.0.linux-amd64.tar.gz
[email protected]100-51:/data#  tar -xf mysqld_exporter-0.10.0.linux-amd64.tar.gz
[email protected]100-51:/data# cd mysqld_exporter-0.10.0/
[email protected]100-51:/data/mysqld_exporter-0.10.0# ls
LICENSE  mysqld_exporter  NOTICE
[email protected]100-51:/data#  mkdir log

#mysqld_exporter需要连接到数据库，创建一个登录数据库的用户

mysql> GRANT PROCESS, REPLICATION CLIENT, SELECT ON *.* TO ‘exporter‘@‘localhost‘ identified by Cds20180808!‘;
mysql> flush privileges;

#创建用于连接数据库的配置文件

[email protected]100-51:/data/mysqld_exporter-0.10.0# vim .my.cnf
[client]
user=exporter
password=Cds20180808!

#创建supervisor启动mysqld_exporter

[email protected]:/data/mysqld_exporter-0.10.0# vim /etc/supervisor/conf.d/mysqld_exporter.conf
[program:mysqld_exporter]
command = /data/mysqld_exporter-0.10.0/mysqld_exporter -config.my-cnf="/data/mysqld_exporter-0.10.0/.my.cnf"
autostart = true
autorestart = true
startsecs = 5
startretries = 3
redirect_stderr = true
stdout_logfile=/data/mysqld_exporter-0.10.0/log/out-mysqld_exporter.log
stderr_logfile=/data/mysqld_exporter-0.10.0/log/err-mysqld_exporter.log
stdout_logfile_maxbytes = 20MB
stdout_logfile_backups = 20

#启动mysqld_exporter

[email protected]100-51:/data/mysqld_exporter-0.10.0# supervisorctl update mysqld_exporter
[email protected]100-51:/data/mysqld_exporter-0.10.0# supervisorctl status mysqld_exporter

4. redis_exporter

redis_exporter主要用于监控采集redis数据库服务器相关指标。
#下载二进制文件

[email protected]:~# cd /data/ wget https://github.com/oliver006/redis_exporter/releases/download/v0.24.0/redis_exporter-v0.24.0.linux-amd64.tar.gz
[email protected]:/data# tar -xf redis_exporter-v0.24.0.linux-amd64.tar.gz
[email protected]:/data# mkdir /data/redis_exporter-v0.24.0
[email protected]:/data# mv redis_exporter redis_exporter-v0.24.0
[email protected]:/data# cd redis_exporter-v0.24.0/
[email protected]:/data/redis_exporter-v0.24.0# mkdir log

#配置supervisor启动redis_exporter

[email protected]:/data/redis_exporter-v0.24.0# vim /etc/supervisor/conf.d/redis_exporter.conf
[program:redis_exporter]
command = /data/redis_exporter-v0.24.0/redis_exporter -redis.addr 10.13.225.112:6379 -redis.password cds-china
autostart = true
startsecs = 5
startretries = 3
redirect_stderr = true
stout_logfile = /data/redis_exporter-v0.24.0/log/out-redis_exporter.log
stderr_logfile = /data/redis_exporter-v0.24.0/log/err-redis_exporter.log
stdout_logfile_maxbytes = 20MB
stdout_logfile_backups = 20

#启动redis_exporter

[email protected]slave:/data/redis_exporter-v0.24.0# supervisorctl update redis_exporter
[email protected]:/data/redis_exporter-v0.24.0# supervisorctl status redis_exporter

5. black_exporter

black_exporter是prometheus社区提供的官方黑盒监控解决方案，其允许用户通过：http、https、dns、tcp以及icmp的方式对网络进行探测。我们利用icmp探针可以坚持网络是否通畅，利用http，https可以坚持网页是否可以正常访问，利用tcp检测服务端口判断服务是否正常。
#下载二进制文件

[email protected]:~# cd /data/
[email protected]:/data# wget https://github.com/prometheus/blackbox_exporter/releases/download/v0.13.0/blackbox_exporter-0.13.0.linux-amd64.tar.gz
[email protected]:/data# tar -xf blackbox_exporter-0.13.0.linux-amd64.tar.gz

#修改blackbox_exporter配置文件

[email protected]:/data# cd blackbox_exporter-0.13.0/
[email protected]:/data/blackbox_exporter-0.13.0# vim blackbox.yml
modules:
  http_2xx:
    prober: http
    timeout: 5s
    http:
      preferred_ip_protocol: "ip4"
      no_follow_redirects: true
      valid_http_versions: ["HTTP/1.1", "HTTP/2"]
      valid_status_codes: [200,302]  # Defaults to 2xx
      method: GET
  http_post_2xx:
    prober: http
    http:
      method: POST
  tcp_connect:
    prober: tcp
    timeout: 5s
  pop3s_banner:
    prober: tcp
    tcp:
      query_response:
      - expect: "^+OK"
      tls: true
      tls_config:
        insecure_skip_verify: false
  ssh_banner:
    prober: tcp
    timeout: 5s
    tcp:
      query_response:
      - expect: "^SSH-2.0-"
  irc_banner:
    prober: tcp
    tcp:
      query_response:
      - send: "NICK prober"
      - send: "USER prober prober prober :prober"
      - expect: "PING :([^ ]+)"
        send: "PONG ${1}"
      - expect: "^:[^ ]+ 001"
  icmp:
    prober: icmp
    timeout: 5s

#配置systemd启动blackbox_exporter

[email protected]:/data/blackbox_exporter-0.13.0# vim /usr/lib/systemd/system/blackbox_exporter.service 

[Unit]
Description=Prometheus blackbox exporter
After=local-fs.target network-online.target network.target
Wants=local-fs.target network-online.target network.target

[Service]
User=root
Type=simple
WorkingDirectory=/data/blackbox_exporter-0.13.0/
ExecStart=/data/blackbox_exporter-0.13.0/blackbox_exporter --config.file=/data/blackbox_exporter-0.13.0/blackbox.yml
Restart=on-failure

[Install]
WantedBy=multi-user.target
[email protected]:/data/blackbox_exporter-0.13.0# supervisorctl start blackbox_exporter
[email protected]:/data/blackbox_exporter-0.13.0# supervisorctl enable blackbox_exporter
[email protected]:/data/blackbox_exporter-0.13.0# supervisorctl status blackbox_exporter

6. cadvisor

cadvisor是google开源的用于监控容器运行的工具。
#下载二进制文件

[email protected]:~# cd /data/
[email protected]:/data# wget https://github.com/google/cadvisor/releases/download/v0.33.0/cadvisor
[email protected]:/data# mkdir cadvisor-v0.33.0
[email protected]:/data# mv cadvisor cadvisor-v0.33.0/
[email protected]:/data# cd cadvisor-v0.33.0/
[email protected]:/data/cadvisor-v0.33.0# mkdir log

#配置supervisor启动cadvisor

[email protected]:/data/cadvisor-v0.33.0# vim /etc/supervisor/conf.d/cadvisor-server.conf
[program:cadvisor-server]
command = /data/cadvisor-v0.33.0/cadvisor
autostart = true
autorestart = true
startsecs = 5
startretries = 3
redirect_stderr = true
stdout_logfile=/data/cadvisor-v0.33.0/log/out-cadvisor.log
stderr_logfile=/data/cadvisor-v0.33.0/log/err-cadvisor.log
stdout_logfile_maxbytes = 20MB
stdout_logfile_backups = 20
[email protected]:/data/cadvisor-v0.33.0# supervisorctl update cadvisor
[email protected]:/data/cadvisor-v0.33.0# supervisorctl status cadvisor

7. 配置prometheus服务端

上面布置了exporter，我们需要配置prometheus server来拿到exporter采集到数据。
#修改pormetheus配置文件，配置文件上篇文章已经介绍了，这里就不在解释

[email protected]:~# cd /data/prometheus-2.4.3/
[email protected]:/data/prometheus-2.4.3# vim prometheus.yml
#my global config
global:
  scrape_interval:     30s # Set the scrape interval to every 15 seconds. Default is every 1 minute.
  evaluation_interval: 25s # Evaluate rules every 15 seconds. The default is every 1 minute.
  scrape_timeout: 25s #is set to the global default (10s).

#Alertmanager configuration
alerting:
  alertmanagers:
  - static_configs:
    - targets:
      - 10.13.103.152:9093
      - 10.128.120.218:9093

#Load rules once and periodically evaluate them according to the global ‘evaluation_interval‘.
rule_files:
  - "/data/prometheus-2.4.3/rules/node_down.yml"
  - "/data/prometheus-2.4.3/rules/memory_over.yml"
  - "/data/prometheus-2.4.3/rules/disk_over.yml"
  - "/data/prometheus-2.4.3/rules/cpu_over.yml"
  - "/data/prometheus-2.4.3/rules/http_check.yml"
  - "/data/prometheus-2.4.3/rules/tcp_check.yml"
  - "/data/prometheus-2.4.3/rules/mysql_check.yml"
  - "/data/prometheus-2.4.3/rules/redis_down_check.yml"
  - "/data/prometheus-2.4.3/rules/redis_rule_check.yml"
  - "/data/prometheus-2.4.3/rules/container_down.yml"
  - "/data/prometheus-2.4.3/rules/ping_check.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: ‘GICHOST‘
    file_sd_configs:
    - files: [‘./node_exporter/host.json‘]

  - job_name: ‘federate‘
    scrape_interval: 30s
    scrape_timeout: 25s
    honor_labels: true
    metrics_path: ‘/federate‘
    params:
      ‘match[]‘:
        - ‘{job=~"kubernetes-.*"}‘
    static_configs:
      - targets:
        - ‘10.13.103.12:9090‘

  - job_name: ‘blackbox-http‘
    scrape_interval: 5s
    metrics_path: /probe
    params:
      module: [http_2xx]  # Look for a HTTP 200 response.
    file_sd_configs:
    - files: [‘./blackbox_exporter/http.json‘]
    relabel_configs:
      - source_labels: [__address__]
        target_label: __param_target
      - source_labels: [__param_target]
        target_label: instance
      - target_label: __address__
        replacement: 10.13.103.151:9115

  - job_name: ‘blackbox-tcp‘
    scrape_interval: 5s
    metrics_path: /probe
    params:
      module: [tcp_connect]
    file_sd_configs:
    - files: [‘./blackbox_exporter/tcp.json‘]
    relabel_configs:
      - source_labels: [__address__]
        target_label: __param_target
      - source_labels: [__param_target]
        target_label: instance
      - target_label: __address__
        replacement: 10.13.103.151:9115

  - job_name: ‘mysqld-exporter‘
    file_sd_configs:
    - files: [‘./mysqld_exporter/mysqld.json‘]

  - job_name: ‘blackbox-ping‘
    scrape_interval: 5s
    metrics_path: /probe
    params:
      module: [icmp]
    file_sd_configs:
    - files: [‘./blackbox_exporter/ping.json‘]
    relabel_configs:
      - source_labels: [__address__]
        target_label: __param_target
      - source_labels: [__param_target]
        target_label: instance
      - target_label: __address__
        replacement: 10.13.103.151:9115

  - job_name: ‘redis-exporter‘
    file_sd_configs:
    - files: [‘./redis_exporter/redis.json‘]

  - job_name: ‘container-exporter‘
    file_sd_configs:
    - files: [‘./container_exporter/container.json‘]

8. 配置prometheus 主机监控文件和告警规则

8.1 主机监控文件

#mysqld_exporter主机监控文件

[email protected]:/data/prometheus-2.4.3# mkdir mysqld_exporter
[email protected]:/data/prometheus-2.4.3# cd mysqld_exporter/
[email protected]:/data/prometheus-2.4.3/mysqld_exporter# vim mysqld.json
[
{
"targets":[
"10.13.100.51:9104"
],
"labels":{
"dbinstance":"db100.51"
}
}
]

#redis_exporter主机监控文件

[email protected]:/data/prometheus-2.4.3# mkdir redis_exporter
[email protected]:/data/prometheus-2.4.3# cd redis_exporter/
[email protected]:/data/prometheus-2.4.3/redis_exporter# vim redis.json
[
{
"targets":[
"10.13.0.235:9121",
"10.13.0.236:9121"
],
"labels":{
"service":"redis"
}
}
]

#blackbox_exporter主机监控文件

[email protected]:/data/prometheus-2.4.3# mkdir blackbox_exporter
[email protected]:/data/prometheus-2.4.3# cd blackbox_exporter
[email protected]:/data/prometheus-2.4.3/blackbox_exporter# vim http.json
[
{
"targets":[
"http://10.13.227.134:6011/health",
"http://10.13.102.134:6011/health"
],
"labels":{
"service":"WSREP"
}
}
]
[email protected]:/data/prometheus-2.4.3/blackbox_exporter# vim tcp.json
[
{
"targets":[
"10.128.107.53:13371",
"10.128.107.57:13371"
],
"labels":{
"service":"vspc"
}
}
]
[email protected]:/data/prometheus-2.4.3/blackbox_exporter# vim ping.json
[
{
"targets":[
"10.13.101.131",
"10.13.101.132",
"10.13.101.141"
],
"labels":{
"service":"mysql"
}
}
]

#配置cadvisor主机监控文件

[email protected]:/data/prometheus-2.4.3# mkdir container_exporter
[email protected]:/data/prometheus-2.4.3# cd container_exporter/
[email protected]:/data/prometheus-2.4.3/container_exporter# vim container.json
[
{
"targets":[
"10.13.103.153:8080",
"10.128.87.5:8080"
],
"labels":{
"service":"docker-monitor"
}
}
]

8.2 告警规则

node_exporter监控获取的cpu，磁盘，实例存活规则上篇文章已经介绍，这里不再介绍

[email protected]:/data/prometheus-2.4.3# cd rules
[email protected]:/data/prometheus-2.4.3/rules# ls
container_down.yml  disk_over.yml  mysql_check.yml  node_down.yml   redis_down_check.yml  tcp_check.yml
cpu_over.yml  http_check.yml  memory_over.yml  ping_check.yml  redis_rule_check.yml

#mysqld_exporter监控mysql数据告警规则

[email protected]:/data/prometheus-2.4.3/rules# vim mysql_check.yml
groups:
- name: MySQLStatsAlert
  rules:
  - alert: MySQL is down
    expr: mysql_up == 0
    for: 1m
    labels:
      severity: critical
    annotations:
      summary: "Instance {{$labels.instance}} MySQL is down"
      description: "MySQL database is down. This requires immediate action!(current value is: {{$value}})"
  - alert: Mysql_High_QPS
    expr: rate(mysql_global_status_questions[5m]) > 8000
    for: 1m
    labels:
      severity: warning
    annotations:
      summary: "{{$labels.instance}}: Mysql_High_QPS detected"
      description: "{{$labels.instance}}: Mysql opreation is more than 5000 per second ,(current value is: {{$value}})"
  - alert: Mysql_Too_Many_Slow_Query
    expr: rate(mysql_global_status_slow_queries[30m]) > 3
    for: 1m
    labels:
      severity: warning
    annotations:
      summary: "{{$labels.instance}}: Mysql_Too_Many_Slow_Query detected"
      description: "{{$labels.instance}}: Mysql current Slow_Query Sql is more than 3 ,(current value is: {{$value}})"
  - alert: Mysql_Deadlock
    expr: mysql_global_status_innodb_deadlocks > 300
    for: 1m
    labels:
      severity: warning
    annotations:
      summary: "{{$labels.instance}}: Mysql_Deadlock detected"
      description: "{{$labels.instance}}: Mysql Deadlock was found ,(current value is: {{$value}})"
  - alert: open files high
    expr: mysql_global_status_innodb_num_open_files > (mysql_global_variables_open_files_limit) * 0.75
    for: 1m
    labels:
      severity: warning
    annotations:
      summary: "Instance {{$labels.instance}} open files high"
      description: "Open files is high. Please consider increasing open_files_limit.(current value is: {{$value}})"
  - alert: Used more than 80% of max connections limited
    expr: mysql_global_status_max_used_connections > mysql_global_variables_max_connections * 0.8
    for: 1m
    labels:
      severity: warning
    annotations:
      summary: "Instance {{$labels.instance}} Used more than 80% of max connections limited"
      description: "Used more than 80% of max connections limited.(current value is: {{$value}})"
  - alert: InnoDB Log File size is too small
    expr: mysql_global_variables_innodb_log_file_size < 16777216
    for: 1m
    labels:
      severity: warning
    annotations:
      summary: "Instance {{$labels.instance}} InnoDB Log File size is too small"
      description: "The InnoDB Log File size is possibly too small. Choosing a small InnoDB Log File size can have significant performance impacts.(current value is: {{$value}})"
  - alert: Binary Log is disabled
    expr: mysql_global_variables_log_bin != 1
    for: 1m
    labels:
      severity: warning
    annotations:
      summary: "Instance {{$labels.instance}} Binary Log is disabled"
      description: "Binary Log is disabled. This prohibits you to do Point in Time Recovery (PiTR).(current value is: {{$value}})"
  - alert: IO thread stopped
    expr: mysql_slave_status_slave_io_running != 1
    for: 1m
    labels:
      severity: critical
    annotations:
      summary: "Instance {{$labels.instance}} IO thread stopped"
      description: "IO thread has stopped. This is usually because it cannot connect to the Master any more.(current value is: {{$value}})"
  - alert: SQL thread stopped
    expr: mysql_slave_status_slave_sql_running != 1
    for: 1m
    labels:
      severity: critical
    annotations:
      summary: "Instance {{$labels.instance}} Sync Binlog is enabled"
      description: "SQL thread has stopped. This is usually because it cannot apply a SQL statement received from the master.(current value is: {{$value}})"
  - alert: Slave lagging behind Master
    expr: rate(mysql_slave_status_seconds_behind_master[1m]) >30
    for: 1m
    labels:
      severity: warning
    annotations:
      summary: "Instance {{$labels.instance}} Slave lagging behind Master"
      description: "Slave is lagging behind Master. Please check if Slave threads are running and if there are some performance issues!(current value is: {{$value}})"

#redis_exporter监控redis指标告警规则

[email protected]:/data/prometheus-2.4.3/rules# vim redis_down_check.yml
groups:
- name: redis检测规则
  rules:
  - alert: redis存活检测
    expr: redis_up{job="redis-exporter"} == 0
    for: 1m
    annotations:
      description: "机器:{{ $labels.instance }} 所属 job:{{ $labels.job }} redis宕机，请检查！"
      summary: "redis服务"
[email protected]:/data/prometheus-2.4.3/rules# vim redis_rule_check.yml
    groups:
- name: RedisStatsAlert
  rules:
  - alert: last create rdb failed
    expr: redis_rdb_last_bgsave_status != 1
    for: 1m
    labels:
      severity: warning
    annotations:
      summary: " Instance {{ $labels.instance }} rdb_last_bgsave_status  "
      description: "last create rdb failed"
  - alert: Redis linked too many clients
    expr: redis_connected_clients / redis_config_maxclients * 100 > 80
    for: 1m
    labels:
      severity: warning
    annotations:
      summary: "Instance {{ $labels.instance }} Redis linked clients too many"
      description: "Redis linked clients too many. This requires immediate action!"
  - alert: master link status failed
    expr: redis_master_link_up == 0
    for: 1m
    labels:
      severity: warning
    annotations:
      summary: "Instance {{ $labels.instance }} link failed"
      description: "redis_master_link=0 link failed"
  - alert: last AOF failed
    expr: redis_aof_last_bgrewrite_status != 1
    for: 1m
    labels:
      severity: warning
    annotations:
      summary: "Instance {{ $labels.instance }} redis aof last rewrite duration sec"
      description: "last AOF failed"
  - alert: Redis Cluster State Wrong
    expr: redis_cluster_state != 1
    for: 1m
    labels:
      severity: warning
    annotations:
      summary: "Instance {{ $labels.instance }} redis cluster status wrong"
      description: "Redis Cluster State Wrong"

#blackbox_exporter监控指标告警规则

[email protected]:/data/prometheus-2.4.3/rules# vim ping_check.yml
groups:
- name: 机器网络存活检测
  rules:
  - alert: 网络检测
    expr: probe_success{job="blackbox-ping"} == 0
    for: 1m
    annotations:
      description: "机器:{{ $labels.instance }} 所属 job:{{ $labels.job }} 网络不通或者宕机超过1分钟，请检查！"
      summary: "网络检测"
[email protected]:/data/prometheus-2.4.3/rules# vim http_check.yml
groups:
- name: 服务检测规则
  rules:
  - alert: http服务检测
    expr: probe_success{job="blackbox-http"} == 0
    for: 1m
    annotations:
      description: "机器:{{ $labels.instance }} 所属 job:{{ $labels.job }} http状态码: {{ printf `probe_http_status_code{instance=‘%s‘}` $labels.instance | query | first | value }} http检测失败，请检查！"
      summary: "http检测"
[email protected]:/data/prometheus-2.4.3/rules# vim tcp_check.yml
groups:
- name: 服务检测规则
  rules:
  - alert: tcp服务检测
    expr: probe_success{job="blackbox-tcp"} == 0
    for: 1m
    annotations:
      description: "机器:{{ $labels.instance }} 所属 job:{{ $labels.job }} tcp检测失败，请检查！"
      summary: "tcp检测"

#cadvisor监控指标告警规则

[email protected]:/data/prometheus-2.4.3/rules# vim container_down.yml 

groups:
- name: 容器存活报警规则
  rules:
  - alert: DockerInstanceDown
    expr: absent(container_last_seen{name="core_vspc"}) == 1
    for: 1m
    annotations:
      description: "vspc client容器:{{ $labels.name }} (所属主机{{ $labels.instance }}) 已经异常退出超过1分钟，请检查！"
      summary: "容器:Instance {{ $labels.name }} 存活检测"

参考文档：

https://github.com/prometheus
https://github.com/oliver006/redis_exporter
https://github.com/google/cadvisor

原文地址：https://www.cnblogs.com/jinanxiaolaohu/p/11294520.html

时间： 2024-11-01 13:50:20

[转帖]prometheus数据采集exporter全家桶的相关文章

prometheus数据采集exporter全家桶

1. exporter介绍 exporter是prometheus监控中重要的组成部分,负责数据指标的采集.上篇文章介绍了prometheus server的相关内容,本文将介绍数据采集插件.官方给出的插件有node_exporter.blackbox_exporter.mysqld_exporter.snmp_exporter等,第三方的插件有redis_exporter,cadvisor等.下面我将结合实际工作中的使用到的插件来分别介绍. 2. node_exporter node_expo

[转]vue全面介绍--全家桶、项目实例

慢慢了解vue及其全家桶的过程 原文http://blog.csdn.net/zhenghao35791/article/details/67639415 简介 “简单却不失优雅,小巧而不乏大匠”. 2016年最火的前端框架当属Vue.js了,很多使用过vue的程序员这样评价它,“vue.js兼具angular.js和React.js的优点,并剔除了它们的缺点”.授予了这么高的评价的vue.js,也是开源世界华人的骄傲,因为它的作者是位中国人–尤雨溪(Evan You). Vue.js 是一个J

vue移动端开发全家桶

一句命令搞定全家桶:  npm install vue-router vue-resource vuex --save main.js配置: import Vue from 'vue' import VueResource from 'vue-resource' import VueRouter from 'vue-router' import Vuex from 'vuex' import App from './App.vue' Vue.use(VueResource) Vue.use(Vu

“永恒之蓝”第二弹-Security Update补丁全家桶地址汇总(二)

Security Only Quality Update for Windows 7 for x64-based Systems (KB4012212) 3/14/2017 http://download.windowsupdate.com/d/msdownload/update/software/secu/2017/02/windows6.1-kb4012212-x64_2decefaa02e2058dcd965702509a992d8c4e92b3.msu Security Only Qua

“永恒之蓝”第二弹-Security Update补丁全家桶地址汇总(一)

MS17-010即Windows SMB 服务器安全更新,是微软于2017年3月14日推出的安全更新,此安全更新修复了 Microsoft Windows 中的漏洞. 如果攻击者向 Microsoft 服务器消息块 1.0 (SMBv1) 服务器发送经特殊设计的消息,则其中最严重的漏洞可能允许远程代码执行.有关该漏洞的更多信息,请参阅微软官链:https://technet.microsoft.com/zh-cn/library/security/MS17-010 下列文章包含此安全更新针对具体

vue全家桶(Vue+Vue-router+Vuex+axios)（Vue+webpack项目实战系列之二）

Vue有多优秀搭配全家桶做项目有多好之类的咱就不谈了,直奔主题. 一.Vue 系列一已经用vue-cli搭建了Vue项目,此处就不赘述了. 二.Vue-router Vue的路由,先献上文档(https://router.vuejs.org/zh-cn/). 路由在全家桶里面定位是什么呢,创建单页应用!简单!我们知道Vuejs是一系列的组件组成应用,既然是组件那么就需要组合起来,将组件(components)映射到路由(routes),然后告诉 vue-router 在哪里渲染它们! 我们一般在

react全家桶-1

全家桶内装有: react - github react-router - github redux - github react-redux - github react-router-redux - github redux-saga - github immutable - github reselect - github antd - github 服务端: json server 作为工具,支持CORS和JSONP跨域请求,支持GET, POST, PUT, PATCH 和 DELET

JetBrains全家桶激活地址

全家桶地址:https://www.jetbrains.com/products.html?fromMenu JetBrains 授权服务器(License Server URL):http://idea.imsxm.com 使用方法:激活时选择License server 填入http://idea.imsxm.com点击Active即可. 感谢授权网址:http://www.imsxm.com/jetbrains-license-server.html

vue全面介绍--全家桶、项目实例

简介 "简单却不失优雅,小巧而不乏大匠". 2016年最火的前端框架当属Vue.js了,很多使用过vue的程序员这样评价它,"vue.js兼具angular.js和react.js的优点,并剔除了它们的缺点".授予了这么高的评价的vue.js,也是开源世界华人的骄傲,因为它的作者是位中国人–尤雨溪(Evan You). Vue.js 是一个JavaScriptMVVM库,是一套构建用户界面的渐进式框架.它是以数据驱动和组件化的思想构建的,采用自底向上增量开发的设计.