{"id":33091,"date":"2025-10-29T11:41:24","date_gmt":"2025-10-29T08:41:24","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/?p=33091"},"modified":"2025-10-29T11:41:24","modified_gmt":"2025-10-29T08:41:24","slug":"topbeat-ve-elk-stack-ile-ubuntu-14-04-uzerinde-altyapi-metrikleri-toplama-rehberi","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/topbeat-ve-elk-stack-ile-ubuntu-14-04-uzerinde-altyapi-metrikleri-toplama-rehberi\/","title":{"rendered":"Topbeat ve ELK Stack ile Ubuntu 14.04 \u00dczerinde Altyap\u0131 Metrikleri Toplama Rehberi"},"content":{"rendered":"

<\/p>\n

Topbeat ve ELK Stack ile Ubuntu 14.04 \u00dczerinde Altyap\u0131 Metrikleri Toplama Rehberi<\/h2>\n

Giri\u015f<\/h3>\n

G\u00fcn\u00fcm\u00fcz\u00fcn h\u0131zla de\u011fi\u015fen IT ortamlar\u0131nda, altyap\u0131 bile\u015fenlerinin performans\u0131n\u0131 s\u00fcrekli olarak izlemek, olas\u0131 sorunlar\u0131 proaktif bir \u015fekilde tespit etmek ve sistemlerin genel sa\u011fl\u0131\u011f\u0131n\u0131 anlamak kritik \u00f6neme sahiptir. Sunucular, a\u011f cihazlar\u0131, depolama birimleri ve uygulamalar gibi farkl\u0131 katmanlardan gelen metrikleri toplamak ve analiz etmek, operasyonel verimlili\u011fi art\u0131rman\u0131n ve hizmet kesintilerini minimize etmenin temelini olu\u015fturur. Bu metrikler sayesinde, CPU kullan\u0131m\u0131, bellek t\u00fcketimi, disk G\/\u00c7 oranlar\u0131, a\u011f trafi\u011fi gibi hayati bilgiler elde edilebilir ve bu veriler \u0131\u015f\u0131\u011f\u0131nda performans darbo\u011fazlar\u0131 giderilebilir, kapasite planlamas\u0131 yap\u0131labilir ve sistem kaynaklar\u0131 daha etkin kullan\u0131labilir.<\/p>\n

Bu makalede, a\u00e7\u0131k kaynakl\u0131 ve olduk\u00e7a pop\u00fcler bir \u00e7\u00f6z\u00fcm olan ELK Stack (Elasticsearch, Logstash, Kibana) ile Topbeat kullanarak Ubuntu 14.04 i\u015fletim sistemi \u00fczerinde altyap\u0131 metriklerinin nas\u0131l toplanaca\u011f\u0131n\u0131, i\u015flenece\u011fini ve g\u00f6rselle\u015ftirilece\u011fini detayl\u0131 bir \u015fekilde ele alaca\u011f\u0131z. Ubuntu 14.04, g\u00fcncel bir i\u015fletim sistemi olmamakla birlikte, baz\u0131 eski altyap\u0131larda veya belirli projelerde hala kullan\u0131l\u0131yor olabilir. Bu nedenle, bu platform \u00fczerinde ELK Stack’in 6.x serisi ve Topbeat’in nas\u0131l kurulup yap\u0131land\u0131r\u0131laca\u011f\u0131n\u0131 ad\u0131m ad\u0131m g\u00f6sterece\u011fiz. Amac\u0131m\u0131z, okuyuculara pratik bir rehber sunarak kendi izleme \u00e7\u00f6z\u00fcmlerini kurmalar\u0131na yard\u0131mc\u0131 olmakt\u0131r.<\/p>\n

ELK Stack Nedir?<\/h3>\n

ELK Stack, Elasticsearch, Logstash ve Kibana olmak \u00fczere \u00fc\u00e7 ana bile\u015fenden olu\u015fan, log ve olay y\u00f6netimi i\u00e7in tasarlanm\u0131\u015f g\u00fc\u00e7l\u00fc bir a\u00e7\u0131k kaynakl\u0131 platformdur. Ancak zamanla, log toplaman\u0131n \u00f6tesine ge\u00e7erek metrik toplama, g\u00fcvenlik olaylar\u0131 y\u00f6netimi (SIEM) ve uygulama performans\u0131 izleme (APM) gibi geni\u015f bir kullan\u0131m alan\u0131na yay\u0131lm\u0131\u015ft\u0131r.<\/p>\n

Elasticsearch<\/h4>\n

Elasticsearch, Apache Lucene \u00fczerine in\u015fa edilmi\u015f, da\u011f\u0131t\u0131k, RESTful bir arama ve analiz motorudur. B\u00fcy\u00fck veri k\u00fcmelerini h\u0131zl\u0131 bir \u015fekilde depolayabilir, arayabilir ve analiz edebilir. JSON tabanl\u0131 belgeleri indeksler ve bunlar\u0131 yatay olarak \u00f6l\u00e7eklenebilir bir k\u00fcme yap\u0131s\u0131nda saklar. Metrik verileri gibi zaman serisi verileri i\u00e7in ideal bir depolama \u00e7\u00f6z\u00fcm\u00fcd\u00fcr, \u00e7\u00fcnk\u00fc bu veriler \u00fczerinde h\u0131zl\u0131 sorgulama ve toplama i\u015flemleri yap\u0131lmas\u0131na olanak tan\u0131r.<\/p>\n

Logstash<\/h4>\n

Logstash, \u00e7e\u015fitli kaynaklardan veri toplayabilen, i\u015fleyebilen ve farkl\u0131 hedeflere g\u00f6nderebilen dinamik bir veri i\u015fleme hatt\u0131d\u0131r. \u00c7e\u015fitli giri\u015f (input) eklentileri (Beats, dosya, Syslog, Kafka vb.) sayesinde farkl\u0131 formatlardaki verileri alabilir. Filtre (filter) eklentileri (Grok, Mutate, Date, Geoip vb.) ile verileri ayr\u0131\u015ft\u0131rabilir, zenginle\u015ftirebilir ve d\u00f6n\u00fc\u015ft\u00fcrebilir. Son olarak, \u00e7\u0131k\u0131\u015f (output) eklentileri (Elasticsearch, Kafka, Redis vb.) arac\u0131l\u0131\u011f\u0131yla i\u015flenmi\u015f verileri istedi\u011finiz hedefe y\u00f6nlendirebilir. Logstash, verilerinizi Elasticsearch’e g\u00f6ndermeden \u00f6nce standartla\u015ft\u0131rmak ve temizlemek i\u00e7in g\u00fc\u00e7l\u00fc bir ara\u00e7t\u0131r.<\/p>\n

Kibana<\/h4>\n

Kibana, Elasticsearch’te depolanan verileri ke\u015ffetmek, analiz etmek ve g\u00f6rselle\u015ftirmek i\u00e7in kullan\u0131lan bir web aray\u00fcz\u00fcd\u00fcr. Kullan\u0131c\u0131 dostu aray\u00fcz\u00fc sayesinde, indekslenmi\u015f veriler \u00fczerinde arama yapabilir, \u00f6zel sorgular olu\u015fturabilir, farkl\u0131 g\u00f6rselle\u015ftirmeler (\u00e7izgi grafikler, pasta grafikler, histogramlar vb.) tasarlayabilir ve bu g\u00f6rselle\u015ftirmeleri bir araya getirerek dinamik panolar (dashboard) olu\u015fturabilirsiniz. Kibana, toplanan altyap\u0131 metriklerinin anla\u015f\u0131l\u0131r ve eyleme ge\u00e7irilebilir bir \u015fekilde sunulmas\u0131nda kritik bir rol oynar.<\/p>\n

Topbeat Nedir ve Neden Kullan\u0131l\u0131r?<\/h3>\n

Topbeat, Elastic Stack’in bir par\u00e7as\u0131 olan ve sunucular\u0131n\u0131zdan sistem metriklerini toplamak i\u00e7in tasarlanm\u0131\u015f hafif bir veri g\u00f6ndericisidir (shipper). “Beats” ailesinin bir \u00fcyesidir ve Filebeat (loglar i\u00e7in), Metricbeat (genel metrikler i\u00e7in), Packetbeat (a\u011f trafi\u011fi i\u00e7in) gibi di\u011fer Beats ara\u00e7lar\u0131yla birlikte \u00e7al\u0131\u015f\u0131r. Topbeat, \u00f6zellikle CPU kullan\u0131m\u0131, bellek t\u00fcketimi, disk G\/\u00c7 oranlar\u0131, a\u011f trafi\u011fi ve \u00e7al\u0131\u015fan s\u00fcre\u00e7ler gibi temel sistem kaynaklar\u0131n\u0131n anl\u0131k durumunu izlemek i\u00e7in kullan\u0131l\u0131r.<\/p>\n

Neden Topbeat Kullan\u0131l\u0131r?<\/strong>
\n* Hafif ve Kaynak Dostu:<\/strong> Topbeat, Go dilinde yaz\u0131lm\u0131\u015ft\u0131r ve \u00e7ok d\u00fc\u015f\u00fck sistem kaynaklar\u0131 t\u00fcketir. Bu sayede izlenen sunucular\u0131n performans\u0131n\u0131 olumsuz etkilemez.
\n* Kolay Kurulum ve Yap\u0131land\u0131rma:<\/strong> Kurulumu ve yap\u0131land\u0131rmas\u0131 olduk\u00e7a basittir. YAML tabanl\u0131 yap\u0131land\u0131rma dosyalar\u0131 ile kolayca ayarlanabilir.
\n* G\u00fcvenilir Veri \u0130letimi:<\/strong> Toplanan metrikleri do\u011frudan Elasticsearch’e veya Logstash arac\u0131l\u0131\u011f\u0131yla Elasticsearch’e g\u00fcvenli ve verimli bir \u015fekilde iletir. A\u011f kesintileri durumunda verileri \u00f6nbelle\u011fe alabilir ve ba\u011flant\u0131 yeniden kuruldu\u011funda g\u00f6ndermeye devam edebilir.
\n* \u00d6zelle\u015ftirilebilir Metrikler:<\/strong> Hangi metriklerin toplanaca\u011f\u0131n\u0131 ve ne s\u0131kl\u0131kla g\u00f6nderilece\u011fini yap\u0131land\u0131rma dosyas\u0131 \u00fczerinden belirleyebilirsiniz.
\n* ELK Stack ile Entegrasyon:<\/strong> ELK Stack ile sorunsuz bir \u015fekilde entegre olur. Toplanan metrikler Kibana’da kolayca g\u00f6rselle\u015ftirilebilir.<\/p>\n

Bu makalede, Topbeat’in sistem metriklerini nas\u0131l toplay\u0131p ELK Stack’e g\u00f6nderece\u011fini ad\u0131m ad\u0131m inceleyece\u011fiz.<\/p>\n

Sistem Gereksinimleri ve \u00d6n Haz\u0131rl\u0131klar<\/h3>\n

Ubuntu 14.04 \u00fczerinde ELK Stack 6.x serisini ve Topbeat’i kurmak i\u00e7in baz\u0131 \u00f6n haz\u0131rl\u0131klar yapmam\u0131z gerekmektedir.<\/p>\n

Ubuntu 14.04 G\u00fcncelleme<\/h4>\n

Kuruluma ba\u015flamadan \u00f6nce sistemin g\u00fcncel oldu\u011fundan emin olmal\u0131y\u0131z. Bu, olas\u0131 ba\u011f\u0131ml\u0131l\u0131k sorunlar\u0131n\u0131 ve g\u00fcvenlik a\u00e7\u0131klar\u0131n\u0131 \u00f6nlemeye yard\u0131mc\u0131 olacakt\u0131r.<\/p>\n

sudo apt-get update\nsudo apt-get upgrade -y<\/code><\/pre>\n
Java Kurulumu<\/h4>\n
Elasticsearch ve Logstash, Java Runtime Environment (JRE) gerektirir. ELK Stack’in 6.x serisi i\u00e7in Java 8 (OpenJDK 8 veya Oracle Java 8) \u00f6nerilir. Ubuntu 14.04 varsay\u0131lan olarak eski Java s\u00fcr\u00fcmlerini i\u00e7erebilir, bu y\u00fczden Java 8’i manuel olarak kurmam\u0131z gerekecek. Burada OpenJDK 8’i kuraca\u011f\u0131z.<\/p>\n
sudo apt-get install software-properties-common -y\nsudo add-apt-repository ppa:openjdk-r\/ppa -y\nsudo apt-get update\nsudo apt-get install openjdk-8-jre -y<\/code><\/pre>\n
Kurulumdan sonra Java s\u00fcr\u00fcm\u00fcn\u00fc kontrol edelim:<\/p>\n
java -version<\/code><\/pre>\n
\u00c7\u0131kt\u0131, Java 1.8.x s\u00fcr\u00fcm\u00fcn\u00fc g\u00f6stermelidir.<\/p>\n
Elastic Stack Depo Anahtar\u0131 ve Depo Ekleme<\/h4>\n
Elastic Stack bile\u015fenlerini APT paket y\u00f6neticisi arac\u0131l\u0131\u011f\u0131yla kurabilmek i\u00e7in Elastic’in GPG anahtar\u0131n\u0131 ve depo adresini sistemimize eklememiz gerekmektedir.<\/p>\n
wget -qO - https:\/\/artifacts.elastic.co\/GPG-KEY-elasticsearch | sudo apt-key add -\necho \"deb https:\/\/artifacts.elastic.co\/packages\/6.x\/apt stable main\" | sudo tee -a \/etc\/apt\/sources.list.d\/elastic-6.x.list\nsudo apt-get update<\/code><\/pre>\n
Bu komutlar, Elastic’in genel anahtar\u0131n\u0131 ekler ve Elastic 6.x depo URL’sini \/etc\/apt\/sources.list.d\/elastic-6.x.list<\/code> dosyas\u0131na yazar. Son apt-get update<\/code> komutu, yeni depoyu sisteminize tan\u0131t\u0131r.<\/p>\n
ELK Stack Kurulumu<\/h3>\n
\u015eimdi Elastic Stack bile\u015fenlerini kurmaya ba\u015flayabiliriz.<\/p>\n
Elasticsearch Kurulumu<\/h4>\n
Elasticsearch’\u00fc kurmak olduk\u00e7a basittir:<\/p>\n
sudo apt-get install elasticsearch -y<\/code><\/pre>\n
Kurulumdan sonra, Elasticsearch’\u00fcn yap\u0131land\u0131rma dosyas\u0131n\u0131 (\/etc\/elasticsearch\/elasticsearch.yml<\/code>) d\u00fczenleyerek baz\u0131 temel ayarlar\u0131 yapmam\u0131z gerekecek. \u00d6zellikle network.host<\/code> ayar\u0131n\u0131, Elasticsearch’\u00fcn hangi IP adresinden eri\u015filebilir olaca\u011f\u0131n\u0131 belirtmek i\u00e7in de\u011fi\u015ftirmemiz \u00f6nemlidir. Tek bir sunucu \u00fczerinde \u00e7al\u0131\u015ft\u0131\u011f\u0131m\u0131z i\u00e7in localhost<\/code> veya sunucunun IP adresini kullanabiliriz.<\/p>\n
sudo nano \/etc\/elasticsearch\/elasticsearch.yml<\/code><\/pre>\n
A\u015fa\u011f\u0131daki sat\u0131rlar\u0131 bulun ve d\u00fczenleyin (veya ekleyin):<\/p>\n
# A node can have a name, which by default is a random ID.\n
# node.name: node-1<\/h2>\n\n
Use a descriptive name for your cluster:<\/h2>\n
# cluster.name: my-application<\/h2>\n\n
# ---------------------------------- Network -----------------------------------<\/h2>\n
# Set the bind address to a specific IP (IPv4 or IPv6):<\/h2>\n
network.host: localhost # Veya sunucunuzun IP adresi, \u00f6rn: \"192.168.1.100\"<\/h2>\n\n
Set a custom port for HTTP:<\/h2>\n
# http.port: 9200<\/code><\/pre>\n<\/h2>\n
network.host<\/code> ayar\u0131n\u0131 localhost<\/code> olarak b\u0131rakmak, Elasticsearch’e sadece ayn\u0131 sunucu \u00fczerinden eri\u015filebilece\u011fi anlam\u0131na gelir. E\u011fer ba\u015fka makinelerden de eri\u015fim sa\u011flamak istiyorsan\u0131z, sunucunun IP adresini belirtmelisiniz.<\/p>\n
De\u011fi\u015fiklikleri kaydedip \u00e7\u0131kt\u0131ktan sonra, Elasticsearch servisini ba\u015flat\u0131n ve sistem ba\u015flang\u0131c\u0131nda otomatik ba\u015flamas\u0131 i\u00e7in etkinle\u015ftirin:<\/p>\n
sudo systemctl daemon-reload # Ubuntu 14.04'te systemctl yerine init.d\/service kullan\u0131l\u0131r\nsudo service elasticsearch start\nsudo update-rc.d elasticsearch defaults 95 10 # Servisi otomatik ba\u015flatmak i\u00e7in<\/code><\/pre>\n
Elasticsearch’\u00fcn \u00e7al\u0131\u015f\u0131p \u00e7al\u0131\u015fmad\u0131\u011f\u0131n\u0131 kontrol etmek i\u00e7in taray\u0131c\u0131n\u0131zdan veya curl<\/code> ile http:\/\/localhost:9200<\/code> adresine eri\u015febilirsiniz:<\/p>\n
curl -X GET \"localhost:9200\/\"<\/code><\/pre>\n
Ba\u015far\u0131l\u0131 bir kurulumda, Elasticsearch k\u00fcme bilgileriyle ilgili bir JSON \u00e7\u0131kt\u0131s\u0131 almal\u0131s\u0131n\u0131z.<\/p>\n
Logstash Kurulumu<\/h4>\n
Logstash’\u0131 kurmak da Elasticsearch kadar basittir:<\/p>\n
sudo apt-get install logstash -y<\/code><\/pre>\n
Logstash kurulumundan sonra, varsay\u0131lan olarak herhangi bir yap\u0131land\u0131rma dosyas\u0131yla gelmez. Kendi pipeline’\u0131m\u0131z\u0131 olu\u015fturmam\u0131z gerekecek. \u015eimdilik sadece kurup b\u0131rakal\u0131m, Topbeat yap\u0131land\u0131rmas\u0131 ile birlikte Logstash pipeline’\u0131n\u0131 olu\u015fturaca\u011f\u0131z.<\/p>\n
Logstash servisini ba\u015flat\u0131n ve otomatik ba\u015flamas\u0131 i\u00e7in etkinle\u015ftirin:<\/p>\n
sudo service logstash start\nsudo update-rc.d logstash defaults 95 10<\/code><\/pre>\n
Kibana Kurulumu<\/h4>\n
Kibana’y\u0131 kurmak i\u00e7in:<\/p>\n
sudo apt-get install kibana -y<\/code><\/pre>\n
Kibana’n\u0131n yap\u0131land\u0131rma dosyas\u0131n\u0131 (\/etc\/kibana\/kibana.yml<\/code>) d\u00fczenlememiz gerekecek. server.host<\/code> ve elasticsearch.url<\/code> ayarlar\u0131n\u0131 kontrol edelim.<\/p>\n
sudo nano \/etc\/kibana\/kibana.yml<\/code><\/pre>\n
A\u015fa\u011f\u0131daki sat\u0131rlar\u0131 bulun ve d\u00fczenleyin:<\/p>\n
# Specifies the address to which the Kibana server will bind.\n
server.host: \"localhost\" # Veya sunucunuzun IP adresi, \u00f6rn: \"192.168.1.100\"<\/h2>\n\n
The URL of the Elasticsearch instance to use for all your queries.<\/h2>\n
elasticsearch.url: \"http:\/\/localhost:9200\"<\/code><\/pre>\n<\/h2>\n
server.host<\/code> ayar\u0131n\u0131 localhost<\/code> olarak b\u0131rakmak, Kibana’ya sadece ayn\u0131 sunucu \u00fczerinden eri\u015filebilece\u011fi anlam\u0131na gelir. E\u011fer Kibana’ya uzaktan eri\u015fmek istiyorsan\u0131z, sunucunun IP adresini belirtmelisiniz.<\/p>\n
De\u011fi\u015fiklikleri kaydedip \u00e7\u0131kt\u0131ktan sonra, Kibana servisini ba\u015flat\u0131n ve otomatik ba\u015flamas\u0131 i\u00e7in etkinle\u015ftirin:<\/p>\n
sudo service kibana start\nsudo update-rc.d kibana defaults 95 10<\/code><\/pre>\n
Kibana’n\u0131n \u00e7al\u0131\u015f\u0131p \u00e7al\u0131\u015fmad\u0131\u011f\u0131n\u0131 kontrol etmek i\u00e7in taray\u0131c\u0131n\u0131zdan http:\/\/:5601<\/code> adresine eri\u015fmeyi deneyin. Varsay\u0131lan olarak 5601 portunu kullan\u0131r. E\u011fer localhost<\/code> olarak yap\u0131land\u0131rd\u0131ysan\u0131z, sunucu \u00fczerinde bir taray\u0131c\u0131dan veya SSH t\u00fcnellemesi ile eri\u015febilirsiniz.<\/p>\n
Topbeat Kurulumu ve Yap\u0131land\u0131rmas\u0131<\/h3>\n
ELK Stack’in temel bile\u015fenlerini kurduktan sonra, s\u0131ra altyap\u0131 metriklerini toplayacak olan Topbeat’e geldi.<\/p>\n
Topbeat Kurulumu<\/h4>\n
Topbeat’i kurmak i\u00e7in daha \u00f6nce ekledi\u011fimiz Elastic deposunu kullanabiliriz:<\/p>\n
sudo apt-get install topbeat -y<\/code><\/pre>\n
Topbeat Yap\u0131land\u0131rmas\u0131<\/h4>\n
Topbeat’in ana yap\u0131land\u0131rma dosyas\u0131 \/etc\/topbeat\/topbeat.yml<\/code> konumundad\u0131r. Bu dosyay\u0131 d\u00fczenleyerek Topbeat’in hangi metrikleri toplayaca\u011f\u0131n\u0131 ve bunlar\u0131 nereye g\u00f6nderece\u011fini belirleyece\u011fiz.<\/p>\n
sudo nano \/etc\/topbeat\/topbeat.yml<\/code><\/pre>\n
Yap\u0131land\u0131rma dosyas\u0131nda dikkat etmemiz gereken ana b\u00f6l\u00fcmler \u015funlard\u0131r:<\/p>\n
1.  topbeat.procs<\/code> (\u0130ste\u011fe Ba\u011fl\u0131):<\/strong> Hangi s\u00fcre\u00e7lerin metriklerini toplayaca\u011f\u0131n\u0131z\u0131 belirler. Varsay\u0131lan olarak t\u00fcm s\u00fcre\u00e7leri izler.<\/p>\n
# Defines the processes to monitor.\n    topbeat.procs: [\".\"] # T\u00fcm s\u00fcre\u00e7leri izle\n    # topbeat.procs: [\"apache\", \"mysql\", \"nginx\"] # Sadece belirli s\u00fcre\u00e7leri izle<\/code><\/pre>\n
2.  output.elasticsearch<\/code> veya output.logstash<\/code>:<\/strong> Toplanan metriklerin do\u011frudan Elasticsearch’e mi yoksa Logstash arac\u0131l\u0131\u011f\u0131yla m\u0131 g\u00f6nderilece\u011fini belirler. Logstash \u00fczerinden g\u00f6ndermek, verileri daha fazla i\u015fleme yetene\u011fi sa\u011flar ve Elasticsearch \u00fczerindeki y\u00fck\u00fc azalt\u0131r. Biz bu rehberde Logstash \u00fczerinden g\u00f6ndermeyi tercih edece\u011fiz.<\/p>\n
    Logstash \u00c7\u0131k\u0131\u015f Yap\u0131land\u0131rmas\u0131 (\u00d6nerilen):<\/strong><\/p>\n
# ---------------------------- Logstash Output -----------------------------\n    output.logstash:\n      # The Logstash hosts\n      hosts: [\"localhost:5044\"] # Logstash'\u0131n \u00e7al\u0131\u015ft\u0131\u011f\u0131 sunucu ve port\n\n      # Optional SSL. By default is off.\n      # List of root certificates for SSL verification\n      # ssl.certificate_authorities: [\"\/etc\/pki\/root\/ca.pem\"]\n\n      # Certificate for SSL client authentication\n      # ssl.certificate: \"\/etc\/pki\/client\/cert.pem\"\n\n      # Client Key for SSL client authentication\n      # ssl.key: \"\/etc\/pki\/client\/cert.key\"<\/code><\/pre>\n
    output.logstash<\/code> b\u00f6l\u00fcm\u00fcn\u00fc etkinle\u015ftirin ve hosts<\/code> k\u0131sm\u0131n\u0131 Logstash’\u0131n dinledi\u011fi IP adresi ve port (varsay\u0131lan 5044) ile g\u00fcncelleyin. Di\u011fer output.elasticsearch<\/code> b\u00f6l\u00fcm\u00fcn\u00fc yorum sat\u0131r\u0131 yaparak devre d\u0131\u015f\u0131 b\u0131rak\u0131n.<\/p>\n
    Elasticsearch \u00c7\u0131k\u0131\u015f Yap\u0131land\u0131rmas\u0131 (Alternatif):<\/strong>
\n    E\u011fer Logstash kullanmak istemiyorsan\u0131z, do\u011frudan Elasticsearch’e g\u00f6nderebilirsiniz:<\/p>\n
# ---------------------------- Elasticsearch Output ----------------------------\n    output.elasticsearch:\n      # Array of hosts to connect to.\n      hosts: [\"localhost:9200\"] # Elasticsearch'\u0131n \u00e7al\u0131\u015ft\u0131\u011f\u0131 sunucu ve port\n\n      # Optional protocol and basic auth credentials.\n      # protocol: https\n      # username: \"elastic\"\n      # password: \"changeme\"<\/code><\/pre>\n
    Bu durumda output.logstash<\/code> b\u00f6l\u00fcm\u00fcn\u00fc yorum sat\u0131r\u0131 yap\u0131n.<\/p>\n
Yap\u0131land\u0131rma dosyas\u0131n\u0131 kaydettikten sonra, Topbeat servisini ba\u015flat\u0131n ve sistem ba\u015flang\u0131c\u0131nda otomatik ba\u015flamas\u0131 i\u00e7in etkinle\u015ftirin:<\/p>\n
Topbeat Servisini Ba\u015flatma<\/h4>\n
sudo service topbeat start\nsudo update-rc.d topbeat defaults 95 10<\/code><\/pre>\n
Topbeat’in durumunu kontrol etmek i\u00e7in:<\/p>\n
sudo service topbeat status<\/code><\/pre>\n
Her \u015fey yolundaysa, Topbeat metrikleri toplamaya ve yap\u0131land\u0131r\u0131ld\u0131\u011f\u0131 gibi Logstash’a (veya do\u011frudan Elasticsearch’e) g\u00f6ndermeye ba\u015flayacakt\u0131r.<\/p>\n
Logstash ile Veri \u0130\u015fleme (\u0130ste\u011fe Ba\u011fl\u0131 ama \u00d6nerilen)<\/h3>\n
Topbeat’ten gelen verileri Logstash \u00fczerinden i\u015flemek, verilerinizi daha tutarl\u0131 hale getirmenize ve Elasticsearch’e g\u00f6ndermeden \u00f6nce zenginle\u015ftirmenize olanak tan\u0131r.<\/p>\n
Logstash i\u00e7in yeni bir yap\u0131land\u0131rma dosyas\u0131 olu\u015ftural\u0131m:<\/p>\n
sudo nano \/etc\/logstash\/conf.d\/topbeat-pipeline.conf<\/code><\/pre>\n
Bu dosyaya a\u015fa\u011f\u0131daki i\u00e7eri\u011fi ekleyin:<\/p>\n
input {\n  beats {\n    port => 5044 # Topbeat'in veri g\u00f6nderdi\u011fi port\n  }\n}\n\nfilter {\n  # Topbeat verileri genellikle temiz gelir, ancak iste\u011fe ba\u011fl\u0131 olarak filtreler eklenebilir.\n  # \u00d6rne\u011fin, bir alan\u0131n tipini de\u011fi\u015ftirmek veya yeni bir alan eklemek i\u00e7in:\n  # mutate {\n  #   add_field => { \"env\" => \"production\" }\n  # }\n}\n\noutput {\n  elasticsearch {\n    hosts => [\"localhost:9200\"] # Elasticsearch'\u0131n \u00e7al\u0131\u015ft\u0131\u011f\u0131 sunucu ve port\n    index => \"topbeat-%{+YYYY.MM.dd}\" # G\u00fcnl\u00fck indeks olu\u015fturma\n    document_type => \"%{[@metadata][type]}\" # Topbeat'in g\u00f6nderdi\u011fi tip bilgisini kullan\n  }\n  stdout { # Hata ay\u0131klama i\u00e7in konsola \u00e7\u0131kt\u0131 alma\n    codec => rubydebug\n  }\n}<\/code><\/pre>\n
A\u00e7\u0131klamalar:<\/strong>
\n*   input { beats { port => 5044 } }<\/code><\/strong>: Logstash’\u0131n Beats istemcilerinden (Topbeat gibi) 5044 numaral\u0131 port \u00fczerinden ba\u011flant\u0131lar\u0131 dinlemesini sa\u011flar.
\n*   filter { ... }<\/code><\/strong>: Topbeat verileri genellikle iyi yap\u0131land\u0131r\u0131lm\u0131\u015f oldu\u011fundan, genellikle karma\u015f\u0131k filtreleme gerektirmez. Ancak, veriye \u00f6zel etiketler eklemek (mutate<\/code> filtresi ile) veya ba\u015fka d\u00f6n\u00fc\u015f\u00fcmler yapmak isterseniz bu b\u00f6l\u00fcm\u00fc kullanabilirsiniz.
\n*   output { elasticsearch { ... } }<\/code><\/strong>: \u0130\u015flenmi\u015f verileri Elasticsearch’e g\u00f6nderir.
\n    *   hosts<\/code>: Elasticsearch sunucusunun adresi ve portu.
\n    *   index<\/code>: Olu\u015fturulacak Elasticsearch indeksinin ad\u0131. topbeat-%{+YYYY.MM.dd}<\/code> format\u0131, her g\u00fcn i\u00e7in yeni bir indeks olu\u015fturulmas\u0131n\u0131 sa\u011flar, bu da veri y\u00f6netimi ve saklama politikalar\u0131 a\u00e7\u0131s\u0131ndan faydal\u0131d\u0131r.
\n    *   document_type<\/code>: Topbeat’in g\u00f6nderdi\u011fi @metadata<\/code> alan\u0131ndaki type<\/code> bilgisini belge tipi olarak kullan\u0131r. (Not: Elasticsearch 6.x ve sonras\u0131 s\u00fcr\u00fcmlerinde _type<\/code> kavram\u0131 deprecated edilmi\u015ftir, ancak Beats hala bu alan\u0131 g\u00f6nderebilir ve Logstash bunu kullanabilir. Daha yeni ELK s\u00fcr\u00fcmlerinde bu sat\u0131r kald\u0131r\u0131labilir veya farkl\u0131 bir yakla\u015f\u0131mla ele al\u0131nabilir.)
\n*   stdout { codec => rubydebug }<\/code><\/strong>: Hata ay\u0131klama amac\u0131yla i\u015flenen verileri Logstash konsoluna yazd\u0131r\u0131r. Kurulum ve test a\u015famas\u0131nda olduk\u00e7a faydal\u0131d\u0131r. Canl\u0131 sistemde kald\u0131r\u0131lmas\u0131 \u00f6nerilir.<\/p>\n
Yap\u0131land\u0131rma dosyas\u0131n\u0131 kaydettikten sonra, Logstash servisini yeniden ba\u015flat\u0131n ki yeni yap\u0131land\u0131rmay\u0131 y\u00fcklesin:<\/p>\n
sudo service logstash restart<\/code><\/pre>\n
Logstash’\u0131n sorunsuz \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olmak i\u00e7in \/var\/log\/logstash\/logstash-plain.log<\/code> dosyas\u0131n\u0131 kontrol edebilirsiniz. stdout<\/code> \u00e7\u0131kt\u0131s\u0131 sayesinde konsolda da verilerin akmaya ba\u015flad\u0131\u011f\u0131n\u0131 g\u00f6rebilirsiniz.<\/p>\n
Kibana ile Verileri G\u00f6rselle\u015ftirme<\/h3>\n
Metrikler Topbeat taraf\u0131ndan toplan\u0131p Logstash arac\u0131l\u0131\u011f\u0131yla Elasticsearch’e g\u00f6nderildikten sonra, s\u0131ra bu verileri Kibana ile anlaml\u0131 hale getirmeye gelir.<\/p>\n
Kibana’ya Eri\u015fim<\/h4>\n
Taray\u0131c\u0131n\u0131zdan http:\/\/:5601<\/code> adresine gidin. Kibana aray\u00fcz\u00fc kar\u015f\u0131n\u0131za gelecektir.<\/p>\n
Index Pattern Olu\u015fturma<\/h4>\n
Kibana’n\u0131n Elasticsearch’teki verilerinizi sorgulayabilmesi i\u00e7in bir indeks deseni (index pattern) olu\u015fturman\u0131z gerekir.
\n1.  Kibana aray\u00fcz\u00fcnde sol men\u00fcden “Management” (Y\u00f6netim) b\u00f6l\u00fcm\u00fcne t\u0131klay\u0131n.
\n2.  “Kibana” alt\u0131nda “Index Patterns” (\u0130ndeks Desenleri) se\u00e7ene\u011fini se\u00e7in.
\n3.  “Create index pattern” (\u0130ndeks deseni olu\u015ftur) butonuna t\u0131klay\u0131n.
\n4.  “Index pattern” alan\u0131na topbeat-*<\/code> yaz\u0131n ve “Next step” (Sonraki ad\u0131m) butonuna t\u0131klay\u0131n. Bu, topbeat-2023.10.27<\/code> gibi t\u00fcm Topbeat indekslerini kapsayacakt\u0131r.
\n5.  “Time Filter field name” (Zaman Filtresi alan\u0131 ad\u0131) a\u00e7\u0131l\u0131r men\u00fcs\u00fcnden @timestamp<\/code> \u00f6\u011fesini se\u00e7in. Bu, Kibana’n\u0131n zaman bazl\u0131 filtrelemeler yapabilmesi i\u00e7in \u00f6nemlidir.
\n6.  “Create index pattern” butonuna t\u0131klay\u0131n.<\/p>\n
Art\u0131k Kibana, Topbeat verilerinizi sorgulamaya haz\u0131rd\u0131r.<\/p>\n
Dashboard Olu\u015fturma<\/h4>\n
\u015eimdi Topbeat’ten gelen metrikleri g\u00f6rselle\u015ftirmek i\u00e7in bir pano (dashboard) olu\u015ftural\u0131m.<\/p>\n
1.  Kibana’n\u0131n sol men\u00fcs\u00fcnden “Discover” (Ke\u015ffet) b\u00f6l\u00fcm\u00fcne t\u0131klay\u0131n. Burada Topbeat’ten gelen ham verileri g\u00f6rebilirsiniz. Zaman aral\u0131\u011f\u0131n\u0131 sa\u011f \u00fcst k\u00f6\u015feden “Last 15 minutes” (Son 15 dakika) veya “Last 1 hour” (Son 1 saat) gibi bir de\u011fere ayarlay\u0131n.
\n2.  Sol men\u00fcden “Visualize” (G\u00f6rselle\u015ftir) b\u00f6l\u00fcm\u00fcne t\u0131klay\u0131n ve “Create new visualization” (Yeni g\u00f6rselle\u015ftirme olu\u015ftur) butonuna t\u0131klay\u0131n.
\n3.  \u00d6rnek G\u00f6rselle\u015ftirmeler:<\/strong><\/p>\n
    *   CPU Kullan\u0131m\u0131 (Line Chart):<\/strong>
\n        *   G\u00f6rselle\u015ftirme tipi olarak “Line” (\u00c7izgi) se\u00e7in.
\n        *   Y-Axis<\/code> (Y Ekseni) i\u00e7in:
\n            *   Aggregation: Max<\/code>
\n            *   Field: system.cpu.total.norm.pct<\/code> (veya system.cpu.total.pct<\/code> eski versiyonlarda)
\n        *   X-Axis<\/code> (X Ekseni) i\u00e7in:
\n            *   Aggregation: Date Histogram<\/code>
\n            *   Field: @timestamp<\/code>
\n            *   Interval: Auto<\/code> (veya 1m<\/code> gibi bir de\u011fer)
\n        *   “Apply changes” (De\u011fi\u015fiklikleri uygula) butonuna t\u0131klay\u0131n ve g\u00f6rselle\u015ftirmeyi “CPU Kullan\u0131m\u0131” ad\u0131yla kaydedin.<\/p>\n
    *   Bellek Kullan\u0131m\u0131 (Area Chart):<\/strong>
\n        *   G\u00f6rselle\u015ftirme tipi olarak “Area” (Alan) se\u00e7in.
\n        *   Y-Axis<\/code> (Y Ekseni) i\u00e7in:
\n            *   Aggregation: Max<\/code>
\n            *   Field: system.memory.used.pct<\/code>
\n        *   X-Axis<\/code> (X Ekseni) i\u00e7in:
\n            *   Aggregation: Date Histogram<\/code>
\n            *   Field: @timestamp<\/code>
\n            *   Interval: Auto<\/code>
\n        *   “Apply changes” butonuna t\u0131klay\u0131n ve g\u00f6rselle\u015ftirmeyi “Bellek Kullan\u0131m\u0131” ad\u0131yla kaydedin.<\/p>\n
    *   Disk G\/\u00c7 (Line Chart):<\/strong>
\n        *   G\u00f6rselle\u015ftirme tipi olarak “Line” se\u00e7in.
\n        *   Y-Axis<\/code> (Y Ekseni) i\u00e7in iki metrik ekleyin:
\n            *   Aggregation: Max<\/code>, Field: system.diskio.write.bytes<\/code>
\n            *   Aggregation: Max<\/code>, Field: system.diskio.read.bytes<\/code>
\n        *   X-Axis<\/code> (X Ekseni) i\u00e7in:
\n            *   Aggregation: Date Histogram<\/code>, Field: @timestamp<\/code>, Interval: Auto<\/code>
\n        *   “Apply changes” butonuna t\u0131klay\u0131n ve g\u00f6rselle\u015ftirmeyi “Disk G\/\u00c7” ad\u0131yla kaydedin.<\/p>\n
    *   A\u011f Trafi\u011fi (Line Chart):<\/strong>
\n        *   G\u00f6rselle\u015ftirme tipi olarak “Line” se\u00e7in.
\n        *   Y-Axis<\/code> (Y Ekseni) i\u00e7in iki metrik ekleyin:
\n            *   Aggregation: Max<\/code>, Field: system.network.out.bytes<\/code>
\n            *   Aggregation: Max<\/code>, Field: system.network.in.bytes<\/code>
\n        *   X-Axis<\/code> (X Ekseni) i\u00e7in:
\n            *   Aggregation: Date Histogram<\/code>, Field: @timestamp<\/code>, Interval: Auto<\/code>
\n        *   “Apply changes” butonuna t\u0131klay\u0131n ve g\u00f6rselle\u015ftirmeyi “A\u011f Trafi\u011fi” ad\u0131yla kaydedin.<\/p>\n
4.  Dashboard Olu\u015fturma:<\/strong>
\n    *   Sol men\u00fcden “Dashboard” (Pano) b\u00f6l\u00fcm\u00fcne t\u0131klay\u0131n ve “Create new dashboard” (Yeni pano olu\u015ftur) butonuna t\u0131klay\u0131n.
\n    *   “Add” (Ekle) butonuna t\u0131klayarak az \u00f6nce olu\u015fturdu\u011funuz g\u00f6rselle\u015ftirmeleri panoya ekleyin.
\n    *   G\u00f6rselle\u015ftirmeleri s\u00fcr\u00fckle-b\u0131rak y\u00f6ntemiyle d\u00fczenleyin ve boyutlar\u0131n\u0131 ayarlay\u0131n.
\n    *   Panoyu “Altyap\u0131 Metrikleri Panosu” gibi bir adla kaydedin.<\/p>\n
Art\u0131k Ubuntu 14.04 sunucunuzun temel altyap\u0131 metriklerini canl\u0131 olarak Kibana panonuzda izleyebilirsiniz.<\/p>\n
Performans ve \u00d6l\u00e7eklenebilirlik \u0130pu\u00e7lar\u0131<\/h3>\n
ELK Stack, do\u011fru yap\u0131land\u0131r\u0131ld\u0131\u011f\u0131nda ve y\u00f6netildi\u011finde olduk\u00e7a \u00f6l\u00e7eklenebilir bir \u00e7\u00f6z\u00fcmd\u00fcr. Ancak b\u00fcy\u00fck veri hacimleriyle u\u011fra\u015f\u0131rken baz\u0131 noktalara dikkat etmek \u00f6nemlidir.<\/p>\n
Veri Saklama Politikalar\u0131<\/h4>\n
Metrik verileri zamanla birikecek ve disk alan\u0131n\u0131z\u0131 dolduracakt\u0131r. Bu nedenle eski verileri otomatik olarak silmek veya ar\u015fivlemek i\u00e7in bir strateji belirlemeniz gerekir.
\n*   Index Lifecycle Management (ILM):<\/strong> ELK Stack’in daha yeni s\u00fcr\u00fcmlerinde (6.7 ve \u00fczeri) yerle\u015fik bir ILM \u00f6zelli\u011fi bulunur. Ancak 6.x serisinde bu \u00f6zellik tam olarak geli\u015fmi\u015f de\u011fildir.
\n*   Curator:<\/strong> Elastic’in curator<\/code> arac\u0131, indeksleri y\u00f6netmek i\u00e7in g\u00fc\u00e7l\u00fc bir komut sat\u0131r\u0131 arac\u0131d\u0131r. Belirli bir ya\u015ftan sonra indeksleri silebilir veya kapatabilir. Ubuntu 14.04’te pip install elasticsearch-curator<\/code> ile kurup yap\u0131land\u0131rabilirsiniz. \u00d6rne\u011fin, 30 g\u00fcnden eski indeksleri silmek i\u00e7in bir curator<\/code> i\u015fi tan\u0131mlayabilirsiniz.
\n*   Manuel Silme:<\/strong> En basit y\u00f6ntem, belirli aral\u0131klarla curl -X DELETE \"localhost:9200\/topbeat-YYYY.MM.DD\"<\/code> komutlar\u0131yla eski indeksleri manuel olarak silmektir.<\/p>\n
Donan\u0131m Gereksinimleri<\/h4>\n
ELK Stack, \u00f6zellikle Elasticsearch, donan\u0131m kaynaklar\u0131 a\u00e7\u0131s\u0131ndan talepkar olabilir.
\n*   RAM:<\/strong> Elasticsearch, sorgu ve indeksleme performans\u0131n\u0131 art\u0131rmak i\u00e7in bol miktarda RAM’e ihtiya\u00e7 duyar. Genellikle sunucunun RAM’inin yar\u0131s\u0131 Elasticsearch’e ayr\u0131l\u0131r (maksimum 30-32 GB).
\n*   CPU:<\/strong> Logstash ve Elasticsearch, veri i\u015fleme ve arama i\u015flemleri i\u00e7in g\u00fc\u00e7l\u00fc CPU’lara ihtiya\u00e7 duyar.
\n*   Disk:<\/strong> SSD’ler, \u00f6zellikle Elasticsearch i\u00e7in y\u00fcksek G\/\u00c7 performans\u0131ndan dolay\u0131 \u015fiddetle tavsiye edilir. Yeterli disk alan\u0131 oldu\u011fundan ve verilerinizi yedekledi\u011finizden emin olun.
\n*   A\u011f:<\/strong> ELK k\u00fcmesi i\u00e7indeki bile\u015fenler ve Beats ile ELK aras\u0131ndaki ileti\u015fim i\u00e7in y\u00fcksek bant geni\u015fli\u011fine sahip bir a\u011f \u00f6nemlidir.<\/p>\n
G\u00fcvenlik<\/h4>\n
ELK Stack’i g\u00fcvenli bir \u015fekilde da\u011f\u0131tmak kritik \u00f6neme sahiptir.
\n*   G\u00fcvenlik Duvar\u0131 (Firewall):<\/strong> Sunucular\u0131n\u0131zda g\u00fcvenlik duvar\u0131n\u0131 etkinle\u015ftirin (\u00f6rn: ufw<\/code>) ve sadece gerekli portlara (\u00f6rn: 9200, 5044, 5601, 22) eri\u015fime izin verin.
\n*   A\u011f Segmentasyonu:<\/strong> ELK Stack bile\u015fenlerini ayr\u0131 bir a\u011f segmentinde \u00e7al\u0131\u015ft\u0131rmak, g\u00fcvenlik risklerini azaltabilir.
\n*   Kimlik Do\u011frulama ve Yetkilendirme:<\/strong> Elasticsearch ve Kibana’ya eri\u015fimi korumak i\u00e7in kimlik do\u011frulama ve yetkilendirme mekanizmalar\u0131 kullan\u0131n. Elastic’in X-Pack’i (\u00fccretli veya temel s\u00fcr\u00fcmde baz\u0131 \u00fccretsiz \u00f6zellikler sunar) veya \u00fc\u00e7\u00fcnc\u00fc taraf \u00e7\u00f6z\u00fcmler (\u00f6rn: Nginx ile temel kimlik do\u011frulama) kullan\u0131labilir.
\n*   SSL\/TLS:<\/strong> Beats, Logstash ve Elasticsearch aras\u0131ndaki ileti\u015fimi SSL\/TLS ile \u015fifreleyerek veri g\u00fcvenli\u011fini art\u0131r\u0131n.<\/p>\n
Sorun Giderme (Troubleshooting)<\/h3>\n
Kurulum veya yap\u0131land\u0131rma s\u0131ras\u0131nda sorunlarla kar\u015f\u0131la\u015fmak olas\u0131d\u0131r. \u0130\u015fte yayg\u0131n sorunlar\u0131 gidermek i\u00e7in baz\u0131 ipu\u00e7lar\u0131:<\/p>\n
Log Kontrolleri<\/h4>\n
Her bile\u015fenin kendi log dosyalar\u0131 vard\u0131r ve bu dosyalar sorunlar\u0131n k\u00f6k nedenini anlamak i\u00e7in ilk bakman\u0131z gereken yerlerdir.
\n*   Elasticsearch:<\/strong> \/var\/log\/elasticsearch\/<\/code> alt\u0131ndaki log dosyalar\u0131.
\n*   Logstash:<\/strong> \/var\/log\/logstash\/<\/code> alt\u0131ndaki log dosyalar\u0131 (\u00f6zellikle logstash-plain.log<\/code>).
\n*   Kibana:<\/strong> \/var\/log\/kibana\/<\/code> alt\u0131ndaki log dosyalar\u0131.
\n*   Topbeat:<\/strong> \/var\/log\/topbeat\/<\/code> alt\u0131ndaki log dosyalar\u0131.<\/p>\n
Loglarda ERROR<\/code> veya WARN<\/code> seviyesindeki mesajlar\u0131 aray\u0131n.<\/p>\n
Port Kontrolleri<\/h4>\n
Bile\u015fenlerin do\u011fru portlarda dinleyip dinlemedi\u011fini ve birbirleriyle ileti\u015fim kurabildi\u011fini kontrol edin.
\n*   sudo netstat -tulnp<\/code> komutu ile a\u00e7\u0131k portlar\u0131 ve hangi servisin kulland\u0131\u011f\u0131n\u0131 g\u00f6rebilirsiniz.
\n    *   Elasticsearch: 9200
\n    *   Logstash (Beats input): 5044
\n    *   Kibana: 5601<\/p>\n
Yap\u0131land\u0131rma Dosyas\u0131 Hatalar\u0131<\/h4>\n
YAML yap\u0131land\u0131rma dosyalar\u0131 girinti (indentation) konusunda \u00e7ok hassast\u0131r. Yanl\u0131\u015f girintiler veya s\u00f6zdizimi hatalar\u0131 servislerin ba\u015flamamas\u0131na neden olabilir.
\n*   Yap\u0131land\u0131rma dosyalar\u0131n\u0131 d\u00fczenlerken dikkatli olun.
\n*   Logstash yap\u0131land\u0131rmalar\u0131n\u0131 test etmek i\u00e7in sudo -u logstash \/usr\/share\/logstash\/bin\/logstash -f \/etc\/logstash\/conf.d\/topbeat-pipeline.conf --config.test_and_exit<\/code> komutunu kullanabilirsiniz.<\/p>\n
Servis Durumu<\/h4>\n
Bile\u015fen servislerinin \u00e7al\u0131\u015f\u0131r durumda oldu\u011fundan emin olun.
\n*   sudo service elasticsearch status<\/code>
\n*   sudo service logstash status<\/code>
\n*   sudo service kibana status<\/code>
\n*   sudo service topbeat status<\/code>
\n\u00c7al\u0131\u015fm\u0131yorsa, start<\/code> yerine restart<\/code> komutunu kullan\u0131n ve loglar\u0131 kontrol edin.<\/p>\n
Sonu\u00e7<\/h3>\n
Bu makalede, Ubuntu 14.04 i\u015fletim sistemi \u00fczerinde Topbeat ve ELK Stack’in 6.x serisini kullanarak altyap\u0131 metriklerini toplama, i\u015fleme ve g\u00f6rselle\u015ftirme s\u00fcrecini ad\u0131m ad\u0131m ele ald\u0131k. Elasticsearch, Logstash ve Kibana’n\u0131n temel bile\u015fenlerini kurduk, Topbeat’i yap\u0131land\u0131rarak sistem metriklerini toplamas\u0131n\u0131 sa\u011flad\u0131k ve bu verileri Kibana’da anlaml\u0131 panolar halinde g\u00f6rselle\u015ftirdik. Ayr\u0131ca, performans, \u00f6l\u00e7eklenebilirlik ve g\u00fcvenlik konular\u0131nda \u00f6nemli ipu\u00e7lar\u0131 ve yayg\u0131n sorun giderme y\u00f6ntemlerini de payla\u015ft\u0131k.<\/p>\n
Bu rehber, eski bir sistem \u00fczerinde dahi olsa, g\u00fc\u00e7l\u00fc ve esnek bir izleme \u00e7\u00f6z\u00fcm\u00fcn\u00fc nas\u0131l hayata ge\u00e7irebilece\u011finizi g\u00f6stermektedir. Altyap\u0131 metriklerini etkin bir \u015fekilde izlemek, sistemlerinizin sa\u011fl\u0131\u011f\u0131n\u0131 koruman\u0131za, performans darbo\u011fazlar\u0131n\u0131 erkenden tespit etmenize ve genel operasyonel verimlili\u011finizi art\u0131rman\u0131za yard\u0131mc\u0131 olacakt\u0131r. Bu kurulum, daha karma\u015f\u0131k izleme ihtiya\u00e7lar\u0131n\u0131z i\u00e7in bir ba\u015flang\u0131\u00e7 noktas\u0131 olabilir ve \u00fczerine ekleyerek daha kapsaml\u0131 \u00e7\u00f6z\u00fcmler geli\u015ftirebilirsiniz. Unutmay\u0131n, iyi bir izleme altyap\u0131s\u0131, sorunlar\u0131 ortaya \u00e7\u0131kmadan \u00f6nce g\u00f6rmenizi ve proaktif m\u00fcdahalelerde bulunman\u0131z\u0131 sa\u011flar.<\/p>\n","protected":false},"excerpt":{"rendered":"Topbeat ve ELK Stack ile Ubuntu 14.04 \u00dczerinde Altyap\u0131 Metrikleri Toplama Rehberi\nGiri\u015f\nG\u00fcn\u00fcm\u00fcz\u00fcn h\u0131zla de\u011fi\u015fen IT ortamlar\u0131nda, altyap\u0131","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_page_header_type":"","csco_page_load_nextpost":"","csco_page_subscribe_form":"","csco_page_contact_form":"","footnotes":""},"categories":[1468],"tags":[],"class_list":{"0":"post-33091","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-ubuntu","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"\nTopbeat ve ELK Stack ile Ubuntu 14.04 \u00dczerinde Altyap\u0131 Metrikleri Toplama Rehberi - Kodlar\u0131n Gizemli D\u00fcnyas\u0131<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fatihsoysal.com\/blog\/topbeat-ve-elk-stack-ile-ubuntu-14-04-uzerinde-altyapi-metrikleri-toplama-rehberi\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Topbeat ve ELK Stack ile Ubuntu 14.04 \u00dczerinde Altyap\u0131 Metrikleri Toplama Rehberi\" \/>\n<meta property=\"og:description\" content=\"Topbeat ve ELK Stack ile Ubuntu 14.04 \u00dczerinde Altyap\u0131 Metrikleri Toplama Rehberi Giri\u015f G\u00fcn\u00fcm\u00fcz\u00fcn h\u0131zla de\u011fi\u015fen IT ortamlar\u0131nda, altyap\u0131\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/topbeat-ve-elk-stack-ile-ubuntu-14-04-uzerinde-altyapi-metrikleri-toplama-rehberi\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2025-10-29T08:41:24+00:00\" \/>\n<meta name=\"author\" content=\"Fatih Soysal\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"Fatih Soysal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"20 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/topbeat-ve-elk-stack-ile-ubuntu-14-04-uzerinde-altyapi-metrikleri-toplama-rehberi\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/topbeat-ve-elk-stack-ile-ubuntu-14-04-uzerinde-altyapi-metrikleri-toplama-rehberi\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"Topbeat ve ELK Stack ile Ubuntu 14.04 \u00dczerinde Altyap\u0131 Metrikleri Toplama Rehberi\",\"datePublished\":\"2025-10-29T08:41:24+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/topbeat-ve-elk-stack-ile-ubuntu-14-04-uzerinde-altyapi-metrikleri-toplama-rehberi\/\"},\"wordCount\":3223,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"articleSection\":[\"Ubuntu\"],\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/topbeat-ve-elk-stack-ile-ubuntu-14-04-uzerinde-altyapi-metrikleri-toplama-rehberi\/#respond\"]}],\"copyrightYear\":\"2025\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/topbeat-ve-elk-stack-ile-ubuntu-14-04-uzerinde-altyapi-metrikleri-toplama-rehberi\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/topbeat-ve-elk-stack-ile-ubuntu-14-04-uzerinde-altyapi-metrikleri-toplama-rehberi\/\",\"name\":\"Topbeat ve ELK Stack ile Ubuntu 14.04 \u00dczerinde Altyap\u0131 Metrikleri Toplama Rehberi - Kodlar\u0131n Gizemli D\u00fcnyas\u0131\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2025-10-29T08:41:24+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/topbeat-ve-elk-stack-ile-ubuntu-14-04-uzerinde-altyapi-metrikleri-toplama-rehberi\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/topbeat-ve-elk-stack-ile-ubuntu-14-04-uzerinde-altyapi-metrikleri-toplama-rehberi\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/topbeat-ve-elk-stack-ile-ubuntu-14-04-uzerinde-altyapi-metrikleri-toplama-rehberi\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Topbeat ve ELK Stack ile Ubuntu 14.04 \u00dczerinde Altyap\u0131 Metrikleri Toplama Rehberi\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/\",\"name\":\"Fatihsoysal.com\",\"description\":\"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim\",\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\",\"name\":\"Fatih Soysal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"contentUrl\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"width\":512,\"height\":512,\"caption\":\"Fatih Soysal\"},\"logo\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\"},\"description\":\"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Topbeat ve ELK Stack ile Ubuntu 14.04 \u00dczerinde Altyap\u0131 Metrikleri Toplama Rehberi - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fatihsoysal.com\/blog\/topbeat-ve-elk-stack-ile-ubuntu-14-04-uzerinde-altyapi-metrikleri-toplama-rehberi\/","og_locale":"tr_TR","og_type":"article","og_title":"Topbeat ve ELK Stack ile Ubuntu 14.04 \u00dczerinde Altyap\u0131 Metrikleri Toplama Rehberi","og_description":"Topbeat ve ELK Stack ile Ubuntu 14.04 \u00dczerinde Altyap\u0131 Metrikleri Toplama Rehberi Giri\u015f G\u00fcn\u00fcm\u00fcz\u00fcn h\u0131zla de\u011fi\u015fen IT ortamlar\u0131nda, altyap\u0131","og_url":"https:\/\/fatihsoysal.com\/blog\/topbeat-ve-elk-stack-ile-ubuntu-14-04-uzerinde-altyapi-metrikleri-toplama-rehberi\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2025-10-29T08:41:24+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"20 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/topbeat-ve-elk-stack-ile-ubuntu-14-04-uzerinde-altyapi-metrikleri-toplama-rehberi\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/topbeat-ve-elk-stack-ile-ubuntu-14-04-uzerinde-altyapi-metrikleri-toplama-rehberi\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"Topbeat ve ELK Stack ile Ubuntu 14.04 \u00dczerinde Altyap\u0131 Metrikleri Toplama Rehberi","datePublished":"2025-10-29T08:41:24+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/topbeat-ve-elk-stack-ile-ubuntu-14-04-uzerinde-altyapi-metrikleri-toplama-rehberi\/"},"wordCount":3223,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"articleSection":["Ubuntu"],"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/topbeat-ve-elk-stack-ile-ubuntu-14-04-uzerinde-altyapi-metrikleri-toplama-rehberi\/#respond"]}],"copyrightYear":"2025","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/topbeat-ve-elk-stack-ile-ubuntu-14-04-uzerinde-altyapi-metrikleri-toplama-rehberi\/","url":"https:\/\/fatihsoysal.com\/blog\/topbeat-ve-elk-stack-ile-ubuntu-14-04-uzerinde-altyapi-metrikleri-toplama-rehberi\/","name":"Topbeat ve ELK Stack ile Ubuntu 14.04 \u00dczerinde Altyap\u0131 Metrikleri Toplama Rehberi - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2025-10-29T08:41:24+00:00","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/topbeat-ve-elk-stack-ile-ubuntu-14-04-uzerinde-altyapi-metrikleri-toplama-rehberi\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/topbeat-ve-elk-stack-ile-ubuntu-14-04-uzerinde-altyapi-metrikleri-toplama-rehberi\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/topbeat-ve-elk-stack-ile-ubuntu-14-04-uzerinde-altyapi-metrikleri-toplama-rehberi\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Topbeat ve ELK Stack ile Ubuntu 14.04 \u00dczerinde Altyap\u0131 Metrikleri Toplama Rehberi"}]},{"@type":"WebSite","@id":"https:\/\/fatihsoysal.com\/blog\/#website","url":"https:\/\/fatihsoysal.com\/blog\/","name":"Fatihsoysal.com","description":"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim","publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1","name":"Fatih Soysal","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","contentUrl":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","width":512,"height":512,"caption":"Fatih Soysal"},"logo":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/"},"description":"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.","url":"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/"}]}},"yoast_meta":{"yoast_wpseo_title":"","yoast_wpseo_metadesc":"","yoast_wpseo_canonical":""},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/33091","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/comments?post=33091"}],"version-history":[{"count":1,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/33091\/revisions"}],"predecessor-version":[{"id":33092,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/33091\/revisions\/33092"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=33091"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=33091"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=33091"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}