Ukuthumela izingodo ze-Nginx json kusetshenziswa i-Vector ku-Clickhouse ne-Elasticsearch

Ukuthumela izingodo ze-Nginx json kusetshenziswa i-Vector ku-Clickhouse ne-Elasticsearch

Vector, eklanyelwe ukuqoqa, ukuguqula nokuthumela idatha yelogi, amamethrikhi nemicimbi.

β†’ I-Github

Njengoba ibhalwe ngolimi lwe-Rust, ibonakala ngokusebenza okuphezulu nokusetshenziswa okuphansi kwe-RAM uma kuqhathaniswa nama-analogues ayo. Ngaphezu kwalokho, kunakekelwa kakhulu imisebenzi ehlobene nokunemba, ikakhulukazi, amandla okugcina imicimbi engathunyelwanga ku-buffer kudiski futhi ujikeleze amafayela.

Ngokwezakhiwo, iVector iyirutha yomcimbi eyamukela imilayezo evela koyedwa noma ngaphezulu imithombo, ngokuzikhethela usebenzisa le milayezo izinguquko, futhi uzithumele koyedwa noma ngaphezulu amapayipi amanzi.

I-Vector ithatha indawo ye-filebeat ne-logstash, ingasebenza kuzo zombili izindima (yamukele futhi ithumele izingodo), imininingwane eyengeziwe kuzo. isayithi.

Uma ku-Logstash iketango lakhiwe njengokufakwayo β†’ isihlungi β†’ okukhiphayo bese kuba kuVector imithombo β†’ uyashintsha β†’ uyacwila

Izibonelo zingatholakala emibhalweni.

Lo myalelo uwumyalelo obuyekeziwe ovela Vyacheslav Rakhinsky. Imiyalo yoqobo iqukethe ukucutshungulwa kwe-geoip. Lapho ihlola i-geoip kunethiwekhi yangaphakathi, i-vector inikeze iphutha.

Aug 05 06:25:31.889 DEBUG transform{name=nginx_parse_rename_fields type=rename_fields}: vector::transforms::rename_fields: Field did not exist field=Β«geoip.country_nameΒ» rate_limit_secs=30

Uma noma ubani edinga ukucubungula i-geoip, bheka iziqondiso zoqobo ezivela Vyacheslav Rakhinsky.

Sizomisa inhlanganisela ye-Nginx (Finyelela amalogi) β†’ Vector (Client | Filebeat) β†’ Vector (Server | Logstash) β†’ ngokuhlukile ku-Clickhouse futhi ngokuhlukene ku-Elasticsearch. Sizofaka amaseva angu-4. Nakuba ungakwazi ukuyidlula ngamaseva ama-3.

Ukuthumela izingodo ze-Nginx json kusetshenziswa i-Vector ku-Clickhouse ne-Elasticsearch

Uhlelo lufana nalokhu.

Khubaza i-Selinux kuwo wonke amaseva akho

sed -i 's/^SELINUX=.*/SELINUX=disabled/g' /etc/selinux/config
reboot

Sifaka i-emulator yeseva ye-HTTP + izinsiza kuwo wonke amaseva

Njenge-emulator yeseva ye-HTTP sizoyisebenzisa nodejs-stub-server kusukela UMaxim Ignatenko

I-Nodejs-stub-server ayinayo i-rpm. kuyinto yenzela i-rpm. rpm izokwakhiwa kusetshenziswa Fedora Copr

Engeza i-antonpatsev/nodejs-stub-server repository

yum -y install yum-plugin-copr epel-release
yes | yum copr enable antonpatsev/nodejs-stub-server

Faka i-nodejs-stub-server, i-Apache benchmark kanye ne-screen multiplexer kuwo wonke amaseva

yum -y install stub_http_server screen mc httpd-tools screen

Ngilungise isikhathi sokuphendula se-stub_http_server kufayela le-/var/lib/stub_http_server/stub_http_server.js ukuze kube namalogi amaningi.

