[{"data":1,"prerenderedAt":456},["ShallowReactive",2],{"site-header":3,"site-footer-license":37,"article-log-aggregation-modern-grafana-loki-vector-hemat-storage-with-latest":41},{"navigations":4},[5,20],{"collection":6,"item":7},"series",{"__typename":6,"title":8,"slug":9,"children_series":10},"Artikel","all",[11,14,17],{"title":12,"slug":13},"Algoritma dan Struktur Data","algoritma-struktur-data",{"title":15,"slug":16},"Konsep Dasar Pemrograman","konsep-dasar-pemrograman",{"title":18,"slug":19},"Kecerdasan Artifisial","kecerdasan-artifisial",{"collection":6,"item":21},{"__typename":6,"title":22,"slug":23,"children_series":24},"Tutorial","tutorial",[25,28,31,34],{"title":26,"slug":27},"Belajar Java","belajar-java",{"title":29,"slug":30},"Belajar Pascal","belajar-pascal",{"title":32,"slug":33},"Belajar Python","belajar-python",{"title":35,"slug":36},"Belajar Golang","belajar-golang",{"name":38,"url":39,"show":40},"CC BY-SA","https://creativecommons.org/licenses/by-sa/4.0/",false,{"article":42,"renderedBody":414,"renderedTakeaway":415,"latestArticles":416,"toc":439},{"id":43,"title":44,"slug":45,"excerpt":46,"published_at":47,"thumbnail_image":48,"tags":50,"reading_time":59,"takeway":60,"body":61,"authors":62,"series":69},"41","Log Aggregation Modern dengan Grafana Loki dan Vector: Hemat Storage Tanpa Indeks Raksasa","log-aggregation-modern-grafana-loki-vector-hemat-storage","Klaster Elasticsearch kalian rakus RAM dan boros storage, ya? Padahal nggak semua kata di log perlu diindeks, lho. Yuk, kita kenalan sama duet Grafana Loki dan Vector yang jauh lebih ramah kantong!","2026-09-01T15:45:01.066Z",{"id":49},"03c9d1a0-c80a-401d-9f2b-2b3ee7abb115",[51,52,53,54,55,56,57,58],"backend","observa","logging","grafana","loki","vector","devops","system-design",5,"- Log aggregation modern bergeser dari full-text indexing (Elasticsearch) ke label-based indexing (Grafana Loki), dan itu jauh lebih hemat RAM serta storage.\n- Vector jadi log shipper berkinerja tinggi berbasis Rust, sanggup mentransformasi, memfilter data sensitif (PII), lalu neruskan log dengan efisien.\n- LogQL dasar ngasih kita cara nyaring stream log berdasarkan label, plus parsing regex on-the-fly langsung di dashboard Grafana.\n- Arsitektur zero-cost log storage menyimpan chunk log terkompresi langsung di object storage kayak S3 atau MinIO.","Buat kalian yang pernah ngurus klaster [Elasticsearch](https://www.elastic.co/) atau ELK Stack, pasti akrab satu keluhan klasik. Rakus RAM dan boros *storage*. 😅\n\nElasticsearch itu teknologi *full-text search* yang hebat banget, sih. Tapi begitu kita jadiin dia tempat nampung jutaan baris *log* tiap hari, dia bikin *inverted index* di hampir setiap kata. Akibatnya ukuran *index*-nya sering membengkak. Bahkan lebih besar dari file log mentahnya sendiri!\n\nDi era *microservices* dan *container Kubernetes*, log dihasilkan dalam volume masif dan cepat. Apa kita beneran butuh ngeindeks setiap kata acak di log? 🤔\n\nJawabannya: **nggak selalu**. Di sinilah kombinasi [Grafana Loki](https://grafana.com/oss/loki/) dan [Vector](https://vector.dev/) hadir. Dua *tool* modern yang **efisien dan ramah kantong**.\n\n## Paradigma Loki: Seperti Prometheus, Tapi Buat Log\n\nFilosofi di balik Loki sederhana banget. Cuma indeks metadata (*label*), bukan isi teks log-nya.\n\nAlih-alih membedah seluruh kalimat log jadi *token* pencarian, Loki cuma ngeindeks *label stream*. Misalnya `app=\"payment-service\"`, `environment=\"production\"`, `level=\"error\"`. Isi teks log aslinya dikompresi dalam bentuk *chunks*. Lalu disimpan di *object storage* murah kayak Amazon S3, Google Cloud Storage, atau MinIO lokal.\n\nPendekatan ini bawa sejumlah keuntungan besar:\n\n- *Footprint* memori sangat rendah. Loki nggak memelihara inverted index raksasa di RAM. Kebutuhan *resource* server-nya jauh lebih kecil dari Elasticsearch.\n- Biaya storage murah. Log tersimpan sebagai *chunk* terkompresi *gzip*/*snappy*. *Retensi* berbulan-bulan pun nggak bikin tagihan cloud membengkak.\n- Integrasi mulus dengan Grafana. Kita bisa pindah dari grafik metrik Prometheus ke log terkait cuma dengan satu klik. Semua di *dashboard* yang sama.\n\n## Kenapa Pilih Vector sebagai Log Shipper?\n\nDulu ekosistem Grafana ngandelin Promtail buat ngirim log ke Loki. Tapi di arsitektur *production* modern, banyak tim beralih ke Vector dari Datadog.\n\nVector adalah *log collector* dan *pipeline processor* *open source*. Ditulis pakai bahasa *Rust*. Keunggulan utamanya kayak gini:\n\n1. Kecepatan dan efisiensi ekstrem. *Throughput*-nya tinggi, konsumsi CPU dan RAM minimal. Semua berkat keamanan memori Rust.\n2. Transformasi data tanpa beban. Ada bahasa ekspresi bawaan namanya *Vector Remap Language* (VRL). Fungsinya buat memparsing JSON dan ngehapus *field* sensitif. Misalnya token JWT atau nomor kartu kredit.\n3. Konektor serba bisa. Vector bisa ngambil log dari Docker, Kubernetes, *syslog*, file lokal, atau Kafka. Lalu ngirimnya paralel ke Loki, S3, atau ClickHouse.\n\n## Alur Vector ke Grafana Loki\n\nProses log-nya jalan dalam tiga tahap berurutan.\n\nPertama, *ingestion* di Vector. Vector bertindak sebagai *DaemonSet* di Kubernetes atau agen di tiap VM. Dia baca stdout/stderr *container* dan memparsing format JSON. Setelah itu dia nyematkan label kayak nama *pod*, *namespace*, dan *service*.\n\nKedua, storage dan *chunking* di Loki. Loki nerima *batch log* dari Vector dan ngelompokin pesan ke dalam *stream* berdasarkan label. Baru deh ditulis ke object storage secara periodik.\n\nKetiga, *querying* pakai *LogQL* di Grafana. *Developer* ngueri log pakai LogQL, bahasa kueri mirip *PromQL*. Kueri mula-mula nyaring stream berdasarkan label. Ini super cepat. Setelah itu baru memfilter isi teks log pakai *regex* secara paralel.\n\n## Contoh Konfigurasi Pipeline Sederhana\n\nBerikut contoh konfigurasi *pipeline* `vector.yaml`. Isinya buat baca *log container Docker* dan memparsing format JSON. Sekalian memfilter data sensitif, lalu ngirimnya ke Loki:\n\n```yaml\nsources:\n  docker_logs:\n    type: docker_logs\n\ntransforms:\n  parse_and_sanitize:\n    type: remap\n    inputs:\n      - docker_logs\n    source: |\n      # Parsing isi pesan log sebagai JSON jika memungkinkan\n      parsed, err = parse_json(.message)\n      if err == null {\n        . = merge(., parsed)\n      }\n\n      # Masking data sensitif seperti password atau token\n      if exists(.password) {\n        .password = \"[REDACTED]\"\n      }\n      if exists(.authorization) {\n        .authorization = \"[REDACTED]\"\n      }\n\nsinks:\n  loki_sink:\n    type: loki\n    inputs:\n      - parse_and_sanitize\n    endpoint: \"http://loki:3100\"\n    encoding:\n      codec: json\n    labels:\n      app: \"{{ container_name }}\"\n      env: \"production\"\n```\n\nSetelah log masuk ke Loki, kita bisa langsung menjelajahinya di Grafana. Pakai ekspresi LogQL berikut:\n\n```logql\n{app=\"payment-service\", env=\"production\"} |= \"error\" | json | latency > 500ms\n```\n\nKueri di atas bakal nyaring *stream log* dari service `payment-service` di production. Dia nyari baris yang mengandung kata `\"error\"`. Lalu memparsing field JSON secara *on-the-fly*. Hasilnya cuma *request* dengan latensi lebih dari 500 ms.\n\n## Kapan Pindah, Kapan Tetap di ELK?\n\nHmm, pindah dari full-text search ke Loki dan Vector bukan berarti observabilitas kita berkurang, kok. **Justru sebaliknya**. Kita dapat efisiensi biaya, kemudahan operasional, dan korelasi data yang lebih solid. Apalagi bareng metrik dan *tracing*.\n\nKalau *server* kalian mulai sering kehabisan memori cuma gara-gara *log aggregator*, cobain aja duet Loki dan Vector di proyek berikutnya.\n\nSelamat ber-*log aggregation* ria, dan semoga tagihan cloud kalian tetap ramah kantong! 👋",[63],{"authors_id":64},{"name":65,"slug":66,"role":67,"profile_picture":68},"Inva","inva","Writer",null,{"id":70,"title":8,"slug":9,"articles":71,"parent_series":68},"9",[72,75,88,100,111,124,136,147,159,170,181,191,201,212,221,232,243,253,261,272,283,294,302,311,320,333,342,353,364,374,383,392,402],{"id":43,"title":44,"slug":45,"excerpt":46,"thumbnail_image":73,"tags":74},{"id":49},[51,52,53,54,55,56,57,58],{"id":76,"title":77,"slug":78,"excerpt":79,"thumbnail_image":80,"tags":82},"45","Rate Limiting Algorithms: Token Bucket vs Leaky Bucket vs Sliding Window","rate-limiting-algorithms-token-bucket-leaky-bucket-sliding-window","Udah tahu kenapa *rate limiting* itu wajib, tapi masih bingung beda Token Bucket, Leaky Bucket, Fixed Window, dan Sliding Window? Yuk, kita adu empat algoritma ini bareng-bareng dan cari tahu mana yang paling pas buat API kalian!",{"id":81},"0e0ed26d-20c6-443c-bde1-4a6200f6f801",[51,58,83,84,85,86,87],"rate-limiting","redis","api-gateway","architecture","traffict-management",{"id":89,"title":90,"slug":91,"excerpt":92,"thumbnail_image":93,"tags":95},"16","Menggunakan TypeScript dengan Node.js dan Express","menggunakan-typescript-dengan-node-js-dan-express","Pengen bikin server Express di Node.js tapi pakai fitur-fitur keren TypeScript? Yuk, intip cara setup lengkapnya dari nol di sini!",{"id":94},"798b60f1-9ef5-4f73-8d43-85825fd86acc",[96,97,98,99],"javascript","nodejs","express","typescript",{"id":101,"title":102,"slug":103,"excerpt":104,"thumbnail_image":105,"tags":107},"17","Pemrograman Asynchronous vs Multithreading, Apa Sih Bedanya?","pemrograman-asynchronous-dan-multithreading-apa-bedanya","Sering dengar istilah asynchronous dan multithreading pas ngoding tapi masih bingung bedanya? Yuk, kita bedah perbedaannya lewat analogi bikin mi instan yang gampang dipahami!",{"id":106},"9c05d0ae-e829-4f1b-b9f7-a84f3e0439d3",[108,109,110],"pemrograman","concurrency","tips-coding",{"id":112,"title":113,"slug":114,"excerpt":115,"thumbnail_image":116,"tags":118},"33","Berkenalan dengan RabbitMQ: Si Kurir Pesan Serba Bisa","berkenalan-dengan-rabbitmq-si-kurir-pesan-serba-bisa","Pernah nggak sih kalian klik Bayar Sekarang dan notifikasi suksesnya muncul seketika, padahal email konfirmasi baru nyampe beberapa detik kemudian? Rahasianya ada di satu kurir tak terlihat. Yuk, kita kenalan sama RabbitMQ!",{"id":117},"f6620f79-b3b2-4f9c-8104-283a335e06c4",[119,120,51,121,122,123],"rabbitmq","message-broker","microservices","async","queue",{"id":125,"title":126,"slug":127,"excerpt":128,"thumbnail_image":129,"tags":131},"34","Kenapa Backend Butuh Database Connection Pooling?","kenapa-backend-butuh-database-connection-pooling","Pernah kena error Too many connections padahal CPU server masih santai di angka 30%? Masalahnya bukan di query kalian, tapi di cara aplikasi ngobrol sama database. Yuk, kenalan sama Connection Pooling!",{"id":130},"6f7a2d8c-2a37-4901-a522-50df8d9c0a20",[51,132,133,134,58,135],"database","postgresql","connection-pooling","performance",{"id":137,"title":138,"slug":139,"excerpt":140,"thumbnail_image":141,"tags":143},"27","Background Worker & Task Queue: Jangan Jalankan Proses Berat di Request HTTP!","background-worker-task-queue-jangan-jalankan-proses-berat-di-http","Pernah nggak sih kalian klik Daftar Akun lalu halaman loading muter sampai 15 detik tanpa kepastian? Penyebabnya klasik banget. Yuk, kita bahas kenapa proses berat nggak boleh dijalanin di request HTTP!",{"id":142},"e119c6ad-fc37-4b92-abdc-3eb20f8e34b4",[51,144,145,146,119,84,122],"task-queue","celery","fastapi",{"id":148,"title":149,"slug":150,"excerpt":151,"thumbnail_image":152,"tags":154},"28","Mengatasi N+1 Query Problem: Musuh Tersembunyi Performa Backend","mengatasi-n-plus-1-query-problem-musuh-tersembunyi-backend","Pernah bikin endpoint yang cuma nampilin 50 postingan beserta nama penulisnya, tapi response-nya lambat banget? Bisa jadi kalian kena N+1 Query. Yuk, kita bedah penyebabnya dan cara memberantasnya!",{"id":153},"34b94e14-3e9a-4778-9f1f-6df5898915fb",[132,155,156,157,158,135,51],"sql","orm","sqlalchemy","django",{"id":160,"title":161,"slug":162,"excerpt":163,"thumbnail_image":164,"tags":166},"30","Berkenalan dengan Bahasa Go: Kenapa Banyak Dipakai untuk Backend Modern?","berkenalan-dengan-bahasa-go-untuk-backend-modern","Kok bisa sih Go yang masih muda ini jadi bahasa andalan Docker sampai Kubernetes? Yuk, kita kenalan sama Goroutine, Channel, dan alasan dia hemat memori luar biasa!",{"id":165},"a368631c-f331-4c50-8322-1d0fc44927aa",[167,168,51,109,169,58],"golang","go","goroutine",{"id":171,"title":172,"slug":173,"excerpt":174,"thumbnail_image":175,"tags":177},"13","Hal yang Perlu Diperhatikan Sebelum Pindah ke Linux","hal-yang-perlu-diperhatikan-sebelum-pindah-ke-linux","Tertarik migrasi dari Windows ke Linux tapi masih ragu? Yuk, pelajari kelebihan, kekurangan, dan persiapan penting sebelum kamu benar-benar pindah!",{"id":176},"ae27713e-5025-4d13-88b6-efb4860cc5b3",[178,179,180],"linux","windows","foss",{"id":182,"title":183,"slug":184,"excerpt":185,"thumbnail_image":186,"tags":188},"11","Apa Kabar JavaScript? Rilis State of JS 2022","apa-kabar-javascript-rilis-state-of-js-2022","Survei State of JS 2022 resmi dirilis dengan lonjakan responden yang luar biasa! Framework dan build tool apa saja yang berhasil mencuri perhatian tahun ini?",{"id":187},"18df5262-d813-43d1-b1f7-5595a7f53602",[96,189,190],"web","news",{"id":192,"title":193,"slug":194,"excerpt":195,"thumbnail_image":196,"tags":198},"12","Buat PowerShell Lebih Berwarna dengan Starship","buat-powershell-lebih-berwarna-dengan-starship","Bosen sama tampilan PowerShell yang hitam putih dan kaku? Yuk, sulap terminalmu jadi lebih interaktif, estetik, dan berwarna pakai Starship!",{"id":197},"c5a8262b-43db-4479-8f6c-5a6a0d61653b",[199,179,200],"shell","powershell",{"id":202,"title":203,"slug":204,"excerpt":205,"thumbnail_image":206,"tags":208},"14","Instalasi Java dengan Visual Studio Code","instalasi-java-dengan-visual-studio-code","Mau belajar ngoding Java tapi spek laptop pas-pasan buat buka IDE berat? Yuk, cari tahu cara setup VS Code biar ngoding Java tetap lancar dan enteng!",{"id":207},"99b01cc2-11ac-4449-9927-a1a7116347df",[209,210,211],"howto","java","editor",{"id":213,"title":214,"slug":215,"excerpt":216,"thumbnail_image":217,"tags":219},"15","Kenapa Ada Banyak Sekali Distro Linux?","kenapa-ada-banyak-sekali-distro-linux","Pernah bingung pas mau install Linux tapi malah disuguhi puluhan pilihan distro? Tenang, kalian nggak sendirian. Yuk, cari tahu kenapa distro Linux bisa sebanyak itu dan apa bedanya!",{"id":218},"b5352a4b-f274-4489-aca9-36814947d514",[178,220],"distro",{"id":222,"title":223,"slug":224,"excerpt":225,"thumbnail_image":226,"tags":228},"18","React, Angular, atau Vue: Pilih Framework yang Mana?","react-angular-vue-pilih-framework-yang-mana","Bingung menentukan pilihan di antara React, Angular, dan Vue untuk proyek web kalian berikutnya? Tenang, yuk kita bandingkan kelebihan masing-masing di sini!",{"id":227},"ff111270-80c2-4ccb-83d7-d5ab8c021201",[229,230,231],"web-development","frontend","framework",{"id":233,"title":234,"slug":235,"excerpt":236,"thumbnail_image":237,"tags":239},"19","Static Typing dan Dynamic Typing: Apa Bedanya?","static-typing-dan-dynamic-typing-apa-bedanya","Pernah bingung kenapa di Java tipe data harus dideklarasikan, sementara di Python tinggal pakai aja? Yuk, cari tahu perbedaan static typing dan dynamic typing di sini!",{"id":238},"98e85e76-9e7b-42d1-b989-7c75e7f49abc",[240,241,242],"programming","types","comparison",{"id":244,"title":245,"slug":246,"excerpt":247,"thumbnail_image":248,"tags":250},"20","Tailwind v3.0 Rilis: Ada JIT, Arbitrary Values, dan Banyak Lagi!","tailwind-v3-0-rilis-jit-arbitrary-dan-banyak-lagi","Tailwind CSS v3.0 resmi dirilis dengan segudang peningkatan performa yang bikin proses coding makin asyik. Apa aja sih fitur andalan yang wajib dicoba?",{"id":249},"d5e879fa-5cd0-4015-a155-b0cc69ff12fb",[251,252,229],"tailwind-css","css-framework",{"id":254,"title":255,"slug":256,"excerpt":257,"thumbnail_image":258,"tags":260},"21","TypeScript: JavaScript dengan Gaya dan Tipe Data Statis","typescript-javascript-dengan-gaya","Pernah pusing gara-gara runtime error di JavaScript? Yuk, kenalan dengan TypeScript yang bawa fitur static typing biar kode kalian makin rapi dan aman!",{"id":259},"f615bb1f-8e36-4d6c-9c2c-f1629407173c",[99,96,229],{"id":262,"title":263,"slug":264,"excerpt":265,"thumbnail_image":266,"tags":268},"22","Yang Baru di Nuxt 3: Nitro Engine, Vite, dan Fitur Keren Lainnya","yang-baru-di-nuxt-3-nitro-vite-dan-banyak-lagi","Nuxt 3 hadir membawa perubahan arsitektur besar-besaran untuk menyelaraskan dengan Vue 3. Penasaran apa saja peningkatan performa dan fitur barunya?",{"id":267},"8444bdbc-f60c-4d8b-8593-1b49400e8659",[269,270,271],"nuxt-3","vue-3","frontend-framework",{"id":273,"title":274,"slug":275,"excerpt":276,"thumbnail_image":277,"tags":279},"23","Kenapa Pakai FastAPI dan Kenapa Dia Kenceng Banget?","kenapa-pakai-fastapi-dan-kenapa-dia-kenceng-banget","Sering dengar FastAPI tapi masih bingung kenapa dia bisa ngebut kayak NodeJS dan Go? Yuk, kita bedah bareng rahasia ASGI, sihir Pydantic, sampai dokumentasi otomatisnya!",{"id":278},"84847c9e-70ab-4dcc-bed7-7be50165f7f4",[146,280,51,281,282],"python","asgi","pydantic",{"id":284,"title":285,"slug":286,"excerpt":287,"thumbnail_image":288,"tags":290},"26","REST API vs gRPC: Kapan Sebaiknya Mulai Pindah dari JSON?","rest-api-vs-grpc-kapan-sebaiknya-pindah-dari-json","Pernah nggak sih sistem mikroservis kalian mulai kerasa berat padahal cuma tuker-tukeran data internal? Belum tentu masalah servernya. Yuk, kita bahas kapan REST + JSON masih juara dan kapan gRPC jadi jawabannya!",{"id":289},"487500a0-9e09-469d-8736-1583c5ea83aa",[51,291,292,121,293,58],"grpc","rest-api","protobuf",{"id":295,"title":296,"slug":297,"excerpt":298,"thumbnail_image":299,"tags":301},"38","Optimistic vs Pessimistic Locking: Mengatasi Rebutan Data di Database","optimistic-vs-pessimistic-locking-mengatasi-rebutan-data-di-database","Seribu orang ngeklik \"Beli Sekarang\" di detik yang sama buat rebutan 1 tiket terakhir. Kira-kira apa yang bakal terjadi di server kalian? Yuk, kita banding *pessimistic* sama *optimistic locking*!",{"id":300},"21ab769d-6f82-4a22-be11-17ac16e9fb6b",[51,132,109,133,58,86,155],{"id":303,"title":304,"slug":305,"excerpt":306,"thumbnail_image":307,"tags":309},"24","Kenapa Butuh Rate Limiting?","kenapa-butuh-rate-limiting","Pernah nggak sih endpoint login kalian diserbu bot yang nyoba nembak ribuan password cuma dalam semenit? Yuk, kita bahas kenapa Rate Limiting itu wajib, plus cara masangnya di FastAPI!",{"id":308},"1401f9e5-6359-404a-8d80-273ddee9a372",[51,83,58,310,84,146],"api",{"id":312,"title":313,"slug":314,"excerpt":315,"thumbnail_image":316,"tags":318},"25","Kenapa Event Queue Bikin Backend Kalian Nggak Gampang Tumbang?","kenapa-event-queue-bikin-backend-kamu-nggak-gampang-tumbang","Pernah klik tombol Beli Sekarang dan notifikasi suksesnya muncul dalam sekejap, padahal di belakang layar ada invoice, email, sampai push notification yang harus dibuat? Rahasianya Event Queue. Yuk, kita bedah!",{"id":317},"d9e76018-fbcc-4c69-ad42-8f75ff229ecd",[51,58,319,120,86],"event-queue",{"id":321,"title":322,"slug":323,"excerpt":324,"thumbnail_image":325,"tags":327},"46","Mengapa C Mulai Ditinggalkan: Duel Filosofi Keamanan Rust vs Kesederhanaan Zig","mengapa-c-mulai-ditinggalkan-duel-filosofi-rust-vs-zig","Pernah denger kalau sekitar 70% celah keamanan kritis software modern itu asalnya dari bahasa C? Iya, bahasa yang udah jadi fondasi internet ini 😅. Yuk, kita bedah duel filosofi Rust vs Zig dan cari tahu mana yang pas buat proyek kalian!",{"id":326},"1942a5c9-c1f6-476d-9913-768f78d9d8eb",[328,329,330,331,332],"system-programming","rust","zig","c","memory-safety",{"id":334,"title":335,"slug":336,"excerpt":337,"thumbnail_image":338,"tags":340},"29","Memahami Database Indexing: Rahasia Query Super Cepat","memahami-database-indexing-rahasia-query-super-cepat","Query kalian mulai lelet padahal data baru nembus jutaan baris? Sebelum buru-buru *upgrade* server, yuk cek dulu *index*-nya. Yuk, kita bedah gimana *database indexing* sebenernya kerja!",{"id":339},"b123036f-1779-478c-a545-cf5f189b5fe9",[132,155,133,341,135,51],"indexing",{"id":343,"title":344,"slug":345,"excerpt":346,"thumbnail_image":347,"tags":349},"31","Mengenal Redis: Lebih dari Sekadar In-Memory Cache","mengenal-redis-lebih-dari-sekadar-in-memory-cache","Masih nganggep Redis cuma buat caching? Padahal dia bisa jadi leaderboard, message broker, sampai rate limiter lho. Yuk, kita bedah semua kemampuannya!",{"id":348},"9595b7d7-60e0-48f5-a715-f3cf60f34e1d",[84,51,350,351,352,280],"cache","nosql","in-memory",{"id":354,"title":355,"slug":356,"excerpt":357,"thumbnail_image":358,"tags":360},"32","Docker Compose untuk Developer Santai: Satu Perintah Buat Jalankan Semua Service","docker-compose-untuk-developer-santai","Pernah nggak kalian ngulang-ngulang perintah `docker run` cuma buat nyalain web, database, dan cache satu-satu? Capek, kan? Yuk, kita rapikan semuanya jadi satu file dan satu perintah!",{"id":359},"f4c08f1b-e0d0-410c-b091-c3618944fb3e",[361,362,57,363,51],"docker","docker-compose","containers",{"id":365,"title":366,"slug":367,"excerpt":368,"thumbnail_image":369,"tags":371},"35","Mengenal Idempotency Key: Rahasia Anti-Double Charge di API Pembayaran","mengenal-idempotency-key-rahasia-anti-double-charge-di-api-pembayaran","Pernah internet kalian ngadat pas lagi nekan tombol Bayar, terus panik ngekliknya tiga kali? Kalau endpoint-nya nggak idempotent, saldo bisa kepotong berkali-kali. Yuk, kenalan sama Idempotency Key!",{"id":370},"724cb83a-3ce5-4ee2-b0d7-533e3a0fc7df",[51,310,372,58,373,146,84],"idempotency","payment",{"id":375,"title":376,"slug":377,"excerpt":378,"thumbnail_image":379,"tags":381},"36","Mencegah Efek Domino di Mikroservis dengan Circuit Breaker Pattern","mencegah-efek-domino-di-mikroservis-dengan-circuit-breaker-pattern","Pernah nggak sih, satu fitur minor di aplikasi kalian mendadak lelet, eh malah bikin halaman checkout dan login ikut down total? Itu namanya *cascading failure*. Yuk, kita bahas gimana *circuit breaker pattern* (pemutus arus) nyelametin arsitektur kalian!",{"id":380},"c2e8e37f-8f9a-423f-a09d-74613b3c2924",[51,121,382,58,86],"circuit-breaker",{"id":384,"title":385,"slug":386,"excerpt":387,"thumbnail_image":388,"tags":390},"37","Kenapa Backend Butuh Graceful Shutdown? Jangan Asal Cabut Kabel Server!","kenapa-backend-butuh-graceful-shutdown-jangan-asal-cabut-kabel-server","Pernah nggak sih, abis kalian nge-*deploy* backend, beberapa detik kemudian monitoring malah banjir *alert* **502 Bad Gateway** dari pengguna? Saldo udah kepotong tapi status order belum keburu ter-*update* di *database*. Yuk, kita bahas kenapa *graceful shutdown* itu wajib banget!",{"id":389},"251a54a7-1d24-47fd-8cbc-a46fd42cbb6f",[51,57,146,361,391,58,86],"kubernetes",{"id":393,"title":394,"slug":395,"excerpt":396,"thumbnail_image":397,"tags":399},"39","Database Sharding vs Partitioning: Kapan Data Perlu Dipecah?","database-sharding-vs-partitioning-kapan-data-perlu-dipecah","Tabel transaksi kalian udah nembus miliaran baris dan tiap *query* laporan bikin *CPU* melonjak 100%? Sebelum asal pecah data, yuk kita pahami dulu beda *sharding* sama *partitioning*!",{"id":398},"08ef5fe5-d935-47b3-bbbc-d976948b2a9e",[51,132,133,58,86,400,401],"sharding","scaling",{"id":403,"title":404,"slug":405,"excerpt":406,"thumbnail_image":407,"tags":409},"40","Menyelami Distributed Tracing: Melacak Jejak Request di Balik Keruwetan Microservices","menyelami-distributed-tracing-melacak-jejak-request-microservices","Satu klik Checkout di backend kalian bisa memicu puluhan network call antar-service, tapi pas ada yang lambat, service mana sebenernya yang salah? Log aja nggak cukup buat njawab itu. Yuk, kita bedah Distributed Tracing!",{"id":408},"1ace92fa-b89c-4cef-ab75-4e4cd67a089c",[51,410,411,412,121,86,413],"distributed-systems","observability","open-telemetry","tracing","\u003Cp>Buat kalian yang pernah ngurus klaster \u003Ca href=\"https://www.elastic.co/\">Elasticsearch\u003C/a> atau ELK Stack, pasti akrab satu keluhan klasik. Rakus RAM dan boros \u003Cem>storage\u003C/em>. 😅\u003C/p>\n\u003Cp>Elasticsearch itu teknologi \u003Cem>full-text search\u003C/em> yang hebat banget, sih. Tapi begitu kita jadiin dia tempat nampung jutaan baris \u003Cem>log\u003C/em> tiap hari, dia bikin \u003Cem>inverted index\u003C/em> di hampir setiap kata. Akibatnya ukuran \u003Cem>index\u003C/em>-nya sering membengkak. Bahkan lebih besar dari file log mentahnya sendiri!\u003C/p>\n\u003Cp>Di era \u003Cem>microservices\u003C/em> dan \u003Cem>container Kubernetes\u003C/em>, log dihasilkan dalam volume masif dan cepat. Apa kita beneran butuh ngeindeks setiap kata acak di log? 🤔\u003C/p>\n\u003Cp>Jawabannya: \u003Cstrong>nggak selalu\u003C/strong>. Di sinilah kombinasi \u003Ca href=\"https://grafana.com/oss/loki/\">Grafana Loki\u003C/a> dan \u003Ca href=\"https://vector.dev/\">Vector\u003C/a> hadir. Dua \u003Cem>tool\u003C/em> modern yang \u003Cstrong>efisien dan ramah kantong\u003C/strong>.\u003C/p>\n\u003Ch2 id=\"paradigma-loki-seperti-prometheus-tapi-buat-log\">Paradigma Loki: Seperti Prometheus, Tapi Buat Log\u003C/h2>\n\u003Cp>Filosofi di balik Loki sederhana banget. Cuma indeks metadata (\u003Cem>label\u003C/em>), bukan isi teks log-nya.\u003C/p>\n\u003Cp>Alih-alih membedah seluruh kalimat log jadi \u003Cem>token\u003C/em> pencarian, Loki cuma ngeindeks \u003Cem>label stream\u003C/em>. Misalnya \u003Ccode>app="payment-service"\u003C/code>, \u003Ccode>environment="production"\u003C/code>, \u003Ccode>level="error"\u003C/code>. Isi teks log aslinya dikompresi dalam bentuk \u003Cem>chunks\u003C/em>. Lalu disimpan di \u003Cem>object storage\u003C/em> murah kayak Amazon S3, Google Cloud Storage, atau MinIO lokal.\u003C/p>\n\u003Cp>Pendekatan ini bawa sejumlah keuntungan besar:\u003C/p>\n\u003Cul>\n\u003Cli>\u003Cem>Footprint\u003C/em> memori sangat rendah. Loki nggak memelihara inverted index raksasa di RAM. Kebutuhan \u003Cem>resource\u003C/em> server-nya jauh lebih kecil dari Elasticsearch.\u003C/li>\n\u003Cli>Biaya storage murah. Log tersimpan sebagai \u003Cem>chunk\u003C/em> terkompresi \u003Cem>gzip\u003C/em>/\u003Cem>snappy\u003C/em>. \u003Cem>Retensi\u003C/em> berbulan-bulan pun nggak bikin tagihan cloud membengkak.\u003C/li>\n\u003Cli>Integrasi mulus dengan Grafana. Kita bisa pindah dari grafik metrik Prometheus ke log terkait cuma dengan satu klik. Semua di \u003Cem>dashboard\u003C/em> yang sama.\u003C/li>\n\u003C/ul>\n\u003Ch2 id=\"kenapa-pilih-vector-sebagai-log-shipper\">Kenapa Pilih Vector sebagai Log Shipper?\u003C/h2>\n\u003Cp>Dulu ekosistem Grafana ngandelin Promtail buat ngirim log ke Loki. Tapi di arsitektur \u003Cem>production\u003C/em> modern, banyak tim beralih ke Vector dari Datadog.\u003C/p>\n\u003Cp>Vector adalah \u003Cem>log collector\u003C/em> dan \u003Cem>pipeline processor\u003C/em> \u003Cem>open source\u003C/em>. Ditulis pakai bahasa \u003Cem>Rust\u003C/em>. Keunggulan utamanya kayak gini:\u003C/p>\n\u003Col>\n\u003Cli>Kecepatan dan efisiensi ekstrem. \u003Cem>Throughput\u003C/em>-nya tinggi, konsumsi CPU dan RAM minimal. Semua berkat keamanan memori Rust.\u003C/li>\n\u003Cli>Transformasi data tanpa beban. Ada bahasa ekspresi bawaan namanya \u003Cem>Vector Remap Language\u003C/em> (VRL). Fungsinya buat memparsing JSON dan ngehapus \u003Cem>field\u003C/em> sensitif. Misalnya token JWT atau nomor kartu kredit.\u003C/li>\n\u003Cli>Konektor serba bisa. Vector bisa ngambil log dari Docker, Kubernetes, \u003Cem>syslog\u003C/em>, file lokal, atau Kafka. Lalu ngirimnya paralel ke Loki, S3, atau ClickHouse.\u003C/li>\n\u003C/ol>\n\u003Ch2 id=\"alur-vector-ke-grafana-loki\">Alur Vector ke Grafana Loki\u003C/h2>\n\u003Cp>Proses log-nya jalan dalam tiga tahap berurutan.\u003C/p>\n\u003Cp>Pertama, \u003Cem>ingestion\u003C/em> di Vector. Vector bertindak sebagai \u003Cem>DaemonSet\u003C/em> di Kubernetes atau agen di tiap VM. Dia baca stdout/stderr \u003Cem>container\u003C/em> dan memparsing format JSON. Setelah itu dia nyematkan label kayak nama \u003Cem>pod\u003C/em>, \u003Cem>namespace\u003C/em>, dan \u003Cem>service\u003C/em>.\u003C/p>\n\u003Cp>Kedua, storage dan \u003Cem>chunking\u003C/em> di Loki. Loki nerima \u003Cem>batch log\u003C/em> dari Vector dan ngelompokin pesan ke dalam \u003Cem>stream\u003C/em> berdasarkan label. Baru deh ditulis ke object storage secara periodik.\u003C/p>\n\u003Cp>Ketiga, \u003Cem>querying\u003C/em> pakai \u003Cem>LogQL\u003C/em> di Grafana. \u003Cem>Developer\u003C/em> ngueri log pakai LogQL, bahasa kueri mirip \u003Cem>PromQL\u003C/em>. Kueri mula-mula nyaring stream berdasarkan label. Ini super cepat. Setelah itu baru memfilter isi teks log pakai \u003Cem>regex\u003C/em> secara paralel.\u003C/p>\n\u003Ch2 id=\"contoh-konfigurasi-pipeline-sederhana\">Contoh Konfigurasi Pipeline Sederhana\u003C/h2>\n\u003Cp>Berikut contoh konfigurasi \u003Cem>pipeline\u003C/em> \u003Ccode>vector.yaml\u003C/code>. Isinya buat baca \u003Cem>log container Docker\u003C/em> dan memparsing format JSON. Sekalian memfilter data sensitif, lalu ngirimnya ke Loki:\u003C/p>\n\n\u003Cdiv class=\"code-block-wrapper my-6 not-prose rounded-xl border-2 border-black dark:border-gray-600 shadow-neo overflow-hidden bg-[#24292e] text-[#e1e4e8] transition-all\">\n  \u003Cdiv class=\"code-block-header flex items-center justify-between px-4 py-2.5 bg-[#1f2428] border-b-2 border-black dark:border-gray-600 font-mono text-xs font-bold text-gray-300 select-none\">\n    \u003Cdiv class=\"flex items-center gap-2\">\n      \u003Cspan class=\"w-3 h-3 rounded-full bg-[#ff5f56] border border-black/40 inline-block\">\u003C/span>\n      \u003Cspan class=\"w-3 h-3 rounded-full bg-[#ffbd2e] border border-black/40 inline-block\">\u003C/span>\n      \u003Cspan class=\"w-3 h-3 rounded-full bg-[#27c93f] border border-black/40 inline-block\">\u003C/span>\n      \u003Cspan class=\"ml-2 font-mono font-bold text-xs uppercase tracking-wider text-gray-300\">YAML\u003C/span>\n    \u003C/div>\n    \u003Cbutton type=\"button\" class=\"copy-code-btn flex items-center gap-1.5 px-3 py-1 text-xs font-bold bg-[#2f363d] text-gray-200 border-2 border-black dark:border-gray-500 rounded-lg shadow-neo-sm hover:translate-x-0.5 hover:translate-y-0.5 hover:shadow-none hover:bg-gray-700 transition-all cursor-pointer\" data-code=\"sources%3A%0A%20%20docker_logs%3A%0A%20%20%20%20type%3A%20docker_logs%0A%0Atransforms%3A%0A%20%20parse_and_sanitize%3A%0A%20%20%20%20type%3A%20remap%0A%20%20%20%20inputs%3A%0A%20%20%20%20%20%20-%20docker_logs%0A%20%20%20%20source%3A%20%7C%0A%20%20%20%20%20%20%23%20Parsing%20isi%20pesan%20log%20sebagai%20JSON%20jika%20memungkinkan%0A%20%20%20%20%20%20parsed%2C%20err%20%3D%20parse_json(.message)%0A%20%20%20%20%20%20if%20err%20%3D%3D%20null%20%7B%0A%20%20%20%20%20%20%20%20.%20%3D%20merge(.%2C%20parsed)%0A%20%20%20%20%20%20%7D%0A%0A%20%20%20%20%20%20%23%20Masking%20data%20sensitif%20seperti%20password%20atau%20token%0A%20%20%20%20%20%20if%20exists(.password)%20%7B%0A%20%20%20%20%20%20%20%20.password%20%3D%20%22%5BREDACTED%5D%22%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20if%20exists(.authorization)%20%7B%0A%20%20%20%20%20%20%20%20.authorization%20%3D%20%22%5BREDACTED%5D%22%0A%20%20%20%20%20%20%7D%0A%0Asinks%3A%0A%20%20loki_sink%3A%0A%20%20%20%20type%3A%20loki%0A%20%20%20%20inputs%3A%0A%20%20%20%20%20%20-%20parse_and_sanitize%0A%20%20%20%20endpoint%3A%20%22http%3A%2F%2Floki%3A3100%22%0A%20%20%20%20encoding%3A%0A%20%20%20%20%20%20codec%3A%20json%0A%20%20%20%20labels%3A%0A%20%20%20%20%20%20app%3A%20%22%7B%7B%20container_name%20%7D%7D%22%0A%20%20%20%20%20%20env%3A%20%22production%22\" title=\"Salin kode\">\n      \u003Csvg class=\"w-3.5 h-3.5 copy-icon-svg\" fill=\"none\" stroke=\"currentColor\" viewBox=\"0 0 24 24\">\n        \u003Cpath stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\" d=\"M8 16H6a2 2 0 01-2-2V6a2 2 0 012-2h8a2 2 0 012 2v2m-6 12h8a2 2 0 002-2v-8a2 2 0 00-2-2h-8a2 2 0 00-2 2v8a2 2 0 002 2z\">\u003C/path>\n      \u003C/svg>\n      \u003Cspan class=\"copy-text\">Copy\u003C/span>\n    \u003C/button>\n  \u003C/div>\n  \u003Cdiv class=\"code-block-content p-4 overflow-x-auto text-sm font-mono leading-relaxed bg-[#24292e]\">\n    \u003Cpre class=\"shiki github-dark\" style=\"background-color:#24292e;color:#e1e4e8\" tabindex=\"0\">\u003Ccode>\u003Cspan class=\"line\">\u003Cspan style=\"color:#85E89D\">sources\u003C/span>\u003Cspan style=\"color:#E1E4E8\">:\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#85E89D\">  docker_logs\u003C/span>\u003Cspan style=\"color:#E1E4E8\">:\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#85E89D\">    type\u003C/span>\u003Cspan style=\"color:#E1E4E8\">: \u003C/span>\u003Cspan style=\"color:#9ECBFF\">docker_logs\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#85E89D\">transforms\u003C/span>\u003Cspan style=\"color:#E1E4E8\">:\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#85E89D\">  parse_and_sanitize\u003C/span>\u003Cspan style=\"color:#E1E4E8\">:\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#85E89D\">    type\u003C/span>\u003Cspan style=\"color:#E1E4E8\">: \u003C/span>\u003Cspan style=\"color:#9ECBFF\">remap\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#85E89D\">    inputs\u003C/span>\u003Cspan style=\"color:#E1E4E8\">:\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">      - \u003C/span>\u003Cspan style=\"color:#9ECBFF\">docker_logs\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#85E89D\">    source\u003C/span>\u003Cspan style=\"color:#E1E4E8\">: \u003C/span>\u003Cspan style=\"color:#F97583\">|\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#9ECBFF\">      # Parsing isi pesan log sebagai JSON jika memungkinkan\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#9ECBFF\">      parsed, err = parse_json(.message)\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#9ECBFF\">      if err == null {\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#9ECBFF\">        . = merge(., parsed)\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#9ECBFF\">      }\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#9ECBFF\">      # Masking data sensitif seperti password atau token\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#9ECBFF\">      if exists(.password) {\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#9ECBFF\">        .password = \"[REDACTED]\"\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#9ECBFF\">      }\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#9ECBFF\">      if exists(.authorization) {\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#9ECBFF\">        .authorization = \"[REDACTED]\"\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#9ECBFF\">      }\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#85E89D\">sinks\u003C/span>\u003Cspan style=\"color:#E1E4E8\">:\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#85E89D\">  loki_sink\u003C/span>\u003Cspan style=\"color:#E1E4E8\">:\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#85E89D\">    type\u003C/span>\u003Cspan style=\"color:#E1E4E8\">: \u003C/span>\u003Cspan style=\"color:#9ECBFF\">loki\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#85E89D\">    inputs\u003C/span>\u003Cspan style=\"color:#E1E4E8\">:\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#E1E4E8\">      - \u003C/span>\u003Cspan style=\"color:#9ECBFF\">parse_and_sanitize\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#85E89D\">    endpoint\u003C/span>\u003Cspan style=\"color:#E1E4E8\">: \u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"http://loki:3100\"\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#85E89D\">    encoding\u003C/span>\u003Cspan style=\"color:#E1E4E8\">:\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#85E89D\">      codec\u003C/span>\u003Cspan style=\"color:#E1E4E8\">: \u003C/span>\u003Cspan style=\"color:#9ECBFF\">json\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#85E89D\">    labels\u003C/span>\u003Cspan style=\"color:#E1E4E8\">:\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#85E89D\">      app\u003C/span>\u003Cspan style=\"color:#E1E4E8\">: \u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"{{ container_name }}\"\u003C/span>\u003C/span>\n\u003Cspan class=\"line\">\u003Cspan style=\"color:#85E89D\">      env\u003C/span>\u003Cspan style=\"color:#E1E4E8\">: \u003C/span>\u003Cspan style=\"color:#9ECBFF\">\"production\"\u003C/span>\u003C/span>\u003C/code>\u003C/pre>\n  \u003C/div>\n\u003C/div>\u003Cp>Setelah log masuk ke Loki, kita bisa langsung menjelajahinya di Grafana. Pakai ekspresi LogQL berikut:\u003C/p>\n\n\u003Cdiv class=\"code-block-wrapper my-6 not-prose rounded-xl border-2 border-black dark:border-gray-600 shadow-neo overflow-hidden bg-[#24292e] text-[#e1e4e8] transition-all\">\n  \u003Cdiv class=\"code-block-header flex items-center justify-between px-4 py-2.5 bg-[#1f2428] border-b-2 border-black dark:border-gray-600 font-mono text-xs font-bold text-gray-300 select-none\">\n    \u003Cdiv class=\"flex items-center gap-2\">\n      \u003Cspan class=\"w-3 h-3 rounded-full bg-[#ff5f56] border border-black/40 inline-block\">\u003C/span>\n      \u003Cspan class=\"w-3 h-3 rounded-full bg-[#ffbd2e] border border-black/40 inline-block\">\u003C/span>\n      \u003Cspan class=\"w-3 h-3 rounded-full bg-[#27c93f] border border-black/40 inline-block\">\u003C/span>\n      \u003Cspan class=\"ml-2 font-mono font-bold text-xs uppercase tracking-wider text-gray-300\">LOGQL\u003C/span>\n    \u003C/div>\n    \u003Cbutton type=\"button\" class=\"copy-code-btn flex items-center gap-1.5 px-3 py-1 text-xs font-bold bg-[#2f363d] text-gray-200 border-2 border-black dark:border-gray-500 rounded-lg shadow-neo-sm hover:translate-x-0.5 hover:translate-y-0.5 hover:shadow-none hover:bg-gray-700 transition-all cursor-pointer\" data-code=\"%7Bapp%3D%22payment-service%22%2C%20env%3D%22production%22%7D%20%7C%3D%20%22error%22%20%7C%20json%20%7C%20latency%20%3E%20500ms\" title=\"Salin kode\">\n      \u003Csvg class=\"w-3.5 h-3.5 copy-icon-svg\" fill=\"none\" stroke=\"currentColor\" viewBox=\"0 0 24 24\">\n        \u003Cpath stroke-linecap=\"round\" stroke-linejoin=\"round\" stroke-width=\"2\" d=\"M8 16H6a2 2 0 01-2-2V6a2 2 0 012-2h8a2 2 0 012 2v2m-6 12h8a2 2 0 002-2v-8a2 2 0 00-2-2h-8a2 2 0 00-2 2v8a2 2 0 002 2z\">\u003C/path>\n      \u003C/svg>\n      \u003Cspan class=\"copy-text\">Copy\u003C/span>\n    \u003C/button>\n  \u003C/div>\n  \u003Cdiv class=\"code-block-content p-4 overflow-x-auto text-sm font-mono leading-relaxed bg-[#24292e]\">\n    \u003Cpre class=\"shiki github-dark\" style=\"background-color:#24292e;color:#e1e4e8\">\u003Ccode>{app=\"payment-service\", env=\"production\"} |= \"error\" | json | latency > 500ms\u003C/code>\u003C/pre>\n  \u003C/div>\n\u003C/div>\u003Cp>Kueri di atas bakal nyaring \u003Cem>stream log\u003C/em> dari service \u003Ccode>payment-service\u003C/code> di production. Dia nyari baris yang mengandung kata \u003Ccode>"error"\u003C/code>. Lalu memparsing field JSON secara \u003Cem>on-the-fly\u003C/em>. Hasilnya cuma \u003Cem>request\u003C/em> dengan latensi lebih dari 500 ms.\u003C/p>\n\u003Ch2 id=\"kapan-pindah-kapan-tetap-di-elk\">Kapan Pindah, Kapan Tetap di ELK?\u003C/h2>\n\u003Cp>Hmm, pindah dari full-text search ke Loki dan Vector bukan berarti observabilitas kita berkurang, kok. \u003Cstrong>Justru sebaliknya\u003C/strong>. Kita dapat efisiensi biaya, kemudahan operasional, dan korelasi data yang lebih solid. Apalagi bareng metrik dan \u003Cem>tracing\u003C/em>.\u003C/p>\n\u003Cp>Kalau \u003Cem>server\u003C/em> kalian mulai sering kehabisan memori cuma gara-gara \u003Cem>log aggregator\u003C/em>, cobain aja duet Loki dan Vector di proyek berikutnya.\u003C/p>\n\u003Cp>Selamat ber-\u003Cem>log aggregation\u003C/em> ria, dan semoga tagihan cloud kalian tetap ramah kantong! 👋\u003C/p>\n","\u003Cul>\n\u003Cli>Log aggregation modern bergeser dari full-text indexing (Elasticsearch) ke label-based indexing (Grafana Loki), dan itu jauh lebih hemat RAM serta storage.\u003C/li>\n\u003Cli>Vector jadi log shipper berkinerja tinggi berbasis Rust, sanggup mentransformasi, memfilter data sensitif (PII), lalu neruskan log dengan efisien.\u003C/li>\n\u003Cli>LogQL dasar ngasih kita cara nyaring stream log berdasarkan label, plus parsing regex on-the-fly langsung di dashboard Grafana.\u003C/li>\n\u003Cli>Arsitektur zero-cost log storage menyimpan chunk log terkompresi langsung di object storage kayak S3 atau MinIO.\u003C/li>\n\u003C/ul>\n",[417,420,423,431],{"id":321,"title":322,"slug":323,"excerpt":324,"thumbnail_image":418,"tags":419},{"id":326},[328,329,330,331,332],{"id":76,"title":77,"slug":78,"excerpt":79,"thumbnail_image":421,"tags":422},{"id":81},[51,58,83,84,85,86,87],{"id":424,"title":425,"slug":426,"excerpt":427,"thumbnail_image":428,"tags":430},"44","Transactional Outbox Pattern: Solusi Konsistensi Database dan Message Broker Tanpa 2PC","transactional-outbox-pattern-konsistensi-database-message-broker","Pernah nggak kalian lihat pesanan udah masuk database, tapi email konfirmasinya nggak pernah kekirim? Itu gejala *dual-write problem*. Yuk, kita bedah Transactional Outbox Pattern biar data dan *event* kalian nggak lagi berselisih paham!",{"id":429},"e3c617fd-1486-4b82-b937-94fbec846c77",[51,121,86,132,120,58,133],{"id":432,"title":433,"slug":434,"excerpt":435,"thumbnail_image":436,"tags":438},"43","Dead Letter Queue (DLQ) & Retry Policy: Menyelamatkan Pesan Nyasar di RabbitMQ Tanpa Bikin Worker Macet","dead-letter-queue-retry-policy-rabbitmq-resilient-messaging","Pernah nggak sih, *worker* kalian nolak satu pesan terus-terusan sampai CPU melonjak 100%? Itu namanya *poison message loop*, jebakan klasik di RabbitMQ. Yuk, kita bahas cara pasang *retry policy* dan *dead letter queue* yang bener!",{"id":437},"6c0a7ead-4841-4073-b29e-df7ae0f2aa3c",[119,120,51,86,121,122,280],[440,444,447,450,453],{"text":441,"depth":442,"id":443},"Paradigma Loki: Seperti Prometheus, Tapi Buat Log",2,"paradigma-loki-seperti-prometheus-tapi-buat-log",{"text":445,"depth":442,"id":446},"Kenapa Pilih Vector sebagai Log Shipper?","kenapa-pilih-vector-sebagai-log-shipper",{"text":448,"depth":442,"id":449},"Alur Vector ke Grafana Loki","alur-vector-ke-grafana-loki",{"text":451,"depth":442,"id":452},"Contoh Konfigurasi Pipeline Sederhana","contoh-konfigurasi-pipeline-sederhana",{"text":454,"depth":442,"id":455},"Kapan Pindah, Kapan Tetap di ELK?","kapan-pindah-kapan-tetap-di-elk",1791045071766]