feat(landing): remote server monitoring guide

apps/landing/src/lib/guide-highlight.ts

@@ -20,6 +20,7 @@
     | "python-logging"
     | "loguru-output"
     | "otel-debug"
+    | "sql"
     | "powershell";
 
 const escape = (s: string) => s.replace(/&/g, "&amp;").replace(/</g, "&lt;").replace(/>/g, "&gt;");
@@ -93,7 +94,8 @@
         [/#.*/y, (m) => span("comment", m[0])],
         [/(?<=^|\n)(\s*-?\s*)([\w./-]+)(:)/y, (m) => escape(m[1]) + span("name", m[2]) + escape(m[3])],
         [/"[^"\n]*"/y, (m) => span("labels", m[0])],
-        [/\b\d+[a-z]*\b/y, (m) => span("value", m[0])],
+        [/(?<![\w.-])\d+[a-z]*\b/y, (m) => span("value", m[0])],
+        [/[\w.-]+/y, (m) => escape(m[0])],
     ]);
 
 const python = (code: string) =>
@@ -182,6 +184,20 @@
         [/[a-zA-Z_]\w*/y, (m) => escape(m[0])],
     ]);
 
+// ClickHouse SQL: comments, strings, $__ macros, function calls, column names.
+// Keywords stay plain so the columns and functions stand out.
+const sql = (code: string) =>
+    tokenize(code, [
+        [/--.*/y, (m) => span("comment", m[0])],
+        [/'[^'\n]*'/y, (m) => span("labels", m[0])],
+        [/\$__\w+/y, (m) => span("value", m[0])],
+        [/\b(?:SELECT|FROM|WHERE|AND|OR|NOT|IN|AS|GROUP|BY|ORDER|LIMIT|WITH)\b/y, (m) => escape(m[0])],
+        [/[a-zA-Z_]\w*(?=\()/y, (m) => span("fn", m[0])],
+        [/\b[A-Z][A-Za-z]+\b/y, (m) => span("name", m[0])],
+        [/\b\d+(?:\.\d+)?\b/y, (m) => span("value", m[0])],
+        [/[a-zA-Z_]\w*/y, (m) => escape(m[0])],
+    ]);
+
 // Loguru's default console line: time | LEVEL | location - message. Each level
 // gets its own class (tok-level-info, tok-level-error...); traceback lines pass through.
 const loguruOutput = (code: string) =>
@@ -265,5 +281,6 @@
         "python-logging": pythonLogging,
         "loguru-output": loguruOutput,
         "otel-debug": otelDebug,
+        sql,
         powershell,
     })[lang](code);

apps/landing/src/pages/guides/index.astro

@@ -91,6 +91,13 @@
         description: "Start logging with Loguru, set the level, write files and JSON, add context, then send its logs to OpenTelemetry.",
         read: "7 min",
     },
+    {
+        href: "/guides/remote-server-monitoring",
+        label: "Infrastructure",
+        title: "Remote server monitoring with OpenTelemetry",
+        description: "Agent vs agentless and the ports each needs, a Collector setup with host metrics, logs, HTTP and SSH checks, and alerts for servers that go quiet.",
+        read: "10 min",
+    },
 ];
 
 const investigationGuides = [

apps/landing/src/pages/llms.txt.ts

@@ -122,6 +122,7 @@ export const GET: APIRoute = ({ site }) => {
 		`- [Uptime monitoring with traces and HTTP checks](${url("/guides/uptime-monitoring")})`,
 		`- [Prometheus metrics, explained](${url("/guides/prometheus-metrics")})`,
 		`- [Log parsing: from raw lines to structured fields](${url("/guides/log-parsing")})`,
+		`- [Remote server monitoring with OpenTelemetry](${url("/guides/remote-server-monitoring")})`,
 		`- [What is observability?](${url("/observability")})`,
 		`- [What is OpenTelemetry?](${url("/opentelemetry")})`,
 		`- [Best open-source observability tools](${url("/best-open-source-observability-tools")})`,