var max_sleep = 10;

Masiqalise i-stub_http_server.

systemctl start stub_http_server
systemctl enable stub_http_server

Ukufakwa kwe-Clickhouse kuseva 3

I-ClickHouse isebenzisa isethi yemiyalo ye-SSE 4.2, ngakho-ke ngaphandle kokuthi kucaciswe ngenye indlela, ukusekelwa kwayo kuphrosesa esetshenzisiwe kuba imfuneko yohlelo eyengeziwe. Nawu umyalo wokuhlola ukuthi iphrosesa yamanje iyayisekela yini i-SSE 4.2:

grep -q sse4_2 /proc/cpuinfo && echo "SSE 4.2 supported" || echo "SSE 4.2 not supported"

Okokuqala udinga ukuxhuma inqolobane esemthethweni:

sudo yum install -y yum-utils
sudo rpm --import https://repo.clickhouse.tech/CLICKHOUSE-KEY.GPG
sudo yum-config-manager --add-repo https://repo.clickhouse.tech/rpm/stable/x86_64

Ukufaka amaphakheji udinga ukusebenzisa imiyalo elandelayo:

sudo yum install -y clickhouse-server clickhouse-client

Vumela i-clickhouse-server ukuthi ilalele ikhadi lenethiwekhi efayeleni /etc/clickhouse-server/config.xml

<listen_host>0.0.0.0</listen_host>

Ukushintsha izinga lokungena kusuka ekulandeleni kuya ekulungiseni iphutha

lungisa

Izilungiselelo zokucindezelwa okujwayelekile:

min_compress_block_size  65536
max_compress_block_size  1048576

Ukuze wenze kusebenze ukucindezelwa kwe-Zstd, kwelulekwe ukuthi ungathinti ukulungiselelwa, kodwa usebenzise i-DDL.

Ukuthumela izingodo ze-Nginx json kusetshenziswa i-Vector ku-Clickhouse ne-Elasticsearch

Angikwazanga ukuthola indlela yokusebenzisa ukucindezela kwe-zstd nge-DDL ku-Google. Ngakho ngayishiya injalo.

Ozakwethu abasebenzisa ukucindezela kwe-zstd ku-Clickhouse, sicela wabelane ngeziyalezo.

Ukuze uqale iseva njenge-daemon, sebenzisa:

service clickhouse-server start

Manje ake siqhubekele phambili ekusetheni i-Clickhouse

Iya ku-Clickhouse

clickhouse-client -h 172.26.10.109 -m

172.26.10.109 β€” IP yeseva lapho iClickhouse ifakwe khona.

Ake sakhe isizindalwazi se-vector

CREATE DATABASE vector;

Ake sihlole ukuthi isizindalwazi sikhona.

show databases;

Dala ithebula le-vector.logs.

/* Π­Ρ‚ΠΎ Ρ‚Π°Π±Π»ΠΈΡ†Π° Π³Π΄Π΅ хранятся Π»ΠΎΠ³ΠΈ ΠΊΠ°ΠΊ Π΅ΡΡ‚ΡŒ */

CREATE TABLE vector.logs
(
    `node_name` String,
    `timestamp` DateTime,
    `server_name` String,
    `user_id` String,
    `request_full` String,
    `request_user_agent` String,
    `request_http_host` String,
    `request_uri` String,
    `request_scheme` String,
    `request_method` String,
    `request_length` UInt64,
    `request_time` Float32,
    `request_referrer` String,
    `response_status` UInt16,
    `response_body_bytes_sent` UInt64,
    `response_content_type` String,
    `remote_addr` IPv4,
    `remote_port` UInt32,
    `remote_user` String,
    `upstream_addr` IPv4,
    `upstream_port` UInt32,
    `upstream_bytes_received` UInt64,
    `upstream_bytes_sent` UInt64,
    `upstream_cache_status` String,
    `upstream_connect_time` Float32,
    `upstream_header_time` Float32,
    `upstream_response_length` UInt64,
    `upstream_response_time` Float32,
    `upstream_status` UInt16,
    `upstream_content_type` String,
    INDEX idx_http_host request_http_host TYPE set(0) GRANULARITY 1
)
ENGINE = MergeTree()
PARTITION BY toYYYYMMDD(timestamp)
ORDER BY timestamp
TTL timestamp + toIntervalMonth(1)
SETTINGS index_granularity = 8192;

