6 ms·

Really like it. My only criticisms are: * I'd love to be able to write my own modules for it * When a module's config is bad it just doesn't show -- no

• senorprogrammer 8y ago
  You can write your own modules, you'll just need to fork the repo and write them in Go. There's no DSL for it. Good idea about the config. I'll create a feature issue for it.
  • ben509 8y ago
    Go uses less CPU and is less crashy, both of which are nice in a dashboard. It also seems like more generic modules may handle the use cases you'd want a DSL for. For instance, there's already a text module; if a similar module can listen to a FIFO or even listen on a socket, you can just throw whatever you need into it from any language that can write to a filehandle. If it can handle ANSI escapes, most commands that can write to a terminal would work with it. So `{clear; ls --color=always} > /whatever/fifo` or `> /dev/tcp/whatever/1234` could stick to my dashboard.
    • senorprogrammer 8y ago
      Both very interesting ideas indeed.
• djsumdog 8y ago
  Yea, this type of error message isn't useful unless I know what module it is from: 2018/06/01 08:51:20 invalid api key
  • senorprogrammer 8y ago
    Completely agree.