A web-based monitoring and metrics tool for Elixir applications, providing system insights and a Prometheus-compatible endpoint.
Wobserver is a web-based monitoring and observer tool for Elixir applications that provides real-time insights into system performance, processes, and metrics. It solves the problem of gaining visibility into Erlang VM and application health without complex setup, offering a drop-in web interface and API for monitoring.
Elixir developers and DevOps engineers who need to monitor and observe their Elixir applications in production or development environments, especially those using distributed systems.
Developers choose Wobserver for its ease of integration, extensibility, and comprehensive monitoring capabilities, including Prometheus metrics support and remote node discovery, all within a lightweight Elixir package.
Web based metrics, monitoring, and observer
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Wobserver runs in standalone mode with minimal configuration, offering immediate web-based access to system metrics, processes, and applications without complex setup.
It allows adding custom pages and metrics via configuration or runtime registration, enabling tailored monitoring for specific libraries or applications, as shown in the Library Integration section.
The /metrics endpoint outputs data in Prometheus format by default, facilitating seamless integration with monitoring stacks like Grafana for long-term metric storage and visualization.
With node discovery features, including DNS and custom functions, it can monitor remote Erlang nodes, making it suitable for overseeing distributed Elixir systems behind firewalls.
The README explicitly lists 'Overhaul web interface' as an improvement needed, indicating the UI is basic and may require customization for a modern, polished look.
Setting up plug mode involves additional routing and socket configuration in Phoenix or Cowboy applications, which can be error-prone and adds setup overhead compared to standalone mode.
The project doesn't support direct inclusion from GitHub due to missing built assets, forcing developers to build manually or rely on Hex packages, adding extra steps for some workflows.