Sihlola ukuthi amathebula adaliwe. Asiqalise clickhouse-client futhi wenze isicelo.

Ake siye kusizindalwazi se-vector.

use vector;

Ok.

0 rows in set. Elapsed: 0.001 sec.

Ake sibheke amatafula.

show tables;

β”Œβ”€name────────────────┐
β”‚ logs                β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Ukufaka i-elasticsearch kuseva yesi-4 ukuthumela idatha efanayo ku-Elasticsearch ukuze iqhathaniswe ne-Clickhouse

Engeza ukhiye we-rpm osesidlangalaleni

rpm --import https://artifacts.elastic.co/GPG-KEY-elasticsearch

Masidale ama-repo angu-2:

/etc/yum.repos.d/elasticsearch.repo

[elasticsearch]
name=Elasticsearch repository for 7.x packages
baseurl=https://artifacts.elastic.co/packages/7.x/yum
gpgcheck=1
gpgkey=https://artifacts.elastic.co/GPG-KEY-elasticsearch
enabled=0
autorefresh=1
type=rpm-md

/etc/yum.repos.d/kibana.repo

[kibana-7.x]
name=Kibana repository for 7.x packages
baseurl=https://artifacts.elastic.co/packages/7.x/yum
gpgcheck=1
gpgkey=https://artifacts.elastic.co/GPG-KEY-elasticsearch
enabled=1
autorefresh=1
type=rpm-md

Faka i-elasticsearch ne-kibana

yum install -y kibana elasticsearch

Njengoba izoba kukhophi engu-1, udinga ukwengeza okulandelayo kufayela /etc/elasticsearch/elasticsearch.yml:

discovery.type: single-node

Ukuze leyo vector ikwazi ukuthumela idatha ku-elasticsearch kwenye iseva, ake sishintshe network.host.

network.host: 0.0.0.0

Ukuze uxhume ku-kibana, shintsha ipharamitha ye-server.host efayeleni /etc/kibana/kibana.yml

server.host: "0.0.0.0"

Okudala futhi kufaka phakathi i-elasticsearch ku-autostart

systemctl enable elasticsearch
systemctl start elasticsearch

futhi kibana

systemctl enable kibana
systemctl start kibana

Ilungiselela i-Elasticsearch yemodi yenodi eyodwa shard engu-1, i-replica engu-0. Kungenzeka ukuthi uzoba neqoqo lenombolo enkulu yamaseva futhi awudingi ukwenza lokhu.

Ukuze uthole izinkomba zesikhathi esizayo, buyekeza isifanekiso esizenzakalelayo:

curl -X PUT http://localhost:9200/_template/default -H 'Content-Type: application/json' -d '{"index_patterns": ["*"],"order": -1,"settings": {"number_of_shards": "1","number_of_replicas": "0"}}' 

setting Vector njengokungena esikhundleni se-Logstash kuseva 2

yum install -y https://packages.timber.io/vector/0.9.X/vector-x86_64.rpm mc httpd-tools screen

Masimise i-Vector esikhundleni se-Logstash. Ukuhlela ifayela /etc/vector/vector.toml

# /etc/vector/vector.toml

data_dir = "/var/lib/vector"

[sources.nginx_input_vector]
  # General
  type                          = "vector"
  address                       = "0.0.0.0:9876"
  shutdown_timeout_secs         = 30

[transforms.nginx_parse_json]
  inputs                        = [ "nginx_input_vector" ]
  type                          = "json_parser"

