Graphite-web:<\/strong>\nGraphite-web, Django web \u00e7er\u00e7evesi \u00fczerine in\u015fa edilmi\u015f bir Python uygulamas\u0131d\u0131r. Kullan\u0131c\u0131lar\u0131n depolanan metrik verilerini ke\u015ffetmelerini, grafikler olu\u015fturmalar\u0131n\u0131, panolar tasarlamalar\u0131n\u0131 ve verileri \u00e7e\u015fitli formatlarda (JSON, CSV, PNG) d\u0131\u015fa aktarmalar\u0131n\u0131 sa\u011flayan bir API ve kullan\u0131c\u0131 aray\u00fcz\u00fc sunar. Carbon’dan gelen verileri do\u011frudan Whisper dosyalar\u0131ndan okuyarak g\u00f6rselle\u015ftirir.<\/p>\n<\/li>\n<\/ol>\n
\u00d6n Gereksinimler ve Sistem Ayarlar\u0131<\/h3>\n
Graphite kurulumuna ba\u015flamadan \u00f6nce Ubuntu 14.04 sunucunuzun haz\u0131r oldu\u011fundan emin olmal\u0131s\u0131n\u0131z. Bu b\u00f6l\u00fcm, gerekli paketleri kurma ve sistemi haz\u0131rlama ad\u0131mlar\u0131n\u0131 i\u00e7erir.<\/p>\n
Sistem G\u00fcncellemesi<\/h4>\n
Herhangi bir kuruluma ba\u015flamadan \u00f6nce sistem paket listesini g\u00fcncellemek ve mevcut paketleri y\u00fckseltmek iyi bir uygulamad\u0131r:<\/p>\n
sudo apt-get update\nsudo apt-get upgrade -y\n<\/code><\/pre>\nGerekli Paketlerin Kurulumu<\/h4>\n
Graphite ve bile\u015fenlerinin \u00e7al\u0131\u015fmas\u0131 i\u00e7in baz\u0131 temel Python k\u00fct\u00fcphanelerine, geli\u015ftirme ara\u00e7lar\u0131na ve bir web sunucusuna ihtiyac\u0131m\u0131z olacak. Ubuntu 14.04 genellikle Python 2.7 ile gelir ve Graphite’\u0131n eski s\u00fcr\u00fcmleri bu Python s\u00fcr\u00fcm\u00fcn\u00fc kullan\u0131r. Python 3 deste\u011fi daha sonraki Graphite s\u00fcr\u00fcmlerinde eklenmi\u015ftir, ancak 14.04 i\u00e7in Python 2.7 tabanl\u0131 kurulum yapaca\u011f\u0131z.<\/p>\n
sudo apt-get install -y python-dev python-pip build-essential \\\nlibffi-dev libcairo2-dev pkg-config python-cairo apache2 libapache2-mod-wsgi\n<\/code><\/pre>\n\npython-dev<\/code>: Python C API’sini kullanmak i\u00e7in gerekli olan ba\u015fl\u0131k dosyalar\u0131n\u0131 ve statik k\u00fct\u00fcphaneleri sa\u011flar.<\/li>\npython-pip<\/code>: Python paketlerini y\u00f6netmek i\u00e7in kullan\u0131lan pip arac\u0131n\u0131 kurar.<\/li>\nbuild-essential<\/code>: Derleme i\u00e7in gerekli temel paketleri (gcc, make vb.) i\u00e7erir.<\/li>\nlibffi-dev<\/code>: C kodundan Python kodunu \u00e7a\u011f\u0131rmak i\u00e7in kullan\u0131lan bir k\u00fct\u00fcphane olan libffi<\/code>‘nin geli\u015ftirme dosyalar\u0131.<\/li>\nlibcairo2-dev<\/code>: Cairo grafik k\u00fct\u00fcphanesinin geli\u015ftirme dosyalar\u0131. Graphite, grafik olu\u015fturmak i\u00e7in Cairo’yu kullan\u0131r.<\/li>\npkg-config<\/code>: Derleme s\u0131ras\u0131nda k\u00fct\u00fcphanelerin konumunu ve ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131 bulmaya yard\u0131mc\u0131 olan bir ara\u00e7.<\/li>\npython-cairo<\/code>: Python i\u00e7in Cairo ba\u011flay\u0131c\u0131lar\u0131.<\/li>\napache2<\/code>: Web sunucusu.<\/li>\nlibapache2-mod-wsgi<\/code>: Apache’nin Python web uygulamalar\u0131n\u0131 (Django gibi) \u00e7al\u0131\u015ft\u0131rmas\u0131n\u0131 sa\u011flayan mod\u00fcl.<\/li>\n<\/ul>\nGraphite Kurulum Ad\u0131mlar\u0131<\/h3>\n
Art\u0131k sistemimiz haz\u0131r oldu\u011funa g\u00f6re, Graphite bile\u015fenlerini kurmaya ba\u015flayabiliriz.<\/p>\n
Ad\u0131m 1: Python Paketlerini Kurma<\/h4>\n
Graphite bile\u015fenlerini pip<\/code> kullanarak kuraca\u011f\u0131z. Bu, en basit ve \u00f6nerilen y\u00f6ntemdir.<\/p>\nsudo pip install carbon whisper graphite-web\n<\/code><\/pre>\nBu komut, carbon<\/code>, whisper<\/code> ve graphite-web<\/code> paketlerini sistem genelinde kuracakt\u0131r. Kurulum tamamland\u0131\u011f\u0131nda, bu paketlerin \u00e7al\u0131\u015ft\u0131r\u0131labilir dosyalar\u0131 genellikle \/usr\/local\/bin<\/code> dizinine, k\u00fct\u00fcphane dosyalar\u0131 ise \/usr\/local\/lib\/python2.7\/dist-packages<\/code> dizinine yerle\u015fir.<\/p>\nAd\u0131m 2: Konfig\u00fcrasyon Dosyalar\u0131 i\u00e7in Dizin Yap\u0131s\u0131 Olu\u015fturma<\/h4>\n
pip<\/code> ile kurulum, konfig\u00fcrasyon dosyalar\u0131n\u0131 do\u011frudan olu\u015fturmaz. Bu dosyalar\u0131 \u00f6rneklerinden kopyalamam\u0131z ve uygun bir yere yerle\u015ftirmemiz gerekecektir. Standart bir Graphite kurulumunda konfig\u00fcrasyon dosyalar\u0131 genellikle \/opt\/graphite\/conf<\/code> dizininde bulunur. Ancak biz pip<\/code> ile kurdu\u011fumuz i\u00e7in, bu dosyalar\u0131 uygun bir sistem dizinine, \u00f6rne\u011fin \/etc\/carbon<\/code> ve \/etc\/graphite-web<\/code>‘e kopyalayaca\u011f\u0131z. Ayr\u0131ca, Whisper verileri i\u00e7in bir dizin ve loglar i\u00e7in bir dizin olu\u015ftural\u0131m.<\/p>\nsudo mkdir -p \/etc\/carbon \/etc\/graphite-web\nsudo mkdir -p \/var\/lib\/graphite\/whisper\nsudo mkdir -p \/var\/log\/graphite\nsudo chown -R www-data:www-data \/var\/lib\/graphite\/whisper # Apache kullan\u0131c\u0131s\u0131na yazma izni\nsudo chown -R www-data:www-data \/var\/log\/graphite # Apache kullan\u0131c\u0131s\u0131na yazma izni\n<\/code><\/pre>\nwww-data<\/code> kullan\u0131c\u0131s\u0131 Apache’nin varsay\u0131lan kullan\u0131c\u0131s\u0131d\u0131r ve Graphite-web’in bu dizinlere eri\u015fmesi gerekecektir. Carbon servisi i\u00e7in de ayr\u0131 bir kullan\u0131c\u0131 olu\u015fturulabilir veya root<\/code> ile \u00e7al\u0131\u015ft\u0131r\u0131labilir, ancak daha g\u00fcvenli bir y\u00f6ntem, Carbon i\u00e7in ayr\u0131 bir kullan\u0131c\u0131 olu\u015fturup ona izin vermektir. Bu makalede basitle\u015ftirmek ad\u0131na, Carbon’un da ayn\u0131 kullan\u0131c\u0131 veya root yetkileriyle \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 varsayaca\u011f\u0131z, ancak \u00fcretim ortamlar\u0131nda g\u00fcvenlik g\u00f6z \u00f6n\u00fcnde bulundurulmal\u0131d\u0131r.<\/p>\nAd\u0131m 3: Carbon Yap\u0131land\u0131rmas\u0131<\/h4>\n
Carbon’un yap\u0131land\u0131rma dosyalar\u0131, carbon<\/code> paketinin y\u00fcklendi\u011fi dizinde \u00f6rnek olarak bulunur. Bunlar\u0131 \/etc\/carbon<\/code> dizinine kopyalayal\u0131m ve d\u00fczenleyelim.<\/p>\n# \u00d6rnek konfig\u00fcrasyon dosyalar\u0131n\u0131n bulundu\u011fu dizini bulal\u0131m\nGRAPHITE_CONF_DIR=$(python -c \"import carbon; print carbon.__path__[0] + '\/conf'\")\n\nsudo cp $GRAPHITE_CONF_DIR\/carbon.conf.example \/etc\/carbon\/carbon.conf\nsudo cp $GRAPHITE_CONF_DIR\/storage-schemas.conf.example \/etc\/carbon\/storage-schemas.conf\nsudo cp $GRAPHITE_CONF_DIR\/storage-aggregation.conf.example \/etc\/carbon\/storage-aggregation.conf\n<\/code><\/pre>\ncarbon.conf<\/code> Ayarlar\u0131<\/h5>\nBu dosya, Carbon bile\u015fenlerinin nas\u0131l \u00e7al\u0131\u015faca\u011f\u0131n\u0131 tan\u0131mlar. Varsay\u0131lan ayarlar \u00e7o\u011fu zaman yeterli olsa da, baz\u0131 \u00f6nemli parametreleri kontrol etmeliyiz.<\/p>\n
sudo nano \/etc\/carbon\/carbon.conf\n<\/code><\/pre>\n[cache]<\/code> b\u00f6l\u00fcm\u00fcnde a\u015fa\u011f\u0131daki ayarlar\u0131 kontrol edin:<\/p>\n[cache]\nENABLE_LOGGING = True\nLOCAL_DATA_DIR = \/var\/lib\/graphite\/whisper\nUSER = www-data # Carbon servisini www-data kullan\u0131c\u0131s\u0131 olarak \u00e7al\u0131\u015ft\u0131rmak i\u00e7in (iste\u011fe ba\u011fl\u0131)\nLINE_RECEIVER_INTERFACE = 0.0.0.0<\/h2>\nLINE_RECEIVER_PORT = 2003<\/h2>\nPICKLE_RECEIVER_INTERFACE = 0.0.0.0<\/h2>\nPICKLE_RECEIVER_PORT = 2004<\/h2>\nCACHE_QUERY_INTERFACE = 0.0.0.0<\/h2>\nCACHE_QUERY_PORT = 7002<\/h2>\n<\/code><\/pre>\n
LOCAL_DATA_DIR<\/code>‘in Whisper dosyalar\u0131n\u0131n depolanaca\u011f\u0131 dizin oldu\u011funu do\u011frulay\u0131n. USER<\/code> ayar\u0131, Carbon’un hangi kullan\u0131c\u0131 alt\u0131nda \u00e7al\u0131\u015faca\u011f\u0131n\u0131 belirler. E\u011fer Carbon’u ayr\u0131 bir kullan\u0131c\u0131 alt\u0131nda \u00e7al\u0131\u015ft\u0131rmak isterseniz, bu kullan\u0131c\u0131y\u0131 olu\u015fturup buraya yazman\u0131z ve ilgili dizinlere (\/var\/lib\/graphite\/whisper<\/code> ve \/var\/log\/graphite<\/code>) yazma izinleri vermeniz gerekir. Aksi takdirde, bu sat\u0131r\u0131 yorum sat\u0131r\u0131 yap\u0131n ve Carbon’u root<\/code> veya ba\u015fka bir yetkili kullan\u0131c\u0131 ile ba\u015flat\u0131n.<\/p>\nstorage-schemas.conf<\/code> Ayarlar\u0131<\/h5>\nBu dosya, Whisper veritabanlar\u0131n\u0131n metrikleri hangi \u00e7\u00f6z\u00fcn\u00fcrl\u00fckte ve ne kadar s\u00fcreyle saklayaca\u011f\u0131n\u0131 tan\u0131mlar. Bu, Graphite’\u0131n kalbi say\u0131l\u0131r \u00e7\u00fcnk\u00fc disk kullan\u0131m\u0131n\u0131 ve veri detay\u0131n\u0131 do\u011frudan etkiler.<\/p>\n
sudo nano \/etc\/carbon\/storage-schemas.conf\n<\/code><\/pre>\nVarsay\u0131lan olarak birka\u00e7 \u00f6rnek \u015fema bulunur. Kendi \u015feman\u0131z\u0131 olu\u015fturabilir veya mevcut olanlar\u0131 d\u00fczenleyebilirsiniz. \u00d6rne\u011fin, a\u015fa\u011f\u0131daki \u015fema t\u00fcm metrikleri (name = .*<\/code>) ilk 7 g\u00fcn boyunca 1 dakikal\u0131k \u00e7\u00f6z\u00fcn\u00fcrl\u00fckte ve sonraki 30 g\u00fcn boyunca 5 dakikal\u0131k \u00e7\u00f6z\u00fcn\u00fcrl\u00fckte saklayacakt\u0131r:<\/p>\n[carbon]\npattern = ^carbon\\.\nretentions = 60s:90d\n\n[default_1min_for_7days]\npattern = .*\nretentions = 60s:7d,5m:30d\n<\/code><\/pre>\nA\u00e7\u0131klama:<\/p>\n
\npattern = .<\/code>: Bu kural\u0131n t\u00fcm metrik adlar\u0131yla e\u015fle\u015fti\u011fini belirtir. Metrik adlar\u0131n\u0131 d\u00fczenli ifadelerle e\u015fle\u015ftirebilirsiniz (\u00f6rn. ^servers\\.web.<\/em><\/code>).<\/li>\nretentions = 60s:7d,5m:30d<\/code>: Bu, bir virg\u00fclle ayr\u0131lm\u0131\u015f bir dizi saklama kural\u0131d\u0131r.\n\n60s:7d<\/code>: Metrikleri 60 saniyelik aral\u0131klarla (1 dakika) 7 g\u00fcn boyunca sakla.<\/li>\n5m:30d<\/code>: 5 dakikal\u0131k aral\u0131klarla 30 g\u00fcn boyunca sakla. Bu, ilk 7 g\u00fcnden sonraki verilerin ortalamas\u0131n\u0131n al\u0131narak daha d\u00fc\u015f\u00fck \u00e7\u00f6z\u00fcn\u00fcrl\u00fckte saklanaca\u011f\u0131 anlam\u0131na gelir.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\nBu ayarlar\u0131 kaydedin ve kapat\u0131n.<\/p>\n
storage-aggregation.conf<\/code> Ayarlar\u0131<\/h5>\nBu dosya, Graphite’\u0131n farkl\u0131 \u00e7\u00f6z\u00fcn\u00fcrl\u00fck seviyelerine ge\u00e7erken metrik verilerini nas\u0131l birle\u015ftirece\u011fini (aggregate) tan\u0131mlar. \u00d6rne\u011fin, 1 dakikal\u0131k veriden 5 dakikal\u0131k veriye ge\u00e7erken ortalama m\u0131, toplam m\u0131, minimum mu yoksa maksimum mu al\u0131naca\u011f\u0131n\u0131 belirtir.<\/p>\n
sudo nano \/etc\/carbon\/storage-aggregation.conf\n<\/code><\/pre>\nVarsay\u0131lan ayarlar \u00e7o\u011fu zaman yeterlidir. \u0130\u015fte bir \u00f6rnek:<\/p>\n
[min]\npattern = \\.min$\nxFilesFactor = 0.1\naggregationMethod = min\n\n[max]\npattern = \\.max$\nxFilesFactor = 0.1\naggregationMethod = max\n\n[sum]\npattern = \\.sum$\nxFilesFactor = 0\naggregationMethod = sum\n\n[count]\npattern = \\.count$\nxFilesFactor = 0\naggregationMethod = sum\n\n[default_average]\npattern = .*\nxFilesFactor = 0.5\naggregationMethod = average\n<\/code><\/pre>\nA\u00e7\u0131klama:<\/p>\n
\npattern = .*<\/code>: Bu kural\u0131n t\u00fcm metrik adlar\u0131yla e\u015fle\u015fti\u011fini belirtir.<\/li>\nxFilesFactor = 0.5<\/code>: Bir \u00fcst \u00e7\u00f6z\u00fcn\u00fcrl\u00fck seviyesine ge\u00e7erken, bir veri noktas\u0131n\u0131n ge\u00e7erli say\u0131labilmesi i\u00e7in ne kadar\u0131n\u0131n (0.0 ile 1.0 aras\u0131nda) mevcut olmas\u0131 gerekti\u011fini belirtir. \u00d6rne\u011fin, 0.5 ise, 5 dakikal\u0131k bir ortalama olu\u015fturmak i\u00e7in en az 2.5 dakikal\u0131k veri olmas\u0131 gerekir.<\/li>\naggregationMethod = average<\/code>: Metriklerin birle\u015ftirilmesi s\u0131ras\u0131nda kullan\u0131lacak y\u00f6ntemi belirtir (average<\/code>, sum<\/code>, min<\/code>, max<\/code>, last<\/code>).<\/li>\n<\/ul>\nBu ayarlar\u0131 kaydedin ve kapat\u0131n.<\/p>\n
Ad\u0131m 4: Graphite-web Yap\u0131land\u0131rmas\u0131<\/h4>\n
Graphite-web, Django tabanl\u0131 bir uygulama oldu\u011fu i\u00e7in kendi yap\u0131land\u0131rma dosyalar\u0131na sahiptir. En \u00f6nemli dosya local_settings.py<\/code>‘dir.<\/p>\nlocal_settings.py<\/code> Dosyas\u0131n\u0131 Olu\u015fturma<\/h5>\n\u00d6rnek local_settings.py.example<\/code> dosyas\u0131n\u0131 kopyalayal\u0131m ve d\u00fczenleyelim. Bu dosya genellikle graphite_web<\/code> paketinin i\u00e7indedir.<\/p>\n# \u00d6rnek konfig\u00fcrasyon dosyalar\u0131n\u0131n bulundu\u011fu dizini bulal\u0131m\nGRAPHITE_WEB_CONF_DIR=$(python -c \"import graphite.app; print graphite.app.__path__[0] + '\/conf'\")\n\nsudo cp $GRAPHITE_WEB_CONF_DIR\/local_settings.py.example \/etc\/graphite-web\/local_settings.py\n<\/code><\/pre>\n\u015eimdi bu dosyay\u0131 d\u00fczenleyelim:<\/p>\n
sudo nano \/etc\/graphite-web\/local_settings.py\n<\/code><\/pre>\nA\u015fa\u011f\u0131daki ayarlar\u0131 g\u00fcncelleyin:<\/p>\n
# Bu sat\u0131r\u0131 bulun ve rastgele bir anahtar de\u011feri atay\u0131n\nSECRET_KEY = 'buraya_rastgele_uzun_bir_string_yazin' # \u00d6rne\u011fin: os.urandom(24).encode('hex') ile olu\u015fturulabilir\n\nVeritaban\u0131 ayarlar\u0131 (SQLite varsay\u0131lan olarak gelir, basit kurulum i\u00e7in yeterlidir)<\/h2>\nDATABASES = {\n 'default': {\n 'NAME': '\/var\/lib\/graphite\/graphite.db',\n 'ENGINE': 'django.db.backends.sqlite3',\n 'USER': '',\n 'PASSWORD': '',\n 'HOST': '',\n 'PORT': ''\n }\n}\n\nZaman dilimi ayar\u0131<\/h2>\nTIME_ZONE = 'Europe\/Istanbul' # Kendi zaman diliminize g\u00f6re ayarlay\u0131n\n\nWhisper veri dizinini belirtin<\/h2>\nWHISPER_DIR = '\/var\/lib\/graphite\/whisper'\n\nLog dizinini belirtin<\/h2>\nLOG_DIR = '\/var\/log\/graphite'\n\nStatik dosyalar\u0131n bulundu\u011fu dizin<\/h2>\nSTATIC_ROOT = '\/var\/www\/html\/graphite\/static' # Apache ile sunulacak statik dosyalar i\u00e7in\n<\/code><\/pre>\n
SECRET_KEY<\/code> i\u00e7in g\u00fc\u00e7l\u00fc, rastgele bir dize olu\u015fturdu\u011funuzdan emin olun. Django uygulamas\u0131n\u0131n g\u00fcvenli\u011fi i\u00e7in bu \u00e7ok \u00f6nemlidir. os.urandom(24).encode('hex')<\/code> gibi bir Python komutuyla kolayca olu\u015fturabilirsiniz. DATABASES<\/code> ayar\u0131 varsay\u0131lan olarak SQLite kullan\u0131r; bu, k\u00fc\u00e7\u00fck kurulumlar i\u00e7in uygundur. \u00dcretim ortamlar\u0131nda PostgreSQL veya MySQL gibi daha g\u00fc\u00e7l\u00fc bir veritaban\u0131 kullanman\u0131z \u00f6nerilir. TIME_ZONE<\/code>‘u kendi b\u00f6lgenize g\u00f6re ayarlay\u0131n. WHISPER_DIR<\/code> ve LOG_DIR<\/code>‘in daha \u00f6nce olu\u015fturdu\u011fumuz dizinleri i\u015faret etti\u011finden emin olun. STATIC_ROOT<\/code> ise Apache’nin sunaca\u011f\u0131 statik dosyalar\u0131n toplanaca\u011f\u0131 dizin olacak.<\/p>\nVeritaban\u0131 Ba\u015flatma ve Y\u00f6netici Olu\u015fturma<\/h5>\n
Graphite-web’in veritaban\u0131 \u015femas\u0131n\u0131 olu\u015fturmas\u0131 ve bir y\u00f6netici kullan\u0131c\u0131 olu\u015fturmas\u0131 gerekir. Bu i\u015flemi, Django’nun manage.py<\/code> komutuyla yapar\u0131z.<\/p>\n# manage.py dosyas\u0131n\u0131n bulundu\u011fu dizini bulal\u0131m\nGRAPHITE_WEB_APP_DIR=$(python -c \"import graphite.app; print graphite.app.__path__[0]\")\n\nsudo PYTHONPATH=$GRAPHITE_WEB_APP_DIR:$GRAPHITE_WEB_CONF_DIR:$PYTHONPATH \\\ndjango-admin.py syncdb --settings=graphite.app.settings --pythonpath=$GRAPHITE_WEB_APP_DIR\n<\/code><\/pre>\nBu komut \u00e7al\u0131\u015ft\u0131r\u0131ld\u0131\u011f\u0131nda, Django veritaban\u0131 tablolar\u0131n\u0131 olu\u015fturacak ve sizden bir y\u00f6netici kullan\u0131c\u0131 ad\u0131, e-posta ve parola olu\u015fturman\u0131z\u0131 isteyecektir. Bu bilgileri web aray\u00fcz\u00fcne giri\u015f yapmak i\u00e7in kullanacaks\u0131n\u0131z.<\/p>\n
Statik Dosyalar\u0131 Toplama<\/h5>\n
Django, web sunucusu taraf\u0131ndan do\u011frudan sunulacak olan t\u00fcm statik dosyalar\u0131 (CSS, JavaScript, resimler) tek bir dizinde toplaman\u0131za olanak tan\u0131r. Daha \u00f6nce STATIC_ROOT<\/code> olarak belirtti\u011fimiz dizini olu\u015ftural\u0131m ve dosyalar\u0131 oraya toplayal\u0131m:<\/p>\nsudo mkdir -p \/var\/www\/html\/graphite\/static\nsudo chown -R www-data:www-data \/var\/www\/html\/graphite\n\nsudo PYTHONPATH=$GRAPHITE_WEB_APP_DIR:$GRAPHITE_WEB_CONF_DIR:$PYTHONPATH \\\ndjango-admin.py collectstatic --noinput --settings=graphite.app.settings --pythonpath=$GRAPHITE_WEB_APP_DIR\n<\/code><\/pre>\n--noinput<\/code>, sorular\u0131 otomatik olarak yan\u0131tlar (\u00f6rne\u011fin, mevcut dosyalar\u0131n \u00fczerine yazma sorusu). Bu i\u015flem tamamland\u0131\u011f\u0131nda, Graphite-web’in statik dosyalar\u0131 \/var\/www\/html\/graphite\/static<\/code> dizininde bulunacakt\u0131r.<\/p>\nAd\u0131m 5: Web Sunucusu (Apache) Yap\u0131land\u0131rmas\u0131<\/h4>\n
Graphite-web bir Django uygulamas\u0131 oldu\u011fu i\u00e7in, bir web sunucusu (Apache veya Nginx) ve bir WSGI (Web Server Gateway Interface) sunucusu (mod_wsgi veya Gunicorn) arac\u0131l\u0131\u011f\u0131yla sunulmas\u0131 gerekir. Bu makalede Apache ve mod_wsgi<\/code> kullanaca\u011f\u0131z.<\/p>\ngraphite.wsgi<\/code> Dosyas\u0131n\u0131 Olu\u015fturma<\/h5>\nApache’nin Graphite-web uygulamas\u0131n\u0131 \u00e7al\u0131\u015ft\u0131rmas\u0131 i\u00e7in bir WSGI dosyas\u0131na ihtiyac\u0131m\u0131z var. Bu dosyay\u0131 \/etc\/graphite-web\/graphite.wsgi<\/code> olarak olu\u015ftural\u0131m:<\/p>\nsudo nano \/etc\/graphite-web\/graphite.wsgi\n<\/code><\/pre>\n\u0130\u00e7eri\u011fi a\u015fa\u011f\u0131daki gibi olmal\u0131:<\/p>\n
import sys\nimport os\n\nGraphite-web uygulamas\u0131n\u0131n k\u00f6k dizini<\/h2>\nGRAPHITE_ROOT = '\/usr\/local\/lib\/python2.7\/dist-packages\/graphite\/app' # pip ile kurulumda bu yol olabilir\nGRAPHITE_CONF = '\/etc\/graphite-web'\n\nsys.path.insert(0, GRAPHITE_ROOT)\nsys.path.insert(0, GRAPHITE_CONF) # local_settings.py i\u00e7in\n\nos.environ['DJANGO_SETTINGS_MODULE'] = 'settings' # Django ayarlar\u0131 i\u00e7in\nos.environ['GRAPHITE_SETTINGS_MODULE'] = 'local_settings' # Graphite'\u0131n \u00f6zel ayarlar\u0131 i\u00e7in\n\nfrom django.core.wsgi import get_wsgi_application\napplication = get_wsgi_application()\n<\/code><\/pre>\n
GRAPHITE_ROOT<\/code> de\u011fi\u015fkeninin, pip<\/code> taraf\u0131ndan kurulan Graphite-web uygulamas\u0131n\u0131n k\u00f6k dizinini do\u011fru bir \u015fekilde g\u00f6sterdi\u011finden emin olun. Genellikle \/usr\/local\/lib\/python2.7\/dist-packages\/graphite\/app<\/code> \u015feklindedir.<\/p>\nApache Sanal Host Ayar\u0131<\/h5>\n
\u015eimdi Apache i\u00e7in bir sanal host yap\u0131land\u0131rmas\u0131 olu\u015ftural\u0131m. Bu, Apache’nin belirli bir URL’ye gelen istekleri Graphite-web uygulamas\u0131na y\u00f6nlendirmesini sa\u011flayacakt\u0131r.<\/p>\n
sudo nano \/etc\/apache2\/sites-available\/graphite.conf\n<\/code><\/pre>\n\u0130\u00e7eri\u011fi a\u015fa\u011f\u0131daki gibi olmal\u0131:<\/p>\n
\n ServerName your_server_ip_or_domain # Sunucunuzun IP adresi veya alan ad\u0131n\u0131 buraya yaz\u0131n\n DocumentRoot \"\/var\/www\/html\/graphite\"\n\n # Statik dosyalar i\u00e7in\n Alias \/static\/ \"\/var\/www\/html\/graphite\/static\/\"\n \n Order deny,allow\n Allow from all\n <\/Directory>\n\n # Graphite-web uygulamas\u0131 i\u00e7in\n WSGIScriptAlias \/ \/etc\/graphite-web\/graphite.wsgi\n \n Order deny,allow\n Allow from all\n <\/Directory>\n\n ErrorLog ${APACHE_LOG_DIR}\/graphite_error.log\n CustomLog ${APACHE_LOG_DIR}\/graphite_access.log combined\n<\/VirtualHost>\n<\/code><\/pre>\nServerName<\/code>‘i sunucunuzun IP adresi veya alan ad\u0131yla de\u011fi\u015ftirmeyi unutmay\u0131n. Bu yap\u0131land\u0131rma, t\u00fcm gelen istekleri graphite.wsgi<\/code> dosyas\u0131na y\u00f6nlendirecek ve statik dosyalar\u0131 do\u011frudan Apache \u00fczerinden sunacakt\u0131r.<\/p>\nApache Sitesini Etkinle\u015ftirme ve Yeniden Ba\u015flatma<\/h5>\n
Yeni sanal host yap\u0131land\u0131rmas\u0131n\u0131 etkinle\u015ftirelim ve Apache’yi yeniden ba\u015flatal\u0131m:<\/p>\n
sudo a2ensite graphite.conf\nsudo service apache2 restart\n<\/code><\/pre>\nE\u011fer bir hata al\u0131rsan\u0131z, Apache’nin hata loglar\u0131n\u0131 (\/var\/log\/apache2\/error.log<\/code> veya \/var\/log\/apache2\/graphite_error.log<\/code>) kontrol edin.<\/p>\nAd\u0131m 6: Graphite Bile\u015fenlerini Ba\u015flatma<\/h4>\n
Carbon cache servisini ba\u015flatmam\u0131z gerekiyor. Bu servisi kal\u0131c\u0131 hale getirmek i\u00e7in bir init.d<\/code> beti\u011fi kullanaca\u011f\u0131z.<\/p>\nCarbon Cache Servisini Ba\u015flatma<\/h5>\n
\u00d6ncelikle, Carbon’un \u00e7al\u0131\u015ft\u0131r\u0131labilir dosyas\u0131n\u0131n yolunu bulal\u0131m (genellikle \/usr\/local\/bin\/carbon-cache.py<\/code>).<\/p>\nsudo \/usr\/local\/bin\/carbon-cache.py start\n<\/code><\/pre>\nBu komut Carbon’u ba\u015flat\u0131r, ancak sunucu yeniden ba\u015flat\u0131ld\u0131\u011f\u0131nda otomatik olarak ba\u015flamaz. Bunu sa\u011flamak i\u00e7in bir init.d<\/code> beti\u011fi olu\u015ftural\u0131m.<\/p>\nInit Script Olu\u015fturma (Ubuntu 14.04 i\u00e7in)<\/h5>\n
A\u015fa\u011f\u0131daki beti\u011fi \/etc\/init.d\/carbon-cache<\/code> olarak kaydedin:<\/p>\nsudo nano \/etc\/init.d\/carbon-cache\n<\/code><\/pre>\n\u0130\u00e7eri\u011fi:<\/p>\n
#!\/bin\/bash\n### BEGIN INIT INFO\nProvides: carbon-cache<\/h2>\nRequired-Start: $network $local_fs $remote_fs<\/h2>\nRequired-Stop: $network $local_fs $remote_fs<\/h2>\nDefault-Start: 2 3 4 5<\/h2>\nDefault-Stop: 0 1 6<\/h2>\nShort-Description: Start\/stop carbon-cache<\/h2>\nDescription: Carbon-cache daemon for Graphite<\/h2>\n### END INIT INFO\n\nVarsay\u0131lan de\u011ferler<\/h2>\nNAME=carbon-cache\nDAEMON=\/usr\/local\/bin\/$NAME.py # carbon-cache.py dosyas\u0131n\u0131n yolu\nCONF_DIR=\/etc\/carbon\nLOG_DIR=\/var\/log\/graphite\nPID_FILE=\/var\/run\/carbon-cache.pid\nUSER=www-data # Carbon'u hangi kullan\u0131c\u0131 alt\u0131nda \u00e7al\u0131\u015ft\u0131raca\u011f\u0131n\u0131z (iste\u011fe ba\u011fl\u0131)\n\nPYTHONPATH'i ayarlay\u0131n<\/h2>\nexport PYTHONPATH=\/usr\/local\/lib\/python2.7\/dist-packages:$PYTHONPATH\n\nLog dizinini ve PID dosyas\u0131n\u0131n dizinini olu\u015fturun<\/h2>\nmkdir -p $(dirname $PID_FILE)\nmkdir -p $LOG_DIR\nchown -R $USER:$USER $LOG_DIR\n\ncase \"$1\" in\n start)\n echo \"Starting $NAME...\"\n start-stop-daemon --start --quiet --pidfile $PID_FILE --chuid $USER --exec $DAEMON -- --config=$CONF_DIR\/carbon.conf --logdir=$LOG_DIR start\n echo \"$NAME started.\"\n ;;\n stop)\n echo \"Stopping $NAME...\"\n start-stop-daemon --stop --quiet --pidfile $PID_FILE\n echo \"$NAME stopped.\"\n ;;\n restart)\n echo \"Restarting $NAME...\"\n start-stop-daemon --stop --quiet --pidfile $PID_FILE\n sleep 1\n start-stop-daemon --start --quiet --pidfile $PID_FILE --chuid $USER --exec $DAEMON -- --config=$CONF_DIR\/carbon.conf --logdir=$LOG_DIR start\n echo \"$NAME restarted.\"\n ;;\n status)\n PID=$(cat $PID_FILE 2>\/dev\/null)\n if [ -n \"$PID\" ] && ps -p $PID > \/dev\/null; then\n echo \"$NAME is running with PID $PID\"\n else\n echo \"$NAME is not running\"\n fi\n ;;\n *)\n echo \"Usage: \/etc\/init.d\/$NAME {start|stop|restart|status}\"\n exit 1\n ;;\nesac\n\nexit 0\n<\/code><\/pre>\n
Bu beti\u011fi kaydettikten sonra, \u00e7al\u0131\u015ft\u0131r\u0131labilir hale getirin ve sistem ba\u015flang\u0131c\u0131nda otomatik olarak ba\u015flamas\u0131 i\u00e7in kaydedin:<\/p>\n
sudo chmod +x \/etc\/init.d\/carbon-cache\nsudo update-rc.d carbon-cache defaults\nsudo service carbon-cache start\n<\/code><\/pre>\nsudo service carbon-cache status<\/code> komutuyla Carbon’un \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 do\u011frulayabilirsiniz. Ayr\u0131ca, \/var\/log\/graphite\/carbon-cache\/carbon-cache.log<\/code> dosyas\u0131n\u0131 kontrol ederek herhangi bir hata olup olmad\u0131\u011f\u0131n\u0131 g\u00f6rebilirsiniz.<\/p>\nGraphite’a Veri G\u00f6nderme<\/h3>\n
Graphite’\u0131n \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olduktan sonra, ona metrik verileri g\u00f6ndermenin zaman\u0131 geldi. Graphite, varsay\u0131lan olarak 2003 numaral\u0131 TCP portundan basit metin tabanl\u0131 metrikleri dinler.<\/p>\n
Netcat ile Basit Bir Test<\/h4>\n
En basit test y\u00f6ntemi netcat<\/code> kullanmakt\u0131r. Bir metrik \u015fu formatta g\u00f6nderilir: metrik.ad\u0131 de\u011feri zaman_damgas\u0131<\/code>.<\/p>\necho \"test.metric 42 $(date +%s)\" | nc -q0 localhost 2003\n<\/code><\/pre>\nBu komut, test.metric<\/code> ad\u0131nda, de\u011feri 42<\/code> olan ve ge\u00e7erli Unix zaman damgas\u0131na sahip bir metrik g\u00f6nderir. -q0<\/code> parametresi, netcat<\/code>‘in veriyi g\u00f6nderdikten hemen sonra ba\u011flant\u0131y\u0131 kapatmas\u0131n\u0131 sa\u011flar.<\/p>\nPython ile Veri G\u00f6nderme<\/h4>\n
Daha programatik bir \u015fekilde veri g\u00f6ndermek i\u00e7in basit bir Python beti\u011fi kullanabiliriz:<\/p>\n
import socket\nimport time\nimport random\n\nCARBON_SERVER = 'localhost'\nCARBON_PORT = 2003\n\ndef send_metric(metric_name, value):\n timestamp = int(time.time())\n message = \"%s %s %s\\n\" % (metric_name, value, timestamp)\n print \"sending message:\\n%s\" % message\n sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)\n try:\n sock.connect((CARBON_SERVER, CARBON_PORT))\n sock.sendall(message)\n except Exception as e:\n print \"Error sending data: %s\" % e\n finally:\n sock.close()\n\nif __name__ == '__main__':\n while True:\n # Rastgele bir CPU kullan\u0131m\u0131 metri\u011fi g\u00f6nderelim\n cpu_usage = random.uniform(0, 100)\n send_metric(\"server.ubuntu1404.cpu.usage\", cpu_usage)\n\n # Rastgele bir bellek kullan\u0131m\u0131 metri\u011fi g\u00f6nderelim\n mem_usage = random.uniform(20, 80)\n send_metric(\"server.ubuntu1404.memory.usage\", mem_usage)\n\n time.sleep(5) # Her 5 saniyede bir veri g\u00f6nder\n<\/code><\/pre>\nBu beti\u011fi bir dosyaya kaydedip (\u00f6rn. send_metrics.py<\/code>) \u00e7al\u0131\u015ft\u0131rarak (python send_metrics.py<\/code>), Graphite’a s\u00fcrekli olarak \u00f6rnek veriler g\u00f6nderebilirsiniz.<\/p>\nStatsD ile Entegrasyon:<\/strong> Ger\u00e7ek d\u00fcnya uygulamalar\u0131nda, metrikleri do\u011frudan Graphite’a g\u00f6ndermek yerine genellikle StatsD<\/a> gibi bir arac\u0131 kullan\u0131l\u0131r. StatsD, uygulama metriklerini toplar, toplar ve belirli aral\u0131klarla Graphite’a g\u00f6nderir. Bu, uygulama taraf\u0131ndaki y\u00fck\u00fc azalt\u0131r ve metrik g\u00f6nderme i\u015flemini basitle\u015ftirir.<\/p>\nGraphite Web Aray\u00fcz\u00fcn\u00fc Kullanma<\/h3>\n
Art\u0131k metrikleriniz Graphite’a akmaya ba\u015flad\u0131\u011f\u0131na g\u00f6re, web aray\u00fcz\u00fcn\u00fc kullanarak bunlar\u0131 g\u00f6rselle\u015ftirebilirsiniz.<\/p>\n
Web Aray\u00fcz\u00fcne Eri\u015fim<\/h4>\n
Web taray\u0131c\u0131n\u0131z\u0131 a\u00e7\u0131n ve sunucunuzun IP adresine veya alan ad\u0131na gidin (\u00f6rn. http:\/\/your_server_ip\/<\/code>). Graphite-web giri\u015f ekran\u0131n\u0131 g\u00f6rmelisiniz. Daha \u00f6nce syncdb<\/code> komutuyla olu\u015fturdu\u011funuz y\u00f6netici kullan\u0131c\u0131 ad\u0131 ve \u015fifrenizle giri\u015f yap\u0131n.<\/p>\nGrafik Olu\u015fturma ve Ke\u015ffetme<\/h4>\n
Giri\u015f yapt\u0131ktan sonra, sol tarafta bir metrik a\u011fac\u0131 (metric tree) g\u00f6receksiniz. G\u00f6nderdi\u011finiz metrikler (\u00f6rn. test.metric<\/code> veya server.ubuntu1404.cpu.usage<\/code>) burada hiyerar\u015fik bir yap\u0131da listelenmelidir. Metrik a\u011fac\u0131ndan bir veya daha fazla metrik se\u00e7erek sa\u011f taraftaki panelde an\u0131nda bir grafik olu\u015fturabilirsiniz.<\/p>\nGraphite’\u0131n web aray\u00fcz\u00fc, grafiklerinizi \u00f6zelle\u015ftirmek i\u00e7in zengin i\u015flevler sunar:<\/p>\n
\n- Grafik Fonksiyonlar\u0131:<\/strong> Grafi\u011fin alt\u0131ndaki “Functions” men\u00fcs\u00fcnden \u00e7e\u015fitli fonksiyonlar\u0131 uygulayabilirsiniz (\u00f6rn.
sumSeries()<\/code>, averageSeries()<\/code>, scale()<\/code>, derivative()<\/code>). Bu fonksiyonlar, verileri d\u00f6n\u00fc\u015ft\u00fcrmenize, birle\u015ftirmenize veya farkl\u0131 \u015fekillerde analiz etmenize olanak tan\u0131r.<\/li>\n- Zaman Aral\u0131\u011f\u0131:<\/strong> Grafi\u011fin \u00fcst k\u0131sm\u0131ndaki zaman aral\u0131\u011f\u0131 se\u00e7icileri kullanarak verileri farkl\u0131 zaman dilimlerinde (son 1 saat, son 24 saat, son 7 g\u00fcn vb.) g\u00f6r\u00fcnt\u00fcleyebilirsiniz.<\/li>\n