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.

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.

Both very interesting ideas indeed.

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

Completely agree.