[transforms.nginx_parse_add_defaults]
  inputs                        = [ "nginx_parse_json" ]
  type                          = "lua"
  version                       = "2"

  hooks.process = """
  function (event, emit)

    function split_first(s, delimiter)
      result = {};
      for match in (s..delimiter):gmatch("(.-)"..delimiter) do
          table.insert(result, match);
      end
      return result[1];
    end

    function split_last(s, delimiter)
      result = {};
      for match in (s..delimiter):gmatch("(.-)"..delimiter) do
          table.insert(result, match);
      end
      return result[#result];
    end

    event.log.upstream_addr             = split_first(split_last(event.log.upstream_addr, ', '), ':')
    event.log.upstream_bytes_received   = split_last(event.log.upstream_bytes_received, ', ')
    event.log.upstream_bytes_sent       = split_last(event.log.upstream_bytes_sent, ', ')
    event.log.upstream_connect_time     = split_last(event.log.upstream_connect_time, ', ')
    event.log.upstream_header_time      = split_last(event.log.upstream_header_time, ', ')
    event.log.upstream_response_length  = split_last(event.log.upstream_response_length, ', ')
    event.log.upstream_response_time    = split_last(event.log.upstream_response_time, ', ')
    event.log.upstream_status           = split_last(event.log.upstream_status, ', ')

    if event.log.upstream_addr == "" then
        event.log.upstream_addr = "127.0.0.1"
    end

    if (event.log.upstream_bytes_received == "-" or event.log.upstream_bytes_received == "") then
        event.log.upstream_bytes_received = "0"
    end

    if (event.log.upstream_bytes_sent == "-" or event.log.upstream_bytes_sent == "") then
        event.log.upstream_bytes_sent = "0"
    end

    if event.log.upstream_cache_status == "" then
        event.log.upstream_cache_status = "DISABLED"
    end

    if (event.log.upstream_connect_time == "-" or event.log.upstream_connect_time == "") then
        event.log.upstream_connect_time = "0"
    end

    if (event.log.upstream_header_time == "-" or event.log.upstream_header_time == "") then
        event.log.upstream_header_time = "0"
    end

    if (event.log.upstream_response_length == "-" or event.log.upstream_response_length == "") then
        event.log.upstream_response_length = "0"
    end

    if (event.log.upstream_response_time == "-" or event.log.upstream_response_time == "") then
        event.log.upstream_response_time = "0"
    end

    if (event.log.upstream_status == "-" or event.log.upstream_status == "") then
        event.log.upstream_status = "0"
    end

    emit(event)

  end
  """

[transforms.nginx_parse_remove_fields]
    inputs                              = [ "nginx_parse_add_defaults" ]
    type                                = "remove_fields"
    fields                              = ["data", "file", "host", "source_type"]

[transforms.nginx_parse_coercer]

    type                                = "coercer"
    inputs                              = ["nginx_parse_remove_fields"]

    types.request_length = "int"
    types.request_time = "float"

    types.response_status = "int"
    types.response_body_bytes_sent = "int"

    types.remote_port = "int"

    types.upstream_bytes_received = "int"
    types.upstream_bytes_send = "int"
    types.upstream_connect_time = "float"
    types.upstream_header_time = "float"
    types.upstream_response_length = "int"
    types.upstream_response_time = "float"
    types.upstream_status = "int"

    types.timestamp = "timestamp"

[sinks.nginx_output_clickhouse]
    inputs   = ["nginx_parse_coercer"]
    type     = "clickhouse"

    database = "vector"
    healthcheck = true
    host = "http://172.26.10.109:8123" #  АдрСс Clickhouse
    table = "logs"

    encoding.timestamp_format = "unix"

    buffer.type = "disk"
    buffer.max_size = 104900000
    buffer.when_full = "block"

    request.in_flight_limit = 20

