当前位置：网站首页>Ansible production environment usage scenario (7): batch deployment of elk clients

Ansible production environment usage scenario (7): batch deployment of elk clients

2022-06-28 22:17:00 【51CTO】

background

As required by the audit , The system log should be kept 1 Year time , Now all the system logs on the private cloud message Send up elk platform 

[[email protected] opt]# more /etc/ansible/yaml/product/message_elk.yaml
# Upload the private cloud system log message to elk platform 
---
- hosts: "{{ hostlist }}" 
  remote_user: root 
  gather_facts: no
  tasks:
  - name: copy file and untar 
    unarchive:
      copy: yes
      src: /root/filebeat.tar.gz
      dest: /opt 
      mode: 0755
      owner: root
    register: copy_untar_files
  - name: copy sh 
    copy:
      src: /tmp/checkfilebeat.sh
      dest: /opt 
      mode: 0755
      owner: root
      backup: yes
    register: copy_sh
  - name: install crontab
    cron:
      minute: "*/20"
      user: root 
      job: /opt/checkfilebeat.sh >/dev/null 2>&1 
      name: check and start filebeat

     
    
      
  • 1.
    • 
      
  • 2.
    • 
      
  • 3.
    • 
      
  • 4.
    • 
      
  • 5.
    • 
      
  • 6.
    • 
      
  • 7.
    • 
      
  • 8.
    • 
      
  • 9.
    • 
      
  • 10.
    • 
      
  • 11.
    • 
      
  • 12.
    • 
      
  • 13.
    • 
      
  • 14.
    • 
      
  • 15.
    • 
      
  • 16.
    • 
      
  • 17.
    • 
      
  • 18.
    • 
      
  • 19.
    • 
      
  • 20.
    • 
      
  • 21.
    • 
      
  • 22.
    • 
      
  • 23.
    • 
      
  • 24.
    • 
      
  • 25.
    • 
      
  • 26.
    • 
      
  • 27.
    • 
      
  • 28.
    • 
      
  • 29.
    •

Script execution logic

  • modular unarchive： take filebeat.tar.gz Document is controlled by tool machine xx Upload to each server and unzip
  • modular copy： Will execute the document checkfilebeat.sh Upload to each server
  • modular cron： Deploy timed tasks , Every time 20 Minutes to execute the script checkfilebeat.sh

Script checkfilebeat.sh Will check the filebeat process , If it does not exist, it will be automatically pulled up

Script execution 

[[email protected] product]# ansible-playbook message_elk.yaml -e hostlist=all

     
    
      
  • 1.
    •

ansible Production environment usage scenarios ( 7、 ... and )： Mass deployment elk client _copy

In case of jamming during execution, it can be executed in batches ：

[[email protected] product]# ansible-playbook message_elk.yaml -e hostlist=xa-1,xb-2,xc-1,xd-1,xe-1,xf 

     
    
      
  • 1.
    •

ansible Production environment usage scenarios ( 7、 ... and )： Mass deployment elk client _copy_02

Check 

[[email protected] opt]# ansible -m shell -a "ps -ef|grep filebeat|grep -v grep " all

     
    
      
  • 1.
    •

ansible Production environment usage scenarios ( 7、 ... and )： Mass deployment elk client _yaml_03

elk Platform view

ansible Production environment usage scenarios ( 7、 ... and )： Mass deployment elk client _cron_04

原网站

版权声明
本文为[51CTO]所创，转载请带上原文链接，感谢
https://yzsam.com/2022/179/202206282134045317.html

边栏推荐

猜你喜欢

随机推荐