lhask

I have no idea why notifications are hidden away from system logs and don't automatically go to Syslog by default so complete agreement there btw. the notify script should be doing it by default.

A drunken non-AI basic agent: # cat /usr/local/emhttp/plugins/dynamix/agents/Syslog.xml <?xml version="1.0" encoding="utf-8"?> <Agent> <Name>Syslog</Name> <!-- <Variables> </Variables> --> <Script> <![CDATA[ MESSAGE="$EVENT: $SUBJECT - $CONTENT" case "$IMPORTANCE" in 'normal' ) PRIORITY="5" ;; 'warning' ) PRIORITY="4" ;; 'alert' ) PRIORITY="1" ;; esac MESSAGE=$(echo -e "$MESSAGE") logger \ --priority $PRIORITY \ "$MESSAGE" ]]> </Script> </Agent> An intern can implement this in an afternoon but with a proper review and added fields for optional remote server.

The simplest solution in the current setup is an alert agent in Unraid itself. And it only requires calling logger with a single command, and would be a checkmarkable agent in the official WebUI. The code is simple, it's unified, there are no third-party factors or hacks. Just one and done. No monitoring, just an agent that would be called like any other through a simple enabling in the webui. I tested logger with additional arguments that followed notification data but ultimately priority was the only important part that was worth specifying AFAIR. Edit: But it should be in notify by default without requiring an agent.

Other way around - I just want notifications piped to syslog. Found a version of the script but the actual XML agent I created in /usr/local/emhttp/plugins/dynamix/agents is gone. I cannot compare if this is an early draft or not. But t's a very simple agent, would be great to see it implemented by Lime themselves. Only need to map notification importance to syslog priority and format it properly. The XML agent UI can also support remote server but default to localhost. I can recreate it if need be, just gauging interest from Lime themselves since agents rely on favicons in another directory and modifying anything in the UnRaid OS itself is too hacky for my taste in a NAS. MESSAGE="$EVENT: $SUBJECT - $CONTENT" case "$IMPORTANCE" in 'normal' ) PRIORITY="5" ;; 'warning' ) PRIORITY="4" ;; 'alert' ) PRIORITY="1" ;; esac MESSAGE=$(echo -e "$MESSAGE") logger \ --priority $PRIORITY \ "$MESSAGE"

It would be really convenient to have Syslog as an agent for notifications. Both for local logging but also in my case I have a central syslog server in my homelab. I wrote one but lost it after an unplanned shutdown, but the code was very simple. Being able to specify server:port would be ideal but it would default to localhost. Any interest in doing this in-house or should I get back to recreating it and submit it here?