[sinks.elasticsearch]
    type = "elasticsearch"
    inputs   = ["nginx_parse_coercer"]
    compression = "none"
    healthcheck = true
    # 172.26.10.116 - сСрвСр Π³Π΄Π΅ установСн elasticsearch
    host = "http://172.26.10.116:9200" 
    index = "vector-%Y-%m-%d"

Ungalungisa isigaba se-transforms.nginx_parse_add_defaults.

Kusukela Vyacheslav Rakhinsky isebenzisa lezi zilungiselelo ku-CDN encane futhi kungaba khona amanani ambalwa phezulu_*

Isibonelo:

"upstream_addr": "128.66.0.10:443, 128.66.0.11:443, 128.66.0.12:443"
"upstream_bytes_received": "-, -, 123"
"upstream_status": "502, 502, 200"

Uma lesi kungesona isimo sakho, khona-ke lesi sigaba singenziwa lula

Masidale izilungiselelo zesevisi ze-systemd /etc/systemd/system/vector.service

# /etc/systemd/system/vector.service

[Unit]
Description=Vector
After=network-online.target
Requires=network-online.target

[Service]
User=vector
Group=vector
ExecStart=/usr/bin/vector
ExecReload=/bin/kill -HUP $MAINPID
Restart=no
StandardOutput=syslog
StandardError=syslog
SyslogIdentifier=vector

[Install]
WantedBy=multi-user.target

Ngemva kokudala amatafula, ungasebenzisa i-Vector

systemctl enable vector
systemctl start vector

Amalogi weVector angabukwa kanje:

journalctl -f -u vector

Kufanele kube nokufakiwe okufana nalokhu kulogi

INFO vector::topology::builder: Healthcheck: Passed.
INFO vector::topology::builder: Healthcheck: Passed.

Kuklayenti (Iseva yewebhu) - iseva yokuqala

Kuseva ene-nginx, udinga ukukhubaza i-ipv6, njengoba ithebula lamalogi ku-clickhouse lisebenzisa inkambu. upstream_addr IPv4, njengoba ngingasebenzisi i-ipv6 ngaphakathi kwenethiwekhi. Uma i-ipv6 ingavaliwe, kuzoba namaphutha:

DB::Exception: Invalid IPv4 value.: (while read the value of key upstream_addr)

Mhlawumbe bafundi, engeza ukwesekwa kwe-ipv6.

Dala ifayela /etc/sysctl.d/98-disable-ipv6.conf

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1

Ukusebenzisa izilungiselelo

sysctl --system

Asifake i-nginx.

Kwengezwe ifayela le-nginx /etc/yum.repos.d/nginx.repo

[nginx-stable]
name=nginx stable repo
baseurl=http://nginx.org/packages/centos/$releasever/$basearch/
gpgcheck=1
enabled=1
gpgkey=https://nginx.org/keys/nginx_signing.key
module_hotfixes=true

Faka iphakheji ye-nginx

yum install -y nginx

Okokuqala, sidinga ukumisa ifomethi yelogi ku-Nginx kufayela /etc/nginx/nginx.conf

user  nginx;
# you must set worker processes based on your CPU cores, nginx does not benefit from setting more than that
worker_processes auto; #some last versions calculate it automatically

# number of file descriptors used for nginx
# the limit for the maximum FDs on the server is usually set by the OS.
# if you don't set FD's then OS settings will be used which is by default 2000
worker_rlimit_nofile 100000;

error_log  /var/log/nginx/error.log warn;
pid        /var/run/nginx.pid;

# provides the configuration file context in which the directives that affect connection processing are specified.
events {
    # determines how much clients will be served per worker
    # max clients = worker_connections * worker_processes
    # max clients is also limited by the number of socket connections available on the system (~64k)
    worker_connections 4000;

    # optimized to serve many clients with each thread, essential for linux -- for testing environment
    use epoll;

    # accept as many connections as possible, may flood worker connections if set too low -- for testing environment
    multi_accept on;
}

