I am writing to discuss the approval of the system-files interface for usage on the alertsync snap. Ideally, the two plugs below would be auto-connected, as they are required for the software’s interaction with Nagios and other compatible software. I suspect I will have to amend these paths to support other monitoring systems such as Icinga, etc, but for now, the below paths are enough.
Is this currently the preferred method for accessing (rw) a UNIX domain socket on the host system?
Alternatively, livestatus could be reconfigured to use TCP, and this snap could use the network binding, however that would be less secure than the current configuration of using a local domain socket, as livestatus connections are only needed locally.
read so there is no need for both a
write version of this interface.
However I am not sure this would even work in practice since
/var/ inside the snap is not the real
/var from the host - instead I think you would have to access this path via
hostfs - ie.
/var/lib/snapd/hostfs/var/lib/nagios3/livestatus - and so this should be modified to:
Thanks for reviewing this and your suggestion. I’ve pushed an updated snap which is building on my CI system right now.
+1 from me for write access to
/var/lib/snapd/hostfs/var/lib/nagios3/livestatus as above. Can other @reviewers please vote?
+1 from me for write access to that location.
+1 from me as well for write access to
3 votes for, 0 against for write access to
/var/lib/snapd/hostfs/var/lib/nagios3/livestatus using the nagios3-livestatus reference. This is now live.