regex101.com<\/a> gibi siteleri kullanarak test etmek, beklenmedik hatalar\u0131 \u00f6nlemek a\u00e7\u0131s\u0131ndan kritik \u00f6neme sahiptir. Yanl\u0131\u015f bir RegEx, ya gereksiz loglar\u0131n ge\u00e7mesine ya da kritik loglar\u0131n d\u00fc\u015f\u00fcr\u00fclmesine neden olabilir.
\n <\/expert-tip><\/p>\n\n Bu kodu main.tf<\/code> dosyan\u0131za ekledikten sonra, de\u011fi\u015fiklikleri uygulamak i\u00e7in tekrar a\u015fa\u011f\u0131daki komutlar\u0131 \u00e7al\u0131\u015ft\u0131r\u0131n:\n <\/p>\n\nterraform plan<\/code>: Tan\u0131mlad\u0131\u011f\u0131n\u0131z kural\u0131n olu\u015fturulaca\u011f\u0131n\u0131 (+ create<\/code>) g\u00f6steren bir \u00e7\u0131kt\u0131 almal\u0131s\u0131n\u0131z.<\/li>\nterraform apply<\/code>: Terraform'un bu kural\u0131 New Relic hesab\u0131n\u0131zda olu\u015fturmas\u0131n\u0131 onaylamak i\u00e7in yes<\/code> yaz\u0131n.<\/li>\n<\/ul>\n\n Ba\u015far\u0131l\u0131 bir uygulaman\u0131n ard\u0131ndan, New Relic One aray\u00fcz\u00fcne (Log Management -> Pipeline Rules) giderek yeni olu\u015fturdu\u011funuz kural\u0131 g\u00f6rebilirsiniz. Bu sayede, log filtreleme stratejilerinizi kod ile y\u00f6netmeye ba\u015flam\u0131\u015f olursunuz. Bu temel ad\u0131mlar, daha karma\u015f\u0131k ge\u00e7i\u015f senaryolar\u0131 i\u00e7in sa\u011flam bir zemin olu\u015fturur.\n <\/p>\n
Ger\u00e7ek D\u00fcnya Senaryosu: Eski Drop Kurallar\u0131n\u0131 Pipeline Cloud Kurallar\u0131na Ta\u015f\u0131ma<\/h2>\n
\n Bir\u00e7ok kurulu\u015f, New Relic'teki log y\u00f6netimini optimize etmek amac\u0131yla eski Drop Kurallar\u0131n\u0131 kullanmaya ba\u015flam\u0131\u015ft\u0131r. Ancak, bu kurallar\u0131n s\u0131n\u0131rlamalar\u0131 g\u00f6z \u00f6n\u00fcne al\u0131nd\u0131\u011f\u0131nda, daha geli\u015fmi\u015f olan Pipeline Cloud Kurallar\u0131na ge\u00e7i\u015f yapmak ka\u00e7\u0131n\u0131lmaz bir hale gelmi\u015ftir. Bu ge\u00e7i\u015f s\u00fcreci, sadece teknolojik bir y\u00fckseltme de\u011fil, ayn\u0131 zamanda log verisi stratejinizi g\u00f6zden ge\u00e7irme ve maliyet optimizasyonu i\u00e7in yeni f\u0131rsatlar yaratma anlam\u0131na da gelir. Bu b\u00f6l\u00fcmde, ger\u00e7ek bir d\u00fcnya senaryosu \u00fczerinden eski Drop Kurallar\u0131n\u0131 Pipeline Cloud Kurallar\u0131na Terraform ile nas\u0131l ta\u015f\u0131yaca\u011f\u0131m\u0131z\u0131 ad\u0131m ad\u0131m inceleyece\u011fiz. Odak noktam\u0131z, veri g\u00fcr\u00fclt\u00fcs\u00fcn\u00fc azaltmak ve sadece eyleme ge\u00e7irilebilir loglar\u0131 tutmak olacak.\n <\/p>\n
Mevcut Drop Kurallar\u0131n\u0131 Anlama ve Envanterini \u00c7\u0131karma<\/h3>\n
\n Ge\u00e7i\u015fin ilk ve en kritik ad\u0131m\u0131, mevcut durumunuzu eksiksiz bir \u015fekilde anlamakt\u0131r. New Relic hesab\u0131n\u0131zda tan\u0131ml\u0131 olan t\u00fcm Drop Kurallar\u0131n\u0131n kapsaml\u0131 bir envanterini \u00e7\u0131karmal\u0131s\u0131n\u0131z. Bu envanter, her kural\u0131n ne yapt\u0131\u011f\u0131n\u0131, hangi loglar\u0131 etkiledi\u011fini ve ne kadar veri hacmini d\u00fc\u015f\u00fcrd\u00fc\u011f\u00fcn\u00fc i\u00e7ermelidir.\n <\/p>\n
\n- New Relic UI \u00dczerinden G\u00f6zden Ge\u00e7irme:<\/strong> New Relic One aray\u00fcz\u00fcnde \"Log Management\" b\u00f6l\u00fcm\u00fcne gidin ve \"Drop Filter Rules\" (veya benzer bir ba\u015fl\u0131k alt\u0131nda) mevcut kurallar\u0131n\u0131z\u0131 listeleyin. Her bir kural\u0131n a\u00e7\u0131klamas\u0131n\u0131, filtreleme desenini (genellikle bir RegEx veya anahtar kelime) ve etkin olup olmad\u0131\u011f\u0131n\u0131 dikkatlice not al\u0131n.<\/li>\n
- API veya NRQL ile Sorgulama:<\/strong> E\u011fer \u00e7ok say\u0131da Drop Kural\u0131n\u0131z varsa, bunlar\u0131 manuel olarak incelemek zaman al\u0131c\u0131 olabilir. New Relic API'si veya NRQL (New Relic Query Language) kullanarak bu kurallar\u0131n bir listesini \u00e7ekmek daha verimli olabilir. Mevcut Drop kurallar\u0131n\u0131n kendisi API taraf\u0131ndan y\u00f6netilemese de, d\u00fc\u015f\u00fcr\u00fclen loglar\u0131 g\u00f6zlemlemek i\u00e7in NRQL kullanabilirsiniz:
\n <\/p>\n\nFROM Log\nSELECT count(*)\nWHERE newrelic.logPattern = 'Dropped by Rule: [Rule Name]'\nFACET newrelic.logPattern\nSINCE 1 week ago\nTIMESERIES\n <\/pre>\n<\/code>
\n <\/code-block>
\n Bu sorgu, hangi Drop Kurallar\u0131n\u0131n ne kadar log d\u00fc\u015f\u00fcrd\u00fc\u011f\u00fcn\u00fc anlaman\u0131za yard\u0131mc\u0131 olabilir.<\/li>\n
- Ama\u00e7 ve Etki Analizi:<\/strong> Her kural i\u00e7in a\u015fa\u011f\u0131daki sorular\u0131 yan\u0131tlamaya \u00e7al\u0131\u015f\u0131n:\n
\n- Bu kural ne t\u00fcr loglar\u0131 d\u00fc\u015f\u00fcr\u00fcyor? (\u00d6rn:
DEBUG<\/code> loglar\u0131, belirli bir servisten gelen INFO<\/code> mesajlar\u0131, sa\u011fl\u0131k kontrol\u00fc loglar\u0131.)<\/li>\n- Bu loglar ger\u00e7ekten de\u011fersiz mi? D\u00fc\u015f\u00fcr\u00fclmesi operasyonel g\u00f6r\u00fcn\u00fcrl\u00fc\u011f\u00fcm\u00fcz\u00fc etkiler mi?<\/li>\n
- Kural hangi RegEx'i veya filtreyi kullan\u0131yor? Bu desen, Pipeline Cloud Kurallar\u0131 i\u00e7in nas\u0131l d\u00f6n\u00fc\u015ft\u00fcr\u00fclecek?<\/li>\n
- Bu kural\u0131n tahmini maliyet tasarrufu nedir?<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n
\n Vaka Analizi: Eski Bir Sistemin Yo\u011fun Hata Loglar\u0131n\u0131 Filtreleme<\/strong>
\n
\n Diyelim ki, eski bir Java uygulamam\u0131z (legacy-app<\/code>) var ve bu uygulama, belirli bir hata durumunda (\u00f6rne\u011fin, \"Connection timeout to external service\") dakikada y\u00fczlerce, hatta binlerce \"ERROR\" seviyesi log \u00fcretiyor. Ancak, bu spesifik hata genellikle kendi kendine \u00e7\u00f6z\u00fcl\u00fcyor ve s\u00fcrekli olarak uyar\u0131 vermek yerine, yaln\u0131zca belirli bir frekans\u0131n \u00fczerinde tekrarland\u0131\u011f\u0131nda bildirim almak istiyoruz. Mevcut bir Drop Kural\u0131, bu loglar\u0131 tamamen d\u00fc\u015f\u00fcr\u00fcyor ve bu da sorunun ger\u00e7ekte ne zaman ortaya \u00e7\u0131kt\u0131\u011f\u0131n\u0131 anlamam\u0131z\u0131 engelliyor. Amac\u0131m\u0131z, bu loglar\u0131n d\u00fc\u015f\u00fcr\u00fclmesini sa\u011flamak, ancak Pipeline Cloud Kurallar\u0131n\u0131n esnekli\u011finden faydalanarak daha sonra bu loglar\u0131 i\u015fleyebilir veya farkl\u0131 bir e\u015fikle uyar\u0131 verebilir hale gelmek.\n <\/p>\nGe\u00e7i\u015f Stratejileri ve D\u00f6n\u00fc\u015ft\u00fcrme Teknikleri<\/h3>\n
\n Mevcut Drop Kurallar\u0131n\u0131z\u0131n envanterini \u00e7\u0131kard\u0131ktan sonra, bunlar\u0131 Pipeline Cloud Kurallar\u0131na d\u00f6n\u00fc\u015ft\u00fcrme s\u00fcrecine ge\u00e7ebiliriz. Bu s\u00fcre\u00e7, stratejik bir yakla\u015f\u0131mla ele al\u0131nmal\u0131d\u0131r.\n <\/p>\n
\n- Tek Tek Ta\u015f\u0131ma ve Do\u011frulama:<\/strong> \u00d6zellikle kritik veya karma\u015f\u0131k kurallar i\u00e7in, her birini tek tek Pipeline Cloud Kural\u0131na d\u00f6n\u00fc\u015ft\u00fcr\u00fcp, uygulay\u0131p, ard\u0131ndan New Relic \u00fczerinde do\u011fru \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olmak en g\u00fcvenli yakla\u015f\u0131md\u0131r. Bu, potansiyel hatalar\u0131n etkisini minimize eder.<\/li>\n
- RegEx ve Filtre D\u00f6n\u00fc\u015f\u00fcm\u00fc:<\/strong> Drop Kurallar\u0131nda kullan\u0131lan RegEx desenlerini veya anahtar kelime filtrelerini, Pipeline Cloud Kurallar\u0131n\u0131n
matching_rules<\/code> yap\u0131s\u0131na uygun hale getirmeniz gerekecektir.\n\n- Basit String E\u015fle\u015fmesi:<\/strong> Drop Rule'da \"DEBUG\" anahtar kelimesini d\u00fc\u015f\u00fcren bir kural varsa:
\n <\/p>\n\n# Drop Rule (konsept)\n# Contains \"DEBUG\"\n\n# Pipeline Cloud Rule Terraform kar\u015f\u0131l\u0131\u011f\u0131:\nresource \"newrelic_cloud_pipeline_rule\" \"drop_debug_logs_migrated\" {\n account_id = var.new_relic_account_id\n description = \"Eski DEBUG drop kural\u0131n\u0131n yeni Pipeline versiyonu.\"\n enabled = true\n matching_rules {\n field = \"message\"\n operator = \"CONTAINS\"\n value = \"DEBUG\"\n }\n actions {\n action = \"drop\"\n }\n}\n <\/pre>\n<\/code>
\n <\/code-block>\n <\/li>\n
- Karma\u015f\u0131k RegEx E\u015fle\u015fmeleri:<\/strong> Drop Rule'da belirli bir hata desenini (\u00f6rne\u011fin, \"Connection timeout to external service for user ID \\d+\") i\u00e7eren loglar\u0131 d\u00fc\u015f\u00fcren bir kural varsa:
\n <\/p>\n\n# Drop Rule (konsept)\n# Regex: \"Connection timeout to external service for user ID \\d+\"\n\n# Pipeline Cloud Rule Terraform kar\u015f\u0131l\u0131\u011f\u0131:\nresource \"newrelic_cloud_pipeline_rule\" \"drop_legacy_app_connection_errors\" {\n account_id = var.new_relic_account_id\n description = \"Legacy uygulamas\u0131ndan gelen belirli ba\u011flant\u0131 zaman a\u015f\u0131m\u0131 hatalar\u0131n\u0131 d\u00fc\u015f\u00fcr\u00fcr.\"\n enabled = true\n matching_rules {\n field = \"message\"\n operator = \"MATCHES\"\n value = \"Connection timeout to external service for user ID \\\\d+\" # RegEx'te ters slash'lar\u0131 \u00e7iftleyin\n }\n matching_rules { # Ek ko\u015ful: sadece legacy-app'ten gelen loglar\n field = \"entity.name\" # Veya 'service.name', 'app.name' log yap\u0131n\u0131za g\u00f6re de\u011fi\u015fir\n operator = \"EQ\"\n value = \"legacy-app\"\n }\n actions {\n action = \"drop\"\n }\n}\n <\/pre>\n<\/code>
\n <\/code-block>
\n
\n Uzman \u0130pucu: RegEx ve Escape Karakterleri:<\/strong> Terraform'da RegEx kullan\u0131rken, \u00f6zellikle ters slash (\\<\/code>) gibi \u00f6zel karakterleri belirtmek i\u00e7in \u00e7ift ters slash (\\\\<\/code>) kullanman\u0131z gerekebilir. Bu, RegEx motorunun karakteri do\u011fru yorumlamas\u0131n\u0131 sa\u011flar. Her zaman RegEx'inizi bir test arac\u0131yla do\u011frulay\u0131n.
\n <\/expert-tip>\n <\/li>\n- Birden Fazla Ko\u015fulun Birle\u015ftirilmesi:<\/strong> Drop kurallar\u0131 genellikle tek bir desene odaklan\u0131rken, Pipeline kurallar\u0131 birden fazla
matching_rules<\/code> blo\u011fu ile AND<\/code> mant\u0131\u011f\u0131yla \u00e7al\u0131\u015f\u0131r. Bu, daha hassas filtreleme yapman\u0131z\u0131 sa\u011flar. \u00d6rne\u011fin, sadece legacy-app<\/code> servisinden gelen ERROR<\/code> seviyesindeki loglar\u0131 d\u00fc\u015f\u00fcrmek isteyebilirsiniz. Yukar\u0131daki \u00f6rnekte entity.name<\/code> ko\u015fulu eklenerek bu g\u00f6sterilmi\u015ftir.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\nGe\u00e7i\u015f Sonras\u0131 Do\u011frulama ve \u0130zleme<\/h3>\n
\n Drop kurallar\u0131n\u0131z\u0131 Pipeline Cloud kurallar\u0131na d\u00f6n\u00fc\u015ft\u00fcr\u00fcp Terraform ile uygulad\u0131ktan sonra, her \u015feyin beklendi\u011fi gibi \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olmak i\u00e7in kapsaml\u0131 bir do\u011frulama ve izleme s\u00fcreci y\u00fcr\u00fctmek hayati \u00f6nem ta\u015f\u0131r. Bu ad\u0131m, potansiyel veri kayb\u0131n\u0131 veya hatal\u0131 filtrelemeyi \u00f6nler.\n <\/p>\n
\n- New Relic Query Language (NRQL) ile Kural Etkinli\u011fini Do\u011frulama:<\/strong>\n
New Relic Log Explorer'da veya bir NRQL sorgu penceresinde, yeni Pipeline kurallar\u0131n\u0131z\u0131n etkinli\u011fini kontrol edebilirsiniz. \u00d6rne\u011fin, d\u00fc\u015f\u00fcrmeyi hedefledi\u011finiz loglar\u0131n art\u0131k g\u00f6r\u00fcnmedi\u011fini veya belirli bir d\u00f6n\u00fc\u015f\u00fcm\u00fcn ba\u015far\u0131yla uyguland\u0131\u011f\u0131n\u0131 do\u011frulayabilirsiniz.<\/p>\n
<\/p>\n\n# Drop edildi\u011fini bekledi\u011fimiz loglar\u0131n gelip gelmedi\u011fini kontrol etme\nFROM Log\nSELECT count(*)\nWHERE log_level = 'DEBUG' AND entity.name = 'my-application'\nSINCE 5 minutes ago\n\n# Eski drop kural\u0131n\u0131n yerine ge\u00e7en yeni kural\u0131n \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 kontrol etme (e\u011fer kural d\u00fc\u015f\u00fcrme yap\u0131yorsa, bu sorgu 0 sonu\u00e7 d\u00f6nmelidir)\nFROM Log\nSELECT *\nWHERE message LIKE '%Connection timeout to external service for user ID%' AND entity.name = 'legacy-app'\nSINCE 10 minutes ago\n <\/pre>\n<\/code>
\n <\/code-block><\/p>\n
Ayr\u0131ca, newrelic.ingest.log.drop<\/code> metri\u011fini kullanarak d\u00fc\u015f\u00fcr\u00fclen loglar\u0131n hacmini de izleyebilirsiniz. Bu metrik, Pipeline kurallar\u0131n\u0131n ne kadar veri d\u00fc\u015f\u00fcrd\u00fc\u011f\u00fcn\u00fc g\u00f6sterir.<\/p>\n<\/li>\n- Maliyet Etkisini \u0130zleme:<\/strong> Ge\u00e7i\u015fin ana motivasyonlar\u0131ndan biri maliyet optimizasyonu oldu\u011fundan, New Relic faturan\u0131z\u0131 ve veri al\u0131m hacminizi yak\u0131ndan takip edin. Beklenen d\u00fc\u015f\u00fc\u015fleri g\u00f6zlemleyebilmelisiniz. New Relic Usage sayfas\u0131 veya NRQL ile kullan\u0131m metriklerini sorgulayarak bu durumu izleyebilirsiniz.<\/li>\n
- Log Explorer'da Filtrelerin \u00c7al\u0131\u015ft\u0131\u011f\u0131n\u0131 G\u00f6rme:<\/strong> New Relic Log Explorer'\u0131 kullanarak canl\u0131 log ak\u0131\u015f\u0131n\u0131 g\u00f6zlemleyin. Yeni Pipeline kurallar\u0131n\u0131z\u0131n loglar\u0131 do\u011fru \u015fekilde d\u00fc\u015f\u00fcrd\u00fc\u011f\u00fcn\u00fc veya d\u00f6n\u00fc\u015ft\u00fcrd\u00fc\u011f\u00fcn\u00fc g\u00f6rsel olarak do\u011frulay\u0131n. Belirli filtreleri uygulayarak d\u00fc\u015f\u00fcrmeyi hedefledi\u011finiz loglar\u0131n ger\u00e7ekten g\u00f6r\u00fcnmedi\u011finden emin olun.<\/li>\n
- Eski Drop Kurallar\u0131n\u0131 Devre D\u0131\u015f\u0131 B\u0131rakma (A\u015famal\u0131):<\/strong> Yeni Pipeline Cloud Kurallar\u0131n\u0131n istikrarl\u0131 bir \u015fekilde \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olduktan sonra, ilgili eski Drop Kurallar\u0131n\u0131 a\u015famal\u0131 olarak devre d\u0131\u015f\u0131 b\u0131rakabilirsiniz. Bu, bir \"geri d\u00f6n\u00fc\u015f\" senaryosu i\u00e7in bir s\u00fcre hem eski hem de yeni kurallar\u0131n paralel \u00e7al\u0131\u015fmas\u0131na izin vermek anlam\u0131na gelebilir. Her \u015fey yolunda gitti\u011finde, eski Drop kurallar\u0131n\u0131 tamamen silebilirsiniz. Terraform ile yap\u0131lan ge\u00e7i\u015fte, eski kurallar New Relic provider taraf\u0131ndan y\u00f6netilmedi\u011fi i\u00e7in manuel olarak devre d\u0131\u015f\u0131 b\u0131rak\u0131lmal\u0131d\u0131r.<\/li>\n<\/ol>\n
\n Bu detayl\u0131 ge\u00e7i\u015f stratejisi, log y\u00f6netiminizin daha verimli, maliyet-etkin ve gelece\u011fe haz\u0131r olmas\u0131n\u0131 sa\u011flarken, operasyonel riskleri minimize etmenize yard\u0131mc\u0131 olacakt\u0131r. Terraform'un g\u00fcc\u00fc sayesinde, bu s\u00fcreci g\u00fcvenilir ve tekrarlanabilir bir \u015fekilde ger\u00e7ekle\u015ftirebilirsiniz.\n <\/p>\n
\u0130leri D\u00fczey Kullan\u0131m Senaryolar\u0131, En \u0130yi Uygulamalar ve Gelecek Perspektifleri<\/h2>\n
\n New Relic Pipeline Cloud Kurallar\u0131n\u0131n Terraform ile y\u00f6netimi, sadece eski Drop Kurallar\u0131ndan ge\u00e7i\u015f yapmakla kalmaz, ayn\u0131 zamanda log y\u00f6netimi stratejinizi daha da ileriye ta\u015f\u0131man\u0131z i\u00e7in yeni kap\u0131lar a\u00e7ar. Bu b\u00f6l\u00fcmde, daha karma\u015f\u0131k senaryolar, performans optimizasyonu, dinamik kural y\u00f6netimi ve modern dashboard entegrasyonu gibi ileri d\u00fczey konulara odaklanarak, log verilerinizden en y\u00fcksek de\u011feri nas\u0131l elde edebilece\u011finizi inceleyece\u011fiz. Bu ipu\u00e7lar\u0131, observability altyap\u0131n\u0131z\u0131n daha esnek, \u00f6l\u00e7eklenebilir ve maliyet etkin olmas\u0131n\u0131 sa\u011flayacakt\u0131r.\n <\/p>\n
Performans Optimizasyonu ve Maliyet Kontrol\u00fc<\/h3>\n
\n B\u00fcy\u00fck \u00f6l\u00e7ekli ortamlarda, Pipeline kurallar\u0131n\u0131n performans\u0131 ve dolay\u0131s\u0131yla maliyet etkisi \u00e7ok \u00f6nemlidir.\n <\/p>\n
\n- Kural S\u0131ralamas\u0131 ve Etkisi:<\/strong> Pipeline kurallar\u0131, belirli bir s\u0131raya g\u00f6re uygulan\u0131r. En y\u00fcksek hacimli loglar\u0131 d\u00fc\u015f\u00fcren veya en s\u0131k e\u015fle\u015fen kurallar\u0131 listenin ba\u015f\u0131na koymak, i\u015fleme maliyetlerini \u00f6nemli \u00f6l\u00e7\u00fcde azaltabilir. \u00d6rne\u011fin, t\u00fcm \"DEBUG\" loglar\u0131n\u0131 d\u00fc\u015f\u00fcren bir kural\u0131, daha spesifik bir uygulama hatas\u0131 kural\u0131ndan \u00f6nce \u00e7al\u0131\u015ft\u0131rarak, daha az logun di\u011fer kurallar taraf\u0131ndan i\u015flenmesini sa\u011flayabilirsiniz.<\/li>\n
- Agresif Filtreleme Stratejileri:<\/strong> Log verilerinizin \u00e7o\u011funun asl\u0131nda eyleme ge\u00e7irilemez oldu\u011funu fark ettiyseniz, \"varsay\u0131lan olarak d\u00fc\u015f\u00fcr, \u00f6nemli olan\u0131 tut\" yakla\u015f\u0131m\u0131n\u0131 benimseyebilirsiniz. \u00d6rne\u011fin, belirli bir uygulama i\u00e7in sadece \"ERROR\" ve \"WARN\" seviyesindeki loglar\u0131 tutarken, di\u011ferlerini d\u00fc\u015f\u00fcrmek i\u00e7in bir genel kural olu\u015fturabilirsiniz.<\/li>\n
- RegEx Verimlili\u011fi:<\/strong> RegEx'ler g\u00fc\u00e7l\u00fcd\u00fcr, ancak ayn\u0131 zamanda performans maliyeti de ta\u015f\u0131rlar. \u00c7ok karma\u015f\u0131k veya verimsiz RegEx desenleri, binlerce log \u00fczerinde uyguland\u0131\u011f\u0131nda i\u015fleme s\u00fcresini uzatabilir. M\u00fcmk\u00fcn oldu\u011funca spesifik ve basit RegEx'ler kullanmaya \u00e7al\u0131\u015f\u0131n. Alternatif olarak,
CONTAINS<\/code> veya EQ<\/code> gibi daha basit operat\u00f6rler, RegEx'lerden daha h\u0131zl\u0131 \u00e7al\u0131\u015f\u0131r.<\/li>\n<\/ul>\nDinamik Kurallar ve \u00c7evik Geli\u015ftirme Yakla\u015f\u0131m\u0131<\/h3>\n
\n Terraform'un sundu\u011fu programatik yetenekler sayesinde, Pipeline kurallar\u0131n\u0131z\u0131 dinamik olarak olu\u015fturabilir ve y\u00f6netebilirsiniz. Bu, \u00f6zellikle mikroservis mimarilerinde veya h\u0131zla de\u011fi\u015fen ortamlarda b\u00fcy\u00fck avantaj sa\u011flar.\n <\/p>\n
\n- Terraform
for_each<\/code> veya count<\/code> ile Dinamik Kural Setleri:<\/strong> Benzer kurallar\u0131 birden fazla uygulama veya ortam i\u00e7in tekrarlamak yerine, Terraform'un d\u00f6ng\u00fc yap\u0131lar\u0131n\u0131 (for_each<\/code>, count<\/code>) kullanarak dinamik olarak kurallar olu\u015fturabilirsiniz. \u00d6rne\u011fin, bir liste veya harita tan\u0131mlayarak her servis i\u00e7in belirli loglar\u0131 d\u00fc\u015f\u00fcren kurallar olu\u015fturabilirsiniz.
\n <\/p>\n\nlocals {\n services_to_monitor = [\n { name = \"user-service\", environment = \"production\" },\n { name = \"product-service\", environment = \"staging\" },\n # ... di\u011fer servisler\n ]\n}\n\nresource \"newrelic_cloud_pipeline_rule\" \"service_debug_drop\" {\n for_each = { for s in local.services_to_monitor : \"${s.name}-${s.environment}\" => s }\n\n account_id = var.new_relic_account_id\n description = \"DEBUG loglar\u0131n\u0131 d\u00fc\u015f\u00fcr: ${each.value.name} (${each.value.environment})\"\n enabled = true\n\n matching_rules {\n field = \"log_level\"\n operator = \"EQ\"\n value = \"DEBUG\"\n }\n matching_rules {\n field = \"service.name\" # veya loglar\u0131n\u0131za g\u00f6re ilgili alan\n operator = \"EQ\"\n value = each.value.name\n }\n matching_rules {\n field = \"environment\" # veya loglar\u0131n\u0131za g\u00f6re ilgili alan\n operator = \"EQ\"\n value = each.value.environment\n }\n\n actions {\n action = \"drop\"\n }\n}\n <\/pre>\n<\/code>
\n <\/code-block>
\n Bu \u00f6rnek, farkl\u0131 servisler ve ortamlar i\u00e7in dinamik olarak DEBUG log d\u00fc\u015f\u00fcrme kurallar\u0131 olu\u015fturur.\n <\/li>\n
- CI\/CD Entegrasyonu:<\/strong> Terraform yap\u0131land\u0131rman\u0131z\u0131 bir versiyon kontrol sisteminde (Git gibi) tutarak, CI\/CD i\u015flem hatt\u0131n\u0131za entegre edebilirsiniz. Bu sayede, bir kural de\u011fi\u015fikli\u011fi yap\u0131ld\u0131\u011f\u0131nda, otomatik olarak
terraform plan<\/code> ve terraform apply<\/code> ad\u0131mlar\u0131 \u00e7al\u0131\u015ft\u0131r\u0131larak de\u011fi\u015fiklikler test edilebilir ve g\u00fcvenli bir \u015fekilde da\u011f\u0131t\u0131labilir. Terraform Cloud veya Atlantis gibi ara\u00e7lar, bu s\u00fcre\u00e7leri daha da kolayla\u015ft\u0131r\u0131r.<\/li>\n<\/ul>\nMobil Uyumlu Dashboard Entegrasyonu (Media Query \u00d6rne\u011fi)<\/h3>\n
\n Pipeline Cloud Kurallar\u0131, log verilerinizi daha anlaml\u0131 hale getirerek, New Relic veya \u00f6zel dashboard'lar\u0131n\u0131zda daha temiz ve odaklanm\u0131\u015f g\u00f6rselle\u015ftirmeler sunman\u0131z\u0131 sa\u011flar. Log verilerinin filtrelenmesi ve d\u00f6n\u00fc\u015ft\u00fcr\u00fclmesi, bu dashboard'lar\u0131n daha h\u0131zl\u0131 y\u00fcklenmesine ve daha alakal\u0131 bilgiler sunmas\u0131na yard\u0131mc\u0131 olur. Modern web geli\u015ftirme pratiklerinde, bu t\u00fcr dashboard'lar\u0131n farkl\u0131 cihazlarda (mobil, tablet, masa\u00fcst\u00fc) iyi g\u00f6r\u00fcnmesi i\u00e7in mobil uyumluluk \u00f6nemlidir. \u0130\u015fte bu noktada, HTML ve CSS'deki media query'ler devreye girer.\n <\/p>\n
\n Bu makalenin \u00e7\u0131kt\u0131s\u0131 bir HTML i\u00e7eri\u011fi oldu\u011fu i\u00e7in, do\u011frudan kendi \u00e7\u0131kt\u0131m\u0131za medya sorgusu uygulayamasak da, filtrelenmi\u015f log verilerini t\u00fcketen ve g\u00f6steren bir dashboard'un nas\u0131l mobil uyumlu hale getirilebilece\u011fine dair bir \u00f6rnekle konuyu somutla\u015ft\u0131rabiliriz:\n <\/p>\n
<\/p>\n\n\n