, air a dhealbhadh gus dàta log, meatrach agus tachartasan a chruinneachadh, a thionndadh agus a chuir.
→
Air a sgrìobhadh ann an cànan Rust, tha e air a chomharrachadh le àrd-choileanadh agus caitheamh RAM ìosal an taca ris na analogues aige. A bharrachd air an sin, thathas a’ toirt mòran aire do ghnìomhan co-cheangailte ri ceartachd, gu sònraichte, an comas tachartasan nach deach a chuir a shàbhaladh gu bufair air diosc agus na faidhlichean a thionndadh.
A thaobh ailtireachd, tha Vector na router tachartais a gheibh teachdaireachdan bho aon no barrachd stòran, gu roghnach a’ cur a-steach thairis air na teachdaireachdan sin cruth-atharraichean, agus gan cur gu fear no dhà drèanaichean.
Tha Vector na àite airson filebeat agus logstash, faodaidh e a bhith an sàs anns an dà dhreuchd (faighinn agus cuir logaichean), barrachd fiosrachaidh mun deidhinn .
Ma tha an t-seine ann an Logstash air a thogail mar chur-a-steach → sìoltachan → toradh an uairsin ann an Vector tha e → →
Gheibhear eisimpleirean anns na sgrìobhainnean.
Tha an stiùireadh seo na stiùireadh ath-sgrùdaichte bho . Anns an stiùireadh tùsail tha giollachd geoip. Nuair a rinn thu deuchainn air geoip bho lìonra a-staigh, thug vectar mearachd seachad.
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=30Ma dh'fheumas duine geoip a phròiseasadh, thoir sùil air an stiùireadh tùsail bho .
Rèitichidh sinn am measgachadh de Nginx (logaichean ruigsinneachd) → Vector (Client | Filebeat) → Vector (Frithealaiche | Logstash) → fa leth ann an Clickhouse agus fa leth ann an Elasticsearch. Stàlaichidh sinn 4 frithealaichean. Ged is urrainn dhut a dhol seachad air le 3 frithealaichean.
Tha an sgeama rudeigin mar seo.
Cuir à comas Selinux air na frithealaichean agad gu lèir
sed -i 's/^SELINUX=.*/SELINUX=disabled/g' /etc/selinux/config
rebootBidh sinn a’ stàladh emuladair frithealaiche HTTP + goireasan air a h-uile frithealaiche
Mar emuladair frithealaiche HTTP cleachdaidh sinn от
Chan eil rpm aig Nodejs-stub-server. cruthaich rpm air a shon. rpm a chur ri chèile a’ cleachdadh
Cuir ris an stòr antonpatsev/nodejs-stub-server
yum -y install yum-plugin-copr epel-release
yes | yum copr enable antonpatsev/nodejs-stub-serverStàlaich nodejs-stub-server, slat-tomhais Apache agus ioma-fhillteadair crìochnachaidh sgrion air a h-uile frithealaiche
yum -y install stub_http_server screen mc httpd-tools screenCeartaich mi an ùine freagairt stub_http_server anns an fhaidhle /var/lib/stub_http_server/stub_http_server.js gus am biodh barrachd logaichean ann.
var max_sleep = 10;Nach cuir sinn air bhog stub_http_server.
systemctl start stub_http_server
systemctl enable stub_http_serverair an fhrithealaiche 3
Bidh ClickHouse a’ cleachdadh an t-seata stiùiridh SSE 4.2, mar sin mura h-eilear ag ràdh a chaochladh, bidh taic air a shon anns a’ phròiseasar a thathar a’ cleachdadh na riatanas siostam a bharrachd. Seo an àithne gus faighinn a-mach a bheil am pròiseasar gnàthach a’ toirt taic do SSE 4.2:
grep -q sse4_2 /proc/cpuinfo && echo "SSE 4.2 supported" || echo "SSE 4.2 not supported"An toiseach feumaidh tu an stòr oifigeil a cheangal:
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_64Gus pacaidean a stàladh feumaidh tu na h-òrdughan a leanas a ruith:
sudo yum install -y clickhouse-server clickhouse-clientLeig le clickhouse-server èisteachd ris a’ chairt lìonraidh san fhaidhle /etc/clickhouse-server/config.xml
<listen_host>0.0.0.0</listen_host>Ag atharrachadh ìre an logaidh bho lorg gu deasbaid
debug
Suidheachaidhean teannachaidh àbhaisteach:
min_compress_block_size 65536
max_compress_block_size 1048576Gus teannachadh Zstd a chuir an gnìomh, chaidh comhairle a thoirt dhut gun a bhith a’ beantainn ris an config, ach an àite DDL a chleachdadh.
Cha b’ urrainn dhomh faighinn a-mach mar a chleachdas mi teannachadh zstd tro DDL ann an Google. Mar sin dh’ fhàg mi e mar a tha.
Co-obraichean a bhios a’ cleachdadh zstd compression ann an Clickhouse, feuch an roinn thu an stiùireadh.
Gus am frithealaiche a thòiseachadh mar dheamhan, ruith:
service clickhouse-server startA-nis gluaisidh sinn air adhart gu bhith a 'stèidheachadh Clickhouse
Rach gu Clickhouse
clickhouse-client -h 172.26.10.109 -m172.26.10.109 - IP an fhrithealaiche far a bheil Clickhouse air a chuir a-steach.
Nach cruthaich sinn stòr-dàta vector
CREATE DATABASE vector;Feuch an dèan sinn cinnteach gu bheil an stòr-dàta ann.
show databases;Cruthaich clàr 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;Bidh sinn a’ dèanamh cinnteach gu bheil na bùird air an cruthachadh. Cuir air bhog sinn clickhouse-client agus iarrtas a dheanamh.
Rachamaid gu stòr-dàta vector.
use vector;
Ok.
0 rows in set. Elapsed: 0.001 sec.Bheir sinn sùil air na bùird.
show tables;
┌─name────────────────┐
│ logs │
└─────────────────────┘A’ stàladh elasticsearch air an 4mh frithealaiche gus an aon dàta a chuir gu Elasticsearch airson coimeas ri Clickhouse
Cuir iuchair rpm poblach ris
rpm --import https://artifacts.elastic.co/GPG-KEY-elasticsearchCruthaichidh sinn 2 repo:
/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-mdStàlaich elasticsearch agus kibana
yum install -y kibana elasticsearchLeis gum bi e ann an 1 leth-bhreac, feumaidh tu na leanas a chur ris an fhaidhle /etc/elasticsearch/elasticsearch.yml:
discovery.type: single-nodeGus an urrainn don vectar sin dàta a chuir gu elasticsearch bho fhrithealaiche eile, atharraichidh sinn network.host.
network.host: 0.0.0.0Gus ceangal ri kibana, atharraich am paramadair server.host anns an fhaidhle /etc/kibana/kibana.yml
server.host: "0.0.0.0"Seann agus cuir a-steach elasticsearch ann an autostart
systemctl enable elasticsearch
systemctl start elasticsearchagus kibana
systemctl enable kibana
systemctl start kibanaA’ rèiteachadh Elasticsearch airson modh aon-nòd 1 shard, 0 mac-samhail. Is coltaiche gum bi cruinneachadh mòr de luchd-frithealaidh agad agus chan fheum thu seo a dhèanamh.
Airson clàran-amais san àm ri teachd, ùraich an teamplaid bunaiteach:
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"}}' suidheachadh mar àite Logstash air server 2
yum install -y https://packages.timber.io/vector/0.9.X/vector-x86_64.rpm mc httpd-tools screenNach cuir sinn air dòigh Vector an àite Logstash. A’ deasachadh an fhaidhle /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"'S urrainn dhut an earrann transforms.nginx_parse_add_defaults atharrachadh.
bho a’ cleachdadh nan rèiteachaidhean sin airson CDN beag agus faodaidh grunn luachan a bhith ann an upstream_ *
Mar eisimpleir:
"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"Mura h-e seo an suidheachadh agad, faodar an roinn seo a dhèanamh nas sìmplidhe
Cruthaichidh sinn roghainnean seirbheis airson 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Às deidh dhut na bùird a chruthachadh, faodaidh tu Vector a ruith
systemctl enable vector
systemctl start vectorFaodar coimhead air logaichean vector mar seo:
journalctl -f -u vectorBu chòir inntrigidhean mar seo a bhith anns na logaichean
INFO vector::topology::builder: Healthcheck: Passed.
INFO vector::topology::builder: Healthcheck: Passed.Air an neach-dèiligidh (lìn frithealaiche) - 1d frithealaiche
Air an fhrithealaiche le nginx, feumaidh tu ipv6 a dhì-cheadachadh, leis gu bheil an clàr logaichean ann an taigh-cliog a’ cleachdadh an raon upstream_addr IPv4, leis nach bi mi a’ cleachdadh ipv6 am broinn an lìonraidh. Mura tèid ipv6 a chuir dheth, bidh mearachdan ann:
DB::Exception: Invalid IPv4 value.: (while read the value of key upstream_addr)Is dòcha luchd-leughaidh, cuir taic ipv6 ris.
Cruthaich am faidhle /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 = 1A 'cur an gnìomh nan roghainnean
sysctl --systemNach stàlaich sinn nginx.
Chaidh faidhle tasgaidh nginx a chur ris /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=trueStàlaich am pasgan nginx
yum install -y nginxAn toiseach, feumaidh sinn an cruth log a rèiteachadh ann an Nginx anns an fhaidhle /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;
}Gus nach bris thu an rèiteachadh gnàthach agad, leigidh Nginx leat grunn stiùiridhean access_log a bhith agad
access_log /var/log/nginx/access.log main; # Стандартный лог
access_log /var/log/nginx/access.json.log vector; # Новый лог в формате jsonNa dìochuimhnich riaghailt a chur ris airson logrotate airson logaichean ùra (mura h-eil am faidhle log a’ crìochnachadh le .log)
Thoir air falbh default.conf bho /etc/nginx/conf.d/
rm -f /etc/nginx/conf.d/default.confCuir aoigheachd mas-fhìor ris /etc/nginx/conf.d/vhost1.conf
server {
listen 80;
server_name vhost1;
location / {
proxy_pass http://172.26.10.106:8080;
}
}Cuir aoigheachd mas-fhìor ris /etc/nginx/conf.d/vhost2.conf
server {
listen 80;
server_name vhost2;
location / {
proxy_pass http://172.26.10.108:8080;
}
}Cuir aoigheachd mas-fhìor ris /etc/nginx/conf.d/vhost3.conf
server {
listen 80;
server_name vhost3;
location / {
proxy_pass http://172.26.10.109:8080;
}
}Cuir aoigheachd mas-fhìor ris /etc/nginx/conf.d/vhost4.conf
server {
listen 80;
server_name vhost4;
location / {
proxy_pass http://172.26.10.116:8080;
}
}Cuir luchd-aoigheachd brìgheil (172.26.10.106 ip den fhrithealaiche far a bheil nginx air a chuir a-steach) chun a h-uile frithealaiche chun fhaidhle /etc/hosts:
172.26.10.106 vhost1
172.26.10.106 vhost2
172.26.10.106 vhost3
172.26.10.106 vhost4Agus ma tha a h-uile dad deiseil an uairsin
nginx -t
systemctl restart nginxA-nis leig dhuinn a stàladh sinn fhèin
yum install -y https://packages.timber.io/vector/0.9.X/vector-x86_64.rpmCruthaichidh sinn faidhle roghainnean airson 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.targetAgus rèiteachadh an àite Filebeat anns an config /etc/vector/vector.toml. Is e seòladh IP 172.26.10.108 an seòladh IP aig an fhrithealaiche loga (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"Na dìochuimhnich an cleachdaiche vector a chuir ris a’ bhuidheann a tha a dhìth gus an urrainn dha faidhlichean log a leughadh. Mar eisimpleir, bidh nginx ann an centos a’ cruthachadh logaichean le còraichean buidhne adm.
usermod -a -G adm vectorFeuch an tòisich sinn air an t-seirbheis vector
systemctl enable vector
systemctl start vectorFaodar coimhead air logaichean vector mar seo:
journalctl -f -u vectorBu chòir inntrigeadh mar seo a bhith anns na logaichean
INFO vector::topology::builder: Healthcheck: Passed.Deuchainn Stress
Bidh sinn a’ dèanamh deuchainnean a’ cleachdadh slat-tomhais Apache.
Chaidh am pasgan httpd-tools a stàladh air a h-uile frithealaiche
Bidh sinn a’ tòiseachadh a’ dèanamh deuchainn le bhith a’ cleachdadh slat-tomhais Apache bho 4 frithealaichean eadar-dhealaichte air an sgrion. An toiseach, bidh sinn a’ cur air bhog an ioma-fhillteadair crìochnachaidh sgrion, agus an uairsin bidh sinn a’ tòiseachadh a’ dèanamh deuchainn le bhith a’ cleachdadh slat-tomhais Apache. Mar a dh’ obraicheas tu leis an scrion gheibh thu a-steach .
Bhon 1mh frithealaiche
while true; do ab -H "User-Agent: 1server" -c 100 -n 10 -t 10 http://vhost1/; sleep 1; doneBhon 2mh frithealaiche
while true; do ab -H "User-Agent: 2server" -c 100 -n 10 -t 10 http://vhost2/; sleep 1; doneBhon 3mh frithealaiche
while true; do ab -H "User-Agent: 3server" -c 100 -n 10 -t 10 http://vhost3/; sleep 1; doneBhon 4mh frithealaiche
while true; do ab -H "User-Agent: 4server" -c 100 -n 10 -t 10 http://vhost4/; sleep 1; doneFeuch an dèan sinn sgrùdadh air an dàta ann an Clickhouse
Rach gu Clickhouse
clickhouse-client -h 172.26.10.109 -mA 'dèanamh ceist 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 │ │
└──────────────┴─────────────────────┴─────────────┴─────────┴────────────────┴────────────────────┴───────────────────┴─────────────┴────────────────┴────────────────┴────────────────┴──────────────┴──────────────────┴─────────────────┴──────────────────────────┴───────────────────────┴───────────────┴─────────────┴─────────────┴───────────────┴───────────────┴─────────────────────────┴─────────────────────┴───────────────────────┴───────────────────────┴──────────────────────┴──────────────────────────┴────────────────────────┴─────────────────┴───────────────────────Faigh a-mach meud chlàran ann an 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;Feuch an lorg sinn a-mach na chaidh de logaichean suas ann an Clickhouse.
Is e meud clàr nan logaichean 857.19 MB.
Is e meud an aon dàta sa chlàr-amais ann an Elasticsearch 4,5GB.
Mura sònraich thu dàta anns an vectar anns na paramadairean, bheir Clickhouse 4500/857.19 = 5.24 tursan nas lugha na ann an Elasticsearch.
Ann am vector, tha an raon teannachaidh air a chleachdadh gu bunaiteach.
Telegram cabadaich le
Telegram cabadaich le
Telegram cabadaich le ""
Source: www.habr.com