What's the recommended way to allow incoming nrpe traffic to 5666/TCP on the Liquidfiles server? I see Liquidfiles uses firewalld. I'd like to properly (w/in the context of Liquidfiles) add the nrpe daemon for monitoring via Nagios. What is the best way to do this so that I don't interfere w/how Liquidfiles is managed? I could issue the command: firewall-cmd --permanent --zone=public --add-rich-rule='rule family="ipv4" source address="x.x.x.x/32" port protocol="tcp" port="5666" accept' This would generally add the following stanza to /etc/firewalld/zones/public.xml (where x.x.x.x is my Nagios server IP): <rule family="ipv4"> <source address="x.x.x.x/32"/> <port protocol="tcp" port="5666"/> <accept/> </rule> But I wasn't sure given the way Liquidfiles sets up firewalld (and I notice it additionally uses tcp-wrappers, for example, for sshd.) I'd like to monitor simple stuff like disk usage. But I'd also like to monitor license usage, which in another forum thread/posting said the only way to do that was with "ft status". If a lot of these monitoring options are now available via an API call, please let me know. I skimmed the API docs for Liquidfiles, but didn't see one that reports this type of stuff. Alternatively, I suppose I could use send_nsca (from the nsca-client rpm) and crontab a job that locally checks stuff and executes send_nsca to inform my Nagios server as a passive check. If you're monitoring your Liquidfiles server with Nagios (or any other monitoring software) and have any recommendations, would love to hear.