http {
    include       /etc/nginx/mime.types;
    default_type  application/octet-stream;

    log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for"';

log_format vector escape=json
    '{'
        '"node_name":"nginx-vector",'
        '"timestamp":"$time_iso8601",'
        '"server_name":"$server_name",'
        '"request_full": "$request",'
        '"request_user_agent":"$http_user_agent",'
        '"request_http_host":"$http_host",'
        '"request_uri":"$request_uri",'
        '"request_scheme": "$scheme",'
        '"request_method":"$request_method",'
        '"request_length":"$request_length",'
        '"request_time": "$request_time",'
        '"request_referrer":"$http_referer",'
        '"response_status": "$status",'
        '"response_body_bytes_sent":"$body_bytes_sent",'
        '"response_content_type":"$sent_http_content_type",'
        '"remote_addr": "$remote_addr",'
        '"remote_port": "$remote_port",'
        '"remote_user": "$remote_user",'
        '"upstream_addr": "$upstream_addr",'
        '"upstream_bytes_received": "$upstream_bytes_received",'
        '"upstream_bytes_sent": "$upstream_bytes_sent",'
        '"upstream_cache_status":"$upstream_cache_status",'
        '"upstream_connect_time":"$upstream_connect_time",'
        '"upstream_header_time":"$upstream_header_time",'
        '"upstream_response_length":"$upstream_response_length",'
        '"upstream_response_time":"$upstream_response_time",'
        '"upstream_status": "$upstream_status",'
        '"upstream_content_type":"$upstream_http_content_type"'
    '}';

    access_log  /var/log/nginx/access.log  main;
    access_log  /var/log/nginx/access.json.log vector;      # Новый Π»ΠΎΠ³ Π² Ρ„ΠΎΡ€ΠΌΠ°Ρ‚Π΅ json

    sendfile        on;
    #tcp_nopush     on;

    keepalive_timeout  65;

    #gzip  on;

    include /etc/nginx/conf.d/*.conf;
}

Ukuze ungaphuli ukumisa kwakho kwamanje, i-Nginx ikuvumela ukuthi ube neziqondiso ezimbalwa zokufinyelela_log

access_log  /var/log/nginx/access.log  main;            # Π‘Ρ‚Π°Π½Π΄Π°Ρ€Ρ‚Π½Ρ‹ΠΉ Π»ΠΎΠ³
access_log  /var/log/nginx/access.json.log vector;      # Новый Π»ΠΎΠ³ Π² Ρ„ΠΎΡ€ΠΌΠ°Ρ‚Π΅ json

Ungakhohlwa ukwengeza umthetho ukuze uthole amalogi amasha (uma ifayela lokungena lingagcini ngokuthi .log)

Susa i-default.conf ku-/etc/nginx/conf.d/

rm -f /etc/nginx/conf.d/default.conf

Engeza i-virtual host /etc/nginx/conf.d/vhost1.conf

server {
    listen 80;
    server_name vhost1;
    location / {
        proxy_pass http://172.26.10.106:8080;
    }
}

Engeza i-virtual host /etc/nginx/conf.d/vhost2.conf

server {
    listen 80;
    server_name vhost2;
    location / {
        proxy_pass http://172.26.10.108:8080;
    }
}

Engeza i-virtual host /etc/nginx/conf.d/vhost3.conf

server {
    listen 80;
    server_name vhost3;
    location / {
        proxy_pass http://172.26.10.109:8080;
    }
}

Engeza i-virtual host /etc/nginx/conf.d/vhost4.conf

server {
    listen 80;
    server_name vhost4;
    location / {
        proxy_pass http://172.26.10.116:8080;
    }
}

Engeza i-virtual host (172.26.10.106 ip yeseva lapho i-nginx ifakiwe) kuwo wonke amaseva kufayela /etc/hosts:

172.26.10.106 vhost1
172.26.10.106 vhost2
172.26.10.106 vhost3
172.26.10.106 vhost4

Futhi uma konke sekumi ngomumo ke

nginx -t 
systemctl restart nginx

Manje ake sizifakele thina Vector

yum install -y https://packages.timber.io/vector/0.9.X/vector-x86_64.rpm

Masidale ifayela lezilungiselelo le-systemd /etc/systemd/system/vector.service

[Unit]
Description=Vector
After=network-online.target
Requires=network-online.target

[Service]
User=vector
Group=vector
ExecStart=/usr/bin/vector
ExecReload=/bin/kill -HUP $MAINPID
Restart=no
StandardOutput=syslog
StandardError=syslog
SyslogIdentifier=vector

[Install]
WantedBy=multi-user.target

Futhi ulungiselele ukushintshwa kwe-Filebeat ku-config /etc/vector/vector.toml. Ikheli lasesizindeni se-inthanethi 172.26.10.108 ikheli lasesizindeni se-inthanethi leseva yelogi (Vector-Server)

data_dir = "/var/lib/vector"

[sources.nginx_file]
  type                          = "file"
  include                       = [ "/var/log/nginx/access.json.log" ]
  start_at_beginning            = false
  fingerprinting.strategy       = "device_and_inode"

[sinks.nginx_output_vector]
  type                          = "vector"
  inputs                        = [ "nginx_file" ]

  address                       = "172.26.10.108:9876"

НС Π·Π°Π±ΡƒΠ΄Ρ‚Π΅ Π΄ΠΎΠ±Π°Π²ΠΈΡ‚ΡŒ ΡŽΠ·Π΅Ρ€Π° vector Π² Π½ΡƒΠΆΠ½ΡƒΡŽ Π³Ρ€ΡƒΠΏΠΏΡƒ Ρ‡Ρ‚ΠΎ Π±Ρ‹ ΠΎΠ½ ΠΌΠΎΠ³ Ρ‡ΠΈΡ‚Π°Ρ‚ΡŒ log Ρ„Π°ΠΉΠ»Ρ‹. НапримСр, nginx Π² centos создаСт Π»ΠΎΠ³ΠΈ с ΠΏΡ€Π°Π²Π°ΠΌΠΈ Π³Ρ€ΡƒΠΏΠΏΡ‹ adm.

usermod -a -G adm vector

Ake siqale isevisi ye-vector

systemctl enable vector
systemctl start vector

Amalogi weVector angabukwa kanje:

journalctl -f -u vector

Kufanele kube khona okufakiwe okufana nalokhu kulogi

INFO vector::topology::builder: Healthcheck: Passed.

Ukuhlolwa Kwengcindezi

Ukuhlola kwenziwa kusetshenziswa ibhentshimakhi ye-Apache.

Iphakheji yamathuluzi we-httpd ifakwe kuwo wonke amaseva

Siqala ukuhlola sisebenzisa ibhentshimakhi ye-Apache kusuka kumaseva angu-4 ahlukene esikrinini. Okokuqala, sethula i-multiplexer yetheminali yesikrini, bese siqala ukuhlola sisebenzisa ibhentshimakhi ye-Apache. Indlela yokusebenza ngesikrini ongayithola isihloko.

Kusuka kuseva yoku-1

while true; do ab -H "User-Agent: 1server" -c 100 -n 10 -t 10 http://vhost1/; sleep 1; done

Kusuka kuseva yoku-2

while true; do ab -H "User-Agent: 2server" -c 100 -n 10 -t 10 http://vhost2/; sleep 1; done

Kusuka kuseva yoku-3

while true; do ab -H "User-Agent: 3server" -c 100 -n 10 -t 10 http://vhost3/; sleep 1; done

Kusuka kuseva yoku-4

while true; do ab -H "User-Agent: 4server" -c 100 -n 10 -t 10 http://vhost4/; sleep 1; done

Ake sihlole idatha ku-Clickhouse

Iya ku-Clickhouse

clickhouse-client -h 172.26.10.109 -m

Ukwenza umbuzo we-SQL

SELECT * FROM vector.logs;

β”Œβ”€node_name────┬───────────timestamp─┬─server_name─┬─user_id─┬─request_full───┬─request_user_agent─┬─request_http_host─┬─request_uri─┬─request_scheme─┬─request_method─┬─request_length─┬─request_time─┬─request_referrer─┬─response_status─┬─response_body_bytes_sent─┬─response_content_type─┬───remote_addr─┬─remote_port─┬─remote_user─┬─upstream_addr─┬─upstream_port─┬─upstream_bytes_received─┬─upstream_bytes_sent─┬─upstream_cache_status─┬─upstream_connect_time─┬─upstream_header_time─┬─upstream_response_length─┬─upstream_response_time─┬─upstream_status─┬─upstream_content_type─┐
β”‚ nginx-vector β”‚ 2020-08-07 04:32:42 β”‚ vhost1      β”‚         β”‚ GET / HTTP/1.0 β”‚ 1server            β”‚ vhost1            β”‚ /           β”‚ http           β”‚ GET            β”‚             66 β”‚        0.028 β”‚                  β”‚             404 β”‚                       27 β”‚                       β”‚ 172.26.10.106 β”‚       45886 β”‚             β”‚ 172.26.10.106 β”‚             0 β”‚                     109 β”‚                  97 β”‚ DISABLED              β”‚                     0 β”‚                0.025 β”‚                       27 β”‚                  0.029 β”‚             404 β”‚                       β”‚
└──────────────┴─────────────────────┴─────────────┴─────────┴────────────────┴────────────────────┴───────────────────┴─────────────┴────────────────┴────────────────┴────────────────┴──────────────┴──────────────────┴─────────────────┴──────────────────────────┴───────────────────────┴───────────────┴─────────────┴─────────────┴───────────────┴───────────────┴─────────────────────────┴─────────────────────┴───────────────────────┴───────────────────────┴──────────────────────┴──────────────────────────┴────────────────────────┴─────────────────┴───────────────────────

Thola usayizi wamatafula ku-Clickhouse

select concat(database, '.', table)                         as table,
       formatReadableSize(sum(bytes))                       as size,
       sum(rows)                                            as rows,
       max(modification_time)                               as latest_modification,
       sum(bytes)                                           as bytes_size,
       any(engine)                                          as engine,
       formatReadableSize(sum(primary_key_bytes_in_memory)) as primary_keys_size
from system.parts
where active
group by database, table
order by bytes_size desc;

Ake sithole ukuthi zingakanani izingodo ezithathwe eClickhouse.

Ukuthumela izingodo ze-Nginx json kusetshenziswa i-Vector ku-Clickhouse ne-Elasticsearch

Usayizi wetafula lamalogi ngu-857.19 MB.

Ukuthumela izingodo ze-Nginx json kusetshenziswa i-Vector ku-Clickhouse ne-Elasticsearch

Usayizi wedatha efanayo kunkomba ku-Elasticsearch ngu-4,5GB.

Uma ungayicacisi idatha ku-vector kumapharamitha, i-Clickhouse ithatha 4500/857.19 = izikhathi ezingaphansi kuka-5.24 kune-Elasticsearch.

Ku-vector, inkambu yokucindezela isetshenziswa ngokuzenzakalelayo.

Ingxoxo yeTelegram clickhouse
Ingxoxo yeTelegram Islastiki
Ingxoxo yocingo ngo-"Ukuqoqwa nokuhlaziywa kohlelo imibiko"

Source: www.habr.com

Thenga ukusingathwa okuthembekile kwamasayithi anokuvikelwa kwe-DDoS, amaseva e-VPS VDS πŸ”₯ Thenga ukusingathwa kwewebhusayithi okuthembekile ngokuvikelwa kwe-DDoS, amaseva e-VPS VDS | ProHoster