â
Rust nyelven ĂrĂłdott, analĂłgjaihoz kĂ©pest nagy teljesĂtmĂ©ny Ă©s alacsony RAM-fogyasztĂĄs jellemzi. Ezen tĂșlmenĆen nagy figyelmet fordĂtanak a helyessĂ©ggel kapcsolatos funkciĂłkra, kĂŒlönösen az el nem kĂŒldött esemĂ©nyek lemezen lĂ©vĆ pufferbe mentĂ©sĂ©re Ă©s a fĂĄjlok elforgatĂĄsĂĄra.
ĂpĂtĂ©szetileg a Vector esemĂ©nyĂștvĂĄlasztĂł, amely egy vagy több ĂŒzenetet fogad forrĂĄsok, opcionĂĄlisan alkalmazva ezekre az ĂŒzenetekre ĂĄtalakulĂĄsok, Ă©s elkĂŒldi Ćket egy vagy többnek lefolyĂłk.
A Vector a filebeat Ă©s a logstash helyettesĂtĆje, mindkĂ©t szerepkörben kĂ©pes mƱködni (naplĂłk fogadĂĄsa Ă©s kĂŒldĂ©se), tovĂĄbbi rĂ©szletek rĂłluk
Ha a Logstash-ban a lĂĄnc bemenetkĂ©nt â szƱrĆ â kimenetkĂ©nt Ă©pĂŒl fel, akkor Vectorban az
PĂ©ldĂĄk talĂĄlhatĂłk a dokumentĂĄciĂłban.
Ez az utasĂtĂĄs egy felĂŒlvizsgĂĄlt utasĂtĂĄs
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
Ha valakinek fel kell dolgoznia a geoip-et, nĂ©zze meg az eredeti utasĂtĂĄsokat
Az Nginx (HozzĂĄfĂ©rĂ©si naplĂłk) â Vector (Client | Filebeat) â Vector (Server | Logstash) â kombinĂĄciĂłt kĂŒlön fogjuk konfigurĂĄlni a Clickhouse-ban Ă©s kĂŒlön az Elasticsearch-ben. 4 szervert telepĂtĂŒnk. BĂĄr 3 szerverrel ki lehet kerĂŒlni.
A séma valami ilyesmi.
Tiltsa le a Selinuxot az összes szerverén
sed -i 's/^SELINUX=.*/SELINUX=disabled/g' /etc/selinux/config
reboot
Minden szerverre telepĂtĂŒnk egy HTTP szerver emulĂĄtort + segĂ©dprogramokat
HTTP szerver emulåtorként fogjuk hasznålni
A Nodejs-stub-server nem rendelkezik fordulatszĂĄmmal.
Adja hozzĂĄ az antonpatsev/nodejs-stub-server lerakat
yum -y install yum-plugin-copr epel-release
yes | yum copr enable antonpatsev/nodejs-stub-server
A nodejs-stub-server, az Apache benchmark Ă©s a kĂ©pernyĆterminĂĄl multiplexer telepĂtĂ©se minden kiszolgĂĄlĂłra
yum -y install stub_http_server screen mc httpd-tools screen
JavĂtottam a stub_http_server vĂĄlaszidĆt a /var/lib/stub_http_server/stub_http_server.js fĂĄjlban, hogy több naplĂł legyen.
var max_sleep = 10;
IndĂtsuk el a stub_http_servert.
systemctl start stub_http_server
systemctl enable stub_http_server
Clickhouse telepĂtĂ©s a 3-as szerveren
A ClickHouse az SSE 4.2-es utasĂtĂĄskĂ©szletĂ©t hasznĂĄlja, Ăgy ha nincs mĂĄskĂ©pp megadva, tovĂĄbbi rendszerkövetelmĂ©ny lesz a tĂĄmogatĂĄs a hasznĂĄlt processzorban. A következĆ parancs segĂtsĂ©gĂ©vel ellenĆrizheti, hogy a jelenlegi processzor tĂĄmogatja-e az SSE 4.2-t:
grep -q sse4_2 /proc/cpuinfo && echo "SSE 4.2 supported" || echo "SSE 4.2 not supported"
ElĆször csatlakoztatnia kell a hivatalos adattĂĄrat:
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
A csomagok telepĂtĂ©sĂ©hez a következĆ parancsokat kell futtatnia:
sudo yum install -y clickhouse-server clickhouse-client
Engedélyezze a clickhouse-server szåmåra a hålózati kårtya meghallgatåsåt az /etc/clickhouse-server/config.xml fåjlban
<listen_host>0.0.0.0</listen_host>
A naplĂłzĂĄsi szint mĂłdosĂtĂĄsa nyomkövetĂ©srĆl hibakeresĂ©sre
hibakeresés
Standard tömörĂtĂ©si beĂĄllĂtĂĄsok:
min_compress_block_size 65536
max_compress_block_size 1048576
A Zstd tömörĂtĂ©s aktivĂĄlĂĄsĂĄhoz azt tanĂĄcsoltuk, hogy ne Ă©rintsĂŒk meg a konfigurĂĄciĂłt, inkĂĄbb hasznĂĄljunk DDL-t.
Nem talĂĄltam meg a zstd tömörĂtĂ©s hasznĂĄlatĂĄt DDL-n keresztĂŒl a Google-ban. SzĂłval hagytam Ășgy ahogy van.
Azok a kollĂ©gĂĄk, akik zstd tömörĂtĂ©st hasznĂĄlnak a Clickhouse-ban, ossza meg az utasĂtĂĄsokat.
A szerver dĂ©monkĂ©nt valĂł indĂtĂĄsĂĄhoz futtassa:
service clickhouse-server start
Most tĂ©rjĂŒnk ĂĄt a Clickhouse beĂĄllĂtĂĄsĂĄra
Menj a Clickhouse-ba
clickhouse-client -h 172.26.10.109 -m
172.26.10.109 â Annak a szervernek az IP-cĂme, amelyre a Clickhouse telepĂtve van.
Hozzunk létre egy vektoros adatbåzist
CREATE DATABASE vector;
EllenĆrizzĂŒk, hogy lĂ©tezik-e az adatbĂĄzis.
show databases;
Hozzon létre egy vector.logs tåblåt.
/* ĐŃĐŸ ŃаблОŃĐ° гЎД Ń
ŃĐ°ĐœŃŃŃŃ Đ»ĐŸĐłĐž ĐșĐ°Đș Đ”ŃŃŃ */
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;
EllenĆrizzĂŒk, hogy a tĂĄblĂĄk lĂ©trejöttek-e. IndĂtsuk el clickhouse-client
és kérjen.
MenjĂŒnk a vektoros adatbĂĄzishoz.
use vector;
Ok.
0 rows in set. Elapsed: 0.001 sec.
NĂ©zzĂŒk a tĂĄblĂĄzatokat.
show tables;
âânameâââââââââââââââââ
â logs â
âââââââââââââââââââââââ
Az elasticsearch telepĂtĂ©se a 4. szerverre, hogy ugyanazokat az adatokat elkĂŒldje az Elasticsearch-nek a Clickhouse-szal valĂł összehasonlĂtĂĄshoz
Adjon hozzĂĄ egy nyilvĂĄnos fordulatszĂĄm-kulcsot
rpm --import https://artifacts.elastic.co/GPG-KEY-elasticsearch
Hozzunk létre 2 repót:
/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
TelepĂtse az elaszticsearch-ot Ă©s a kibanĂĄt
yum install -y kibana elasticsearch
Mivel 1 pĂ©ldĂĄnyban lesz, a következĆket kell hozzĂĄadnia az /etc/elasticsearch/elasticsearch.yml fĂĄjlhoz:
discovery.type: single-node
Ahhoz, hogy ez a vektor adatokat kĂŒldhessen az elasticsearch-nek egy mĂĄsik szerverrĆl, vĂĄltoztassuk meg a network.host-ot.
network.host: 0.0.0.0
A kibanĂĄhoz valĂł csatlakozĂĄshoz mĂłdosĂtsa a server.host paramĂ©tert az /etc/kibana/kibana.yml fĂĄjlban
server.host: "0.0.0.0"
RĂ©gi Ă©s tartalmazza az elaszticsearch-t az automatikus indĂtĂĄsban
systemctl enable elasticsearch
systemctl start elasticsearch
Ă©s kibana
systemctl enable kibana
systemctl start kibana
Az Elasticsearch konfigurĂĄlĂĄsa egycsomĂłpontos mĂłdhoz 1 szilĂĄnk, 0 replika. ValĂłszĂnƱleg nagyszĂĄmĂș kiszolgĂĄlĂłbĂłl ĂĄllĂł fĂŒrtje lesz, Ă©s ezt nem kell megtennie.
A jövĆbeli indexekhez frissĂtse az alapĂ©rtelmezett sablont:
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"}}'
TelepĂtĂ©s vektor a Logstash helyettesĂtĆjekĂ©nt a 2-es szerveren
yum install -y https://packages.timber.io/vector/0.9.X/vector-x86_64.rpm mc httpd-tools screen
ĂllĂtsuk be a Vectort a Logstash helyettesĂtĂ©sĂ©re. Az /etc/vector/vector.toml fĂĄjl szerkesztĂ©se
# /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"
BeĂĄllĂthatja a transforms.nginx_parse_add_defaults szakaszt.
Mint
PĂ©ldĂĄul:
"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"
Ha nem ez a helyzet, akkor ez a szakasz leegyszerƱsĂthetĆ
Hozzuk lĂ©tre a systemd /etc/systemd/system/vector.service szolgĂĄltatĂĄs beĂĄllĂtĂĄsait
# /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
A tåblåzatok létrehozåsa utån futtathatja a Vectort
systemctl enable vector
systemctl start vector
A vektornaplĂłkat a következĆkĂ©ppen tekintheti meg:
journalctl -f -u vector
Ilyen bejegyzĂ©seknek kell lenniĂŒk a naplĂłkban
INFO vector::topology::builder: Healthcheck: Passed.
INFO vector::topology::builder: Healthcheck: Passed.
A kliensen (webszerver) - 1. szerver
Az nginx-szel rendelkezĆ szerveren le kell tiltani az ipv6-ot, mivel a clickhouse naplĂłtĂĄblĂĄzata a mezĆt hasznĂĄlja upstream_addr
IPv4, mivel nem hasznĂĄlok ipv6-ot a hĂĄlĂłzaton belĂŒl. Ha az ipv6 nincs kikapcsolva, hibĂĄk lĂ©pnek fel:
DB::Exception: Invalid IPv4 value.: (while read the value of key upstream_addr)
TalĂĄn olvasĂłk, adjĂĄk hozzĂĄ az ipv6 tĂĄmogatĂĄst.
Hozza létre az /etc/sysctl.d/98-disable-ipv6.conf fåjlt
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
A beĂĄllĂtĂĄsok alkalmazĂĄsa
sysctl --system
TelepĂtsĂŒk az nginx-et.
nginx adattĂĄrfĂĄjl hozzĂĄadva /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
TelepĂtse az nginx csomagot
yum install -y nginx
ElĆször is be kell ĂĄllĂtanunk a naplĂłformĂĄtumot az Nginxben az /etc/nginx/nginx.conf fĂĄjlban
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;
}
Annak Ă©rdekĂ©ben, hogy ne törje meg a jelenlegi konfigurĂĄciĂłt, az Nginx lehetĆvĂ© teszi több access_log direktĂva hasznĂĄlatĂĄt
access_log /var/log/nginx/access.log main; # ĐĄŃĐ°ĐœĐŽĐ°ŃŃĐœŃĐč Đ»ĐŸĐł
access_log /var/log/nginx/access.json.log vector; # ĐĐŸĐČŃĐč Đ»ĐŸĐł ĐČ ŃĐŸŃĐŒĐ°ŃĐ” json
Ne felejtsen el egy szabĂĄlyt hozzĂĄadni az Ășj naplĂłk logrotate-jĂĄhoz (ha a naplĂłfĂĄjl nem vĂ©gzĆdik .log-al)
TĂĄvolĂtsa el a default.conf fĂĄjlt az /etc/nginx/conf.d/ fĂĄjlbĂłl
rm -f /etc/nginx/conf.d/default.conf
Adja hozzå az /etc/nginx/conf.d/vhost1.conf virtuålis gazdagépet
server {
listen 80;
server_name vhost1;
location / {
proxy_pass http://172.26.10.106:8080;
}
}
Adja hozzå az /etc/nginx/conf.d/vhost2.conf virtuålis gazdagépet
server {
listen 80;
server_name vhost2;
location / {
proxy_pass http://172.26.10.108:8080;
}
}
Adja hozzå az /etc/nginx/conf.d/vhost3.conf virtuålis gazdagépet
server {
listen 80;
server_name vhost3;
location / {
proxy_pass http://172.26.10.109:8080;
}
}
Adja hozzå az /etc/nginx/conf.d/vhost4.conf virtuålis gazdagépet
server {
listen 80;
server_name vhost4;
location / {
proxy_pass http://172.26.10.116:8080;
}
}
Adjon hozzĂĄ virtuĂĄlis gazdagĂ©peket (az nginx telepĂtett kiszolgĂĄlĂł 172.26.10.106 ip-je) az összes kiszolgĂĄlĂłhoz az /etc/hosts fĂĄjlba:
172.26.10.106 vhost1
172.26.10.106 vhost2
172.26.10.106 vhost3
172.26.10.106 vhost4
Ăs ha minden kĂ©szen van, akkor
nginx -t
systemctl restart nginx
Most telepĂtsĂŒk mi magunk
yum install -y https://packages.timber.io/vector/0.9.X/vector-x86_64.rpm
Hozzon lĂ©tre egy beĂĄllĂtĂĄsi fĂĄjlt a systemd /etc/systemd/system/vector.service szĂĄmĂĄra
[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
Ăs ĂĄllĂtsa be a Filebeat cserĂ©t az /etc/vector/vector.toml konfigurĂĄciĂłban. A 172.26.10.108 IP-cĂm a naplĂłszerver IP-cĂme (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"
Ne felejtse el hozzĂĄadni a vektor felhasznĂĄlĂłt a kĂvĂĄnt csoporthoz, hogy naplĂłfĂĄjlokat olvashasson. PĂ©ldĂĄul az nginx in centos naplĂłkat hoz lĂ©tre adm csoportjogokkal.
usermod -a -G adm vector
IndĂtsuk el a vektorszolgĂĄltatĂĄst
systemctl enable vector
systemctl start vector
A vektornaplĂłkat a következĆkĂ©ppen tekintheti meg:
journalctl -f -u vector
Ilyen bejegyzésnek kell lennie a naplókban
INFO vector::topology::builder: Healthcheck: Passed.
Stressz tesztelés
A tesztelĂ©st Apache benchmark segĂtsĂ©gĂ©vel vĂ©gezzĂŒk.
A httpd-tools csomag minden kiszolgĂĄlĂłra telepĂtve volt
ElkezdjĂŒk a tesztelĂ©st az Apache benchmark hasznĂĄlatĂĄval 4 kĂŒlönbözĆ szerverrĆl a kĂ©pernyĆn. ElĆször elindĂtjuk a kĂ©pernyĆterminĂĄl multiplexert, majd megkezdjĂŒk a tesztelĂ©st az Apache benchmark segĂtsĂ©gĂ©vel. A kĂ©pernyĆvel valĂł munkavĂ©gzĂ©s mĂłdja itt talĂĄlhatĂł
1. szerverrĆl
while true; do ab -H "User-Agent: 1server" -c 100 -n 10 -t 10 http://vhost1/; sleep 1; done
2. szerverrĆl
while true; do ab -H "User-Agent: 2server" -c 100 -n 10 -t 10 http://vhost2/; sleep 1; done
3. szerverrĆl
while true; do ab -H "User-Agent: 3server" -c 100 -n 10 -t 10 http://vhost3/; sleep 1; done
4. szerverrĆl
while true; do ab -H "User-Agent: 4server" -c 100 -n 10 -t 10 http://vhost4/; sleep 1; done
NĂ©zzĂŒk meg az adatokat a Clickhouse-ban
Menj a Clickhouse-ba
clickhouse-client -h 172.26.10.109 -m
SQL lekĂ©rdezĂ©s kĂ©szĂtĂ©se
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 â â
ââââââââââââââââŽââââââââââââââââââââââŽââââââââââââââŽââââââââââŽâââââââââââââââââŽâââââââââââââââââââââŽââââââââââââââââââââŽââââââââââââââŽâââââââââââââââââŽâââââââââââââââââŽâââââââââââââââââŽâââââââââââââââŽâââââââââââââââââââŽââââââââââââââââââŽâââââââââââââââââââââââââââŽââââââââââââââââââââââââŽââââââââââââââââŽââââââââââââââŽââââââââââââââŽââââââââââââââââŽââââââââââââââââŽââââââââââââââââââââââââââŽââââââââââââââââââââââŽââââââââââââââââââââââââŽââââââââââââââââââââââââŽâââââââââââââââââââââââŽâââââââââââââââââââââââââââŽâââââââââââââââââââââââââŽââââââââââââââââââŽâââââââââââââââââââââââ
Tudja meg a Clickhouse asztalainak méretét
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;
NĂ©zzĂŒk meg, mennyi rönk foglalt el a Clickhouse-ban.
A naplótåblåzat mérete 857.19 MB.
Ugyanennek az adatnak a mérete az Elasticsearch indexében 4,5 GB.
Ha nem ad meg adatokat a vektorban a paraméterekben, akkor a Clickhouse 4500/857.19 = 5.24-szer kevesebbet vesz igénybe, mint az Elasticsearch-ben.
A vektorban alapĂ©rtelmezĂ©s szerint a tömörĂtĂ©si mezĆt hasznĂĄljĂĄk.
Telegram chat by
Telegram chat by
Telegram chat a következĆtĆl: "
ForrĂĄs: will.com