Nostr relay with gRPC, HTTP/JSON, and WebSocket interfaces https://code.northwest.io/muxstr.git/atom?h=main 2026-02-16T01:13:46+00:00 2026-02-16T01:13:46+00:00 bndw ben@bdw.to 2026-02-16T01:13:46+00:00 urn:sha1:e7c37e80f0ebd0894df45cf2e9f4f29e16a781d7 Makes it clear this metric tracks events rejected by kind filtering, not general blocking 2026-02-15T18:39:05+00:00 bndw ben@bdw.to 2026-02-15T18:39:05+00:00 urn:sha1:84dc5995f28e6d63d3cbb1af44daba7f10cbca66 - Added getMetricByLabels() helper for multi-label metric queries - Split 'Authorized' metric into: - Auth Writes: requests_total{method=EVENT, status=authorized} - Auth Reads: requests_total{method=REQ, status=authorized} - Provides clearer visibility into authenticated read vs write operations 2026-02-15T18:31:06+00:00 bndw ben@bdw.to 2026-02-15T18:31:06+00:00 urn:sha1:f658ef072394ff9fd28244ad475859c210e8ec16 Add 'authorized' status for requests that complete successfully after authentication. This complements the existing 'unauthenticated' (pre-auth) status tracking. Now the dashboard shows: - Authorized: Authenticated requests that succeeded - Unauthorized: Authenticated requests rejected (not in allowlist) - Pre-Auth: Requests sent before authentication This gives full visibility into the auth flow: 1. Challenges: How many clients authenticated 2. Authorized: How many authenticated requests succeeded 3. Unauthorized: How many were rejected despite valid auth 4. Pre-Auth: How many tried before authenticating Updated metrics: - requests_total{status="authorized"} - authenticated successes - requests_total{status="ok"} - unauthenticated successes (when no auth) 2026-02-15T18:23:33+00:00 bndw ben@bdw.to 2026-02-15T18:23:33+00:00 urn:sha1:a6ee0e3f268f9a847bf8a19159cf291021a0f38e Updated metrics dashboard to show: - Unauthorized: Requests rejected due to pubkey not in allowlist - Pre-Auth: Requests sent before authentication completed - Challenges: Successful AUTH challenge completions This surfaces the new 'unauthorized' and 'unauthenticated' request status metrics on the dashboard for easier monitoring of auth issues. 2026-02-15T16:22:03+00:00 bndw ben@bdw.to 2026-02-15T16:22:03+00:00 urn:sha1:71f7a444398275923246e1bc8283938a63a8267a Track and display blocked event counts with per-kind breakdown. - Add events_blocked_total counter with kind label - Add RecordBlockedEvent method to metrics - Display blocked count in dashboard Storage section - Call metric when rejecting non-core protocol kinds Allows monitoring spam patterns and verifying kind filter effectiveness. Raw metrics show breakdown by kind (e.g., kind=20001, kind=30311). 2026-02-14T22:18:55+00:00 bndw ben@bdw.to 2026-02-14T22:18:55+00:00 urn:sha1:dbfc55ed1aec5faefacfcfbd51c4de06b316fa90 2026-02-14T22:14:56+00:00 bndw ben@bdw.to 2026-02-14T22:14:56+00:00 urn:sha1:4a99f5dae75636cffdf88f850c46b9e5aad43e69 Transform metrics dashboard from dark modern theme to classic beige theme matching the index page. Changes: - Background: dark (#0a0a0a) → beige (#f5f0e8) - Font: sans-serif → Courier New (monospace) - Colors: vibrant gradients → simple black/brown - Cards: dark (#1a1a1a) → white with black borders - Layout: max-width 1200px → 960px (matches index) - Typography: modern sizing → classic smaller fonts - Logo: Add muxstr SVG logo matching index page - Dividers: Add horizontal rules for section breaks - Status badge: Green gradient → orange/brown (#c97556) - Removed: Color coding (success/error/warning classes) Result: Clean, classic, brutalist aesthetic consistent with index page. The dashboard now feels like part of the same relay, not a separate app. 2026-02-14T20:53:50+00:00 bndw ben@bdw.to 2026-02-14T20:53:50+00:00 urn:sha1:75fb3a583cf4e8a7ca34bedb3322d309bb170ed4 Track and display storage and performance metrics that were previously showing zeros. Storage metrics: - Add GetStats() method to storage returning event count and DB size - Store database file path for size calculation - Update metrics every 30 seconds via goroutine in main.go - Display event count and DB size (MB) in dashboard Performance metrics: - Calculate average latency from histogram sum/count metrics - Display as milliseconds in dashboard - Formula: (duration_sum / duration_count) * 1000 Missing metrics (deferred): - Connections: requires connection lifecycle tracking (gRPC + WebSocket) - Deletions: count would need API change to ProcessDeletion Dashboard now shows accurate storage stats and request latency! 2026-02-14T20:45:20+00:00 bndw ben@bdw.to 2026-02-14T20:45:20+00:00 urn:sha1:9711b2b177959c0ea8e5119bead16dfd40b12c47 Bug: Dashboard showed zeros because it detected "go" as the prefix instead of "muxstr" when Go runtime metrics appeared first in the metrics list. Fix: Search for the first metric containing "_relay_" to properly detect the namespace (muxstr, nostr-grpc, etc.) instead of using the first metric in the alphabetical list. Before: Object.keys(metrics)[0] → "go_gc_..." → prefix = "go" After: Find metric with "_relay_" → "muxstr_relay_..." → prefix = "muxstr" This fixes the dashboard displaying zeros when metrics data is present. 2026-02-14T20:29:01+00:00 bndw ben@bdw.to 2026-02-14T20:29:01+00:00 urn:sha1:c33395cee66770c4d88a47537c0ed821f6585f62 Two critical fixes for metrics: 1. Fix interceptor chaining - Changed from mixed grpc.UnaryInterceptor/ChainUnaryInterceptor to proper chaining with grpc.ChainUnaryInterceptor - Metrics interceptor now runs first (as intended) - All interceptors properly chained in order: metrics → auth → ratelimit - This fixes metrics not being recorded for any requests 2. Fix dashboard uptime calculation - Changed from page load time to process_start_time_seconds metric - Uptime now persists correctly across page refreshes - Uses Prometheus standard process_start_time_seconds gauge Before: Metrics showed 0 for all requests, uptime reset on refresh After: Metrics properly record all gRPC requests, uptime shows actual relay uptime