Wobserver: Easy to Integrate Monitoring and Debugging
summary
: wobserver claims to give observer‑like visibility over nodes you cannot attach to, by shipping a web interface and JSON API formatted for Prometheus and integrating as a drop-in mix dependency with Phoenix. It runs an HTTP/WebSocket layer (default port 4001), discovers multi‑instance setups (demo uses five nodes behind a load balancer), proxies requests to the right node, and aggregates metrics from Docker containers. It works but needs npm/distillery asset steps, has rough security and WebSocket edge cases, and is read‑only.
AI-written summary · about
chapters (35)
- 0:00Introduction
- 0:42What is Wobserver
- 0:59Why use Wobserver
- 1:17Why not use Wobserver
- 1:51Alternatives
- 3:53Wobserver Features
- 4:59Metrics
- 5:35Live Demo
- 9:35Port
- 11:57WebSockets
- 14:00Phoenix
- 16:34The problem
- 16:58The solution
- 17:31DNS
- 18:55Custom Discovery
- 19:25Remote View Notes
- 19:55Should they do that
- 20:21Custom note discovery
- 21:35Remote node information
- 22:00Remote node caller
- 22:23Remote node identifier
- 23:10Process identifier
- 23:26Sending process information
- 23:43Node information
- 24:51Solution
- 25:12Extending
- 26:13Marbles
- 27:09Metric Generator
- 29:24Additional Pages
- 30:28Generating Pages
- 31:48Register
- 32:41Apply
- 33:27Code Structure
- 34:01Reflection
- 36:15QA
related talks
08mGraphQL Observability
32mObservability for Frontend Engineers
53mUnmask hidden issues with Observability superpowers!
52mIs your JVM app flying blind? Unmask hidden issues with Observability superpowers!
28mUnlocking Multi-Cloud Observability: The Case Study of...
17mUnlocking Observability with React & Node.js
56mFull-stack observability and application monitoring with
23mObservability by Design: Leveraging OpenTelemetry Weaver To Take Control of Your Observability