Eminim belki bir \u00e7o\u011fumuz geleneksel .NET Framework \u00fczerinde geli\u015ftirdi\u011fimiz uygulamalarda,\u00a0NLog<\/em> library’si ile “NLog.Targets.Gelf<\/em>” paketini kullanarak, log’lama i\u015flemlerini GrayLog<\/em> \u00fczerinde ger\u00e7ekle\u015ftirmi\u015fizdir. Bir \u00f6nceki seri olan “ASP.NET Core Serisi 01: Dapper ile RESTful API Tasarlama ve Azure App Services\u2019e Deploy<\/em><\/a>” makalesinde, bu aralar ASP.NET Core \u00fczerinde \u00e7ok fazla \u00e7al\u0131\u015ft\u0131\u011f\u0131mdan bahsetmi\u015ftim. \u015euanda \u00e7al\u0131\u015ft\u0131\u011f\u0131m firmada yeni geli\u015ftirdi\u011fimiz API’lar\u0131, ASP.NET Core \u00fczerinde geli\u015ftirmeye \u00e7al\u0131\u015f\u0131yoruz. Bunun yan\u0131nda mevcut .NET stack’imiz i\u00e7erisindeki t\u00fcm log’lama i\u015flemlerimizi,\u00a0GrayLog<\/em> \u00fczerinde ger\u00e7ekle\u015ftirerek log’lama i\u015flemlerini merkezile\u015ftirmi\u015f durumday\u0131z.<\/p>\n K\u0131saca \u00f6neminden bahsetmek gerekirse e\u011fer:<\/p>\n Merkezi log’lama i\u015flemleri \u00f6zellikle son kullan\u0131c\u0131y\u0131 mutlu edebilmek i\u00e7in \u00e7ok \u00f6nemlidir. Ayr\u0131ca sistem performans\u0131n\u0131 s\u00fcrekli iyile\u015ftirebilmek ve hatalar\u0131n h\u0131zl\u0131ca fark\u0131na varabilmek i\u00e7in de \u00e7ok \u00f6nemli oldu\u011fu a\u015fikard\u0131r.<\/p><\/blockquote>\n Her neyse, ASP.NET Core<\/strong> \u00fczerinde development yaparken farkettim ki,\u00a0NLog<\/em>‘un “NLog.Targets.Gelf<\/em>” paketi hen\u00fcz ASP.NET Core ile uyumlu bir hale getirilmemi\u015f (yada ben bulamad\u0131m). Bende bir katk\u0131da bulunabilmek i\u00e7in ilgili kaynak kodu GitHub<\/em> \u00fczerinden fork’layarak, “NLog.Web.AspNetCore.Targets.Gelf<\/em><\/a>” ismi alt\u0131nda ASP.NET Core’a uyumlu bir hale getirdim ve\u00a0NuGet<\/em> server \u00fczerine publish ettim.<\/p>\n G\u00fcn\u00fcm\u00fcz \u00e7a\u011f\u0131nda sabit duran sistemlerden \u00e7ok, h\u0131zla de\u011fi\u015fen<\/strong> ve ya\u015fayan dinamik<\/strong> sistemlere sahibiz. Bununla birlikte da\u011f\u0131t\u0131k<\/strong> ve otonom<\/strong> bir \u015fekilde ya\u015fayan microservice’ler, kendini baz\u0131 rule’lara g\u00f6re dinamik olarak scale<\/strong> eden yap\u0131larada. Bu ya\u015fayan sistemlerin s\u00fcrekliliklerini<\/strong> sa\u011flayabilmek i\u00e7in, infrastructure’da neler olup bitti\u011fini bir noktada biliyor olmam\u0131z laz\u0131m. Bu sayede \u00f6zellikle son kullan\u0131c\u0131y\u0131 mutlu edebilmek i\u00e7in de\u011fi\u015fen uygulamalar\u0131 takip edebilmek, performans\u0131 s\u00fcrekli iyile\u015ftirebilmek ve hatalar kar\u015f\u0131s\u0131nda iz s\u00fcrebilerek h\u0131zl\u0131 aksiyonlar alabilmek m\u00fcmk\u00fcn olmaktad\u0131r. \u00d6zellikle distributed<\/strong>\u00a0bir \u015fekilde ya\u015fayan sisteme sahipsek ve log yap\u0131lar\u0131m\u0131z\u0131 merkezi bir platform \u00fczerine ta\u015f\u0131rsak, b\u00fct\u00fcn sistem i\u00e7erisinde belirli bir anda herhangi bir aksiyon ger\u00e7ekle\u015fti\u011fi an, tek bir noktadan monitor edebilme i\u015flemi \u00e7ok daha kolay olacakt\u0131r.<\/p>\n Merkezi log y\u00f6netimi i\u015flemini ger\u00e7ekle\u015ftirebilmek i\u00e7in, Splunk,<\/em>\u00a0Graylog<\/em>, Logstash<\/em>, Logwatch<\/em>\u00a0gibi bir \u00e7ok alternarif tool vard\u0131r. Biz bu makale i\u00e7erisinde ise ASP.NET Core application’\u0131 geli\u015ftirirken, NLog<\/em> library’si ile log’lar\u0131m\u0131z\u0131 GrayLog<\/em> i\u00e7erisinde tutabilme i\u015flemini ger\u00e7ekle\u015ftirece\u011fiz.<\/p>\n ve dahas\u0131…<\/p>\n A\u015fa\u011f\u0131daki “docker-compose.yml<\/em><\/strong>” dosyas\u0131n\u0131 kullanarak, GrayLog<\/em>‘u Docker<\/em> \u00fczerinde \u00e7al\u0131\u015ft\u0131raca\u011f\u0131z.<\/p>\n Bu i\u015flem i\u00e7in “aspnetcore-graylog-sample-with-nlog<\/em>” isminde bir folder olu\u015ftural\u0131m ve “docker-compose.yml<\/em>” dosyas\u0131n\u0131, i\u00e7erisine kopyalayal\u0131m. Bu i\u015flemin ard\u0131ndan herhangi bir command tool’u kullanarak a\u015fa\u011f\u0131daki komutu \u00e7al\u0131\u015ft\u0131ral\u0131m.<\/p>\n Bu i\u015flemin ard\u0131ndan GrayLog<\/em> UI’\u0131na, “http:\/\/192.168.99.100:9000<\/em>” bu URL \u00fczerinden eri\u015febiliriz.<\/p>\n NOT: Log in i\u015flemi i\u00e7in giri\u015f bilgileri “admin”, “admin” \u015feklindedir.<\/p><\/blockquote>\n GrayLog<\/em> kurulumu neredeyse haz\u0131r. NLog<\/em> ile loglar\u0131 GrayLog<\/em> \u00fczerinde tutabilmemiz i\u00e7in yapmam\u0131z gereken tek bir \u015fey kald\u0131. Log tutabilme i\u015flemi i\u00e7in GrayLog<\/em>‘un, “GELF<\/em>” gibi bir \u00e7ok input’u destekledi\u011finden s\u00f6z etmi\u015ftik. GELF<\/em> input’unu kullanabilmek i\u00e7in GrayLog<\/em> UI’\u0131 \u00fczerinden, “System \/ Inputs<\/strong> > Inputs<\/strong>” men\u00fcs\u00fcne girelim.<\/p>\n GrayLog<\/em> kurulumuna ba\u015flamadan \u00f6nce “aspnetcore-graylog-sample-with-nlog<\/em>” isminde bir folder olu\u015fturmu\u015ftuk. Command tool’u ile tekrardan ayn\u0131 folder i\u00e7erisine gelerek, a\u015fa\u011f\u0131daki gibi bir ASP.NET Core MVC<\/em> projesi olu\u015ftural\u0131m.<\/p>\n Olu\u015fturma i\u015fleminin ard\u0131ndan, Visual Studio Code<\/em> a\u00e7\u0131lacakt\u0131r.<\/p>\n Implementasyon i\u015fleminden \u00f6nce projeye NuGet<\/em> server \u00fczerinden “NLog.Web.AspNetCore<\/em>” ve log message’lar\u0131n\u0131 GrayLog2<\/em>‘ye push yapabilmemiz i\u00e7in gerekli olan “NLog.Web.AspNetCore.Targets.Gelf<\/em>” paketini a\u015fa\u011f\u0131daki gibi dahil etmemiz gerekmektedir.<\/p>\n Paketleri projeye dahil ettikten sonra a\u015fa\u011f\u0131daki “nlog.config<\/em>” dosyas\u0131n\u0131 projenin root klas\u00f6r\u00fc alt\u0131na koyal\u0131m.<\/p>\n Burada iki adet target’a sahibiz. Birincisi file’a log atabilmek i\u00e7in, di\u011feri ise Gelf UDP<\/em> \u00fczerinden message’lar\u0131 GrayLog2<\/em> \u00fczerinde saklayabilmek i\u00e7in. \u00d6rne\u011fimiz gere\u011fi sadece error message’lar\u0131n\u0131 log’layaca\u011f\u0131z.<\/p>\n \u015eimdi “Startup.cs<\/em>” i\u00e7erisine girelim ve a\u015fa\u011f\u0131daki gibi NLog\u00a0<\/em>i\u00e7in,\u00a0bir ka\u00e7 sat\u0131r kod ekleyelim.<\/p>\n Yukar\u0131daki kod blo\u011funda, NLog<\/em>‘u\u00a0bir logger olarak kullanaca\u011f\u0131m\u0131z\u0131 belirledik. Hemen ard\u0131ndan ise\u00a0“nlog.config<\/em>” file’\u0131n\u0131n relative path’ini set ettik. T\u00fcm i\u015flemler bu kadar.<\/p>\n “HomeController<\/em>” i\u00e7erisine girelim ve a\u015fa\u011f\u0131daki gibi bir log atal\u0131m.<\/p>\n “ILogger<\/em>” interface’i constructor \u00fczerinden, otomatik olarak ilgili type’da inject olacakt\u0131r. Buradaki index action’a bakarsak e\u011fer, action execute olaca\u011f\u0131 zaman “Something happened.<\/em>” \u015feklinde bir error message’\u0131 log’lad\u0131k.<\/p>\n \u015eimdi projeyi, terminal \u00fczerinden “dotnet run<\/em>” komutu ile \u00e7al\u0131\u015ft\u0131ral\u0131m. Projenin \u00e7al\u0131\u015ft\u0131r\u0131lmas\u0131ndan sonra “http:\/\/localhost:5000<\/em>” URL’i \u00fczerinden projeye eri\u015fim sa\u011flayal\u0131m. Buradaki index action’\u0131 execute edilecektir ve ard\u0131ndan “C:\\@Logs<\/em>” path’i alt\u0131nda a\u015fa\u011f\u0131daki gibi bir log message’\u0131 tutulacakt\u0131r.<\/p>\n GrayLog <\/em>UI \u00fczerinden ise “System \/ Inputs<\/strong> > Inputs<\/strong> > Show received messages<\/strong>” path’ini izlersek, GrayLog<\/em> \u00fczerine gelen message’\u0131 da a\u015fa\u011f\u0131daki gibi g\u00f6rebiliriz.<\/p>\n ASP.NET Core \u00fczerinde NLog<\/em> ve NLog’un GELF<\/em> target’\u0131n\u0131 (.NET Core i\u00e7in benim transforme etti\u011fim) kullanarak, GrayLog2<\/em> \u00fczerine log atabilme i\u015flemini ger\u00e7ekle\u015ftirdik. Bu makale i\u00e7erisindeki as\u0131l odak noktam\u0131z da buydu. Bunlar\u0131n yan\u0131nda merkezi bir log y\u00f6netim sisteminin de, enterprise seviyedeki projeler i\u00e7in ne denli \u00f6nemli oldu\u011funu tekrardan hat\u0131rlatmak istedim.<\/p>\n Gelecek .NET Core makalelerinde g\u00f6r\u00fc\u015fmek \u00fczere.<\/p>\n https:\/\/github.com\/GokGokalp\/aspnetcore-graylog-sample-with-nlog\/tree\/master<\/a><\/em> https:\/\/github.com\/Graylog2\/graylog-docker Selam millet. ASP.NET Core ile ilgili olan bu 2. serimizde,\u00a0NLog\u00a0library’sini kullanarak uygulama i\u00e7erisinde tutmak istedi\u011fimiz \u00e7e\u015fitli log message’lar\u0131n\u0131,\u00a0GrayLog \u00fczerinde tutabilme i\u015flemini ger\u00e7ekle\u015ftirece\u011fiz. Eminim belki bir \u00e7o\u011fumuz geleneksel .NET Framework \u00fczerinde geli\u015ftirdi\u011fimiz uygulamalarda,\u00a0NLog library’si ile “NLog.Targets.Gelf” paketini kullanarak, log’lama i\u015flemlerini GrayLog \u00fczerinde ger\u00e7ekle\u015ftirmi\u015fizdir. Bir \u00f6nceki seri…<\/p>\n![\"\"](\"\/wp-content\/uploads\/2017\/06\/asp-net-core-nlog-graylog.jpg\")
<\/a><\/p>\nPeki Neden Merkezi Bir Log Sistemine Sahip Olmal\u0131y\u0131z?<\/h5>\n
<\/a><\/p>\nNeden GrayLog?<\/h5>\n
\n
Docker \u00dczerinde GrayLog Kurulumu<\/h5>\n
version: '2'\r\nservices:\r\n some-mongo:\r\n image: \"mongo:3\"\r\n some-elasticsearch:\r\n image: \"elasticsearch:2\"\r\n command: \"elasticsearch -Des.cluster.name='graylog'\"\r\n graylog:\r\n image: graylog2\/server:2.1.1-1\r\n environment:\r\n GRAYLOG_PASSWORD_SECRET: somepasswordpepper\r\n GRAYLOG_ROOT_PASSWORD_SHA2: 8c6976e5b5410415bde908bd4dee15dfb167a9c873fc4bb8a81f6f2ab448a918\r\n GRAYLOG_WEB_ENDPOINT_URI: http:\/\/192.168.99.100:9000\/api\r\n links:\r\n - some-mongo:mongo\r\n - some-elasticsearch:elasticsearch\r\n ports:\r\n - \"9000:9000\"\r\n - \"12201:12201\/udp\"\r\n - \"1514:1514\/udp\"<\/pre>\n
docker-compose up<\/pre>\n
<\/a><\/p>\n<\/a><\/p>\n<\/a>Buradan ise “Select input<\/strong>” drop down men\u00fcs\u00fcnden, “GELF UDP<\/em>” se\u00e7ene\u011fini se\u00e7erek “Launch new input<\/strong>” butonuna t\u0131klayal\u0131m. Kar\u015f\u0131m\u0131za \u00e7\u0131kacak olan ekrandan ise, “Title<\/strong>” b\u00f6l\u00fcm\u00fcne herhangi bir isim vererek doldurmam\u0131z yeterli olacakt\u0131r. Art\u0131k “GELF UDP<\/em>“, “12201<\/strong>” numaral\u0131 port alt\u0131ndan dinlemeye ba\u015flayacakt\u0131r.<\/p>\nASP.NET Core NLog Implementasyonu<\/h5>\n
dotnet new mvc<\/pre>\n
<\/a><\/p>\n<\/a><\/p>\n<nlog xmlns=\"http:\/\/www.nlog-project.org\/schemas\/NLog.xsd\"\r\n xmlns:xsi=\"http:\/\/www.w3.org\/2001\/XMLSchema-instance\"\r\n autoReload=\"true\"\r\n throwExceptions=\"false\"\r\n internalLogLevel=\"Off\"\r\n internalLogFile=\"c:\\temp\\internal-nlog.txt\">\r\n <extensions>\r\n <add assembly=\"NLog.Web.AspNetCore\"\/>\r\n <add assembly=\"NLog.Web.AspNetCore.Targets.Gelf\"\/>\r\n <\/extensions>\r\n <targets>\r\n <target xsi:type=\"File\" name=\"errorFile\" filename=\"C:\\@Logs\\${shortdate}-${level}-AspNetCoreTest.txt\" layout=\"${longdate}|${level:upperCase=true}|${logger}|${aspnet-Request-Method}|url: ${aspnet-Request-Url}${aspnet-Request-QueryString}|${message}\" concurrentWrites=\"false\" \/>\r\n <target xsi:type=\"Gelf\" name=\"graylog\" endpoint=\"udp:\/\/192.168.99.100:12201\" facility=\"console-runner\" SendLastFormatParameter=\"true\" \/>\r\n <\/targets>\r\n <rules>\r\n <logger name=\"*\" minlevel=\"Error\" writeTo=\"errorFile, graylog\" \/>\r\n <\/rules>\r\n<\/nlog><\/pre>\n\/\/ This method gets called by the runtime. Use this method to configure the HTTP request pipeline.\r\npublic void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)\r\n{\r\n loggerFactory.AddNLog();\r\n app.AddNLogWeb();\r\n\r\n env.ConfigureNLog(\"nlog.config\");\r\n\r\n if (env.IsDevelopment())\r\n {\r\n app.UseDeveloperExceptionPage();\r\n app.UseBrowserLink();\r\n }\r\n else\r\n {\r\n app.UseExceptionHandler(\"\/Home\/Error\");\r\n }\r\n\r\n app.UseStaticFiles();\r\n\r\n app.UseMvc(routes =>\r\n {\r\n routes.MapRoute(\r\n name: \"default\",\r\n template: \"{controller=Home}\/{action=Index}\/{id?}\");\r\n });\r\n}<\/pre>\nusing System;\r\nusing System.Collections.Generic;\r\nusing System.Linq;\r\nusing System.Threading.Tasks;\r\nusing Microsoft.AspNetCore.Mvc;\r\nusing Microsoft.Extensions.Logging;\r\n\r\nnamespace aspnetcore_graylog_sample_with_nlog.Controllers\r\n{\r\n public class HomeController : Controller\r\n {\r\n private ILogger _logger;\r\n\r\n public HomeController(ILogger logger)\r\n {\r\n _logger = logger;\r\n }\r\n \r\n public IActionResult Index()\r\n {\r\n _logger.LogError(\"Something happened.\");\r\n\r\n return View();\r\n }\r\n }\r\n}<\/pre>\n<\/a><\/p>\n<\/a><\/p>\nSonu\u00e7<\/h5>\n
\nhttps:\/\/github.com\/GokGokalp\/NLog.Web.AspNetCore.Targets.Gelf<\/a><\/em><\/p>\nBaz\u0131 Referanslar<\/h6>\n
\nhttps:\/\/docs.microsoft.com\/en-us\/aspnet\/core\/fundamentals\/logging<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"