Browse free open source Elixir Terminals and projects below. Use the toggles on the left to filter open source Elixir Terminals by OS, license, language, programming language, and project status.

  • Paessler: Easy to Use With Enterprise Power. Free Trial Icon
    Paessler: Easy to Use With Enterprise Power. Free Trial

    A low-code dashboard makes monitoring intuitive for any admin, while scripting and custom sensors give experts full control.

    You shouldn't have to choose between a monitoring tool that's easy to use and one that's powerful enough for a complex environment. PRTG's low-code interface lets any admin build dashboards, set alerts and monitor devices without scripting, while custom sensors and full API access are there when your team needs deeper control. One platform, no compromise. Download a free 30-day trial now.
    Get Free Download
  • Endpoint Management with Remote Control Built In Icon
    Endpoint Management with Remote Control Built In

    Patch, monitor, and connect to Windows and macOS devices from one console

    Splashtop AEM handles patching, alerts, scripts, and inventory, and unattended remote control is included. When something needs hands-on work, you’re one click away instead of switching tools.
    Start Free Trial
  • 1
    observer_cli

    observer_cli

    Visualize Erlang/Elixir Nodes On The Command Line

    Observer CLI is a library to be dropped into any beam nodes, to be used to assist DevOps people to diagnose problems in production nodes. Provide a high-performance tool usable both in development and production settings. Focus on important and detailed information about real-time running systems. Keep minimal consumption. Increments are values that are mostly useful when compared to a previous one to have an idea of what they're doing because otherwise, they'd never stop increasing: bytes in and out of the node, number of garbage collector runs, words of memory that were garbage collected, and the global reductions count for the node. Total scheduler utilization will equal 1.0 when all schedulers have been active all the time between the two refresh intervals. The result being that there is a decent chunk of CPU usage that would be mostly free for scheduling actual Erlang work (assuming the schedulers are busy waiting more than trying to select tasks to run).
    Downloads: 0 This Week
    Last Update:
    See Project
  • Previous
  • You're on page 1
  • Next