From d612c953f4c9efec546df6a9bf2a38be8898a176 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marcel=20St=C3=B6r?= Date: Sat, 3 Jan 2026 23:01:40 +0100 Subject: [PATCH 1/2] Add Wikipedia link to NATS --- monitoring/logs-api-options.html.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/monitoring/logs-api-options.html.md b/monitoring/logs-api-options.html.md index ffd52124c5..755195c516 100644 --- a/monitoring/logs-api-options.html.md +++ b/monitoring/logs-api-options.html.md @@ -8,7 +8,7 @@ date: 2025-10-01 ## Overview -Fly.io apps run on Firecracker microVMs we call Machines. Each Machine captures `stdout`/`stderr`, ships those logs over NATS, and stores them for a period of time in a Quickwit-backed search index. Most users consume logs via `fly logs` or by setting up log shipping to an external sink. +Fly.io apps run on Firecracker microVMs we call Machines. Each Machine captures `stdout`/`stderr`, ships those logs over [NATS](https://en.wikipedia.org/wiki/NATS_Messaging), and stores them for a period of time in a Quickwit-backed search index. Most users consume logs via `fly logs` or by setting up log shipping to an external sink. But sometimes you want to grab logs directly, without a CLI or setting up an exporter, because you’re building a tool, automating something, or you just want to pipe logs into your own system. From a5246143d11a6c31fb01b91ca8c631447e3d651d Mon Sep 17 00:00:00 2001 From: Kristin Martin Date: Fri, 17 Jul 2026 20:18:56 +0000 Subject: [PATCH 2/2] Point NATS link to nats.io and sync line with current wording --- monitoring/logs-api-options.html.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/monitoring/logs-api-options.html.md b/monitoring/logs-api-options.html.md index 755195c516..ca7d24e85a 100644 --- a/monitoring/logs-api-options.html.md +++ b/monitoring/logs-api-options.html.md @@ -8,7 +8,7 @@ date: 2025-10-01 ## Overview -Fly.io apps run on Firecracker microVMs we call Machines. Each Machine captures `stdout`/`stderr`, ships those logs over [NATS](https://en.wikipedia.org/wiki/NATS_Messaging), and stores them for a period of time in a Quickwit-backed search index. Most users consume logs via `fly logs` or by setting up log shipping to an external sink. +Fly.io apps run on Firecracker microVMs we call Machines. Each Machine captures `stdout`/`stderr`, ships those logs over [NATS](https://nats.io+external), and stores them for a period of time in a VictoriaLogs-backed search index. Most users consume logs via `fly logs` or by setting up log shipping to an external sink. But sometimes you want to grab logs directly, without a CLI or setting up an exporter, because you’re building a tool, automating something, or you just want to pipe logs into your own system.