Hi,

I am running xo from sources on the latest commit and have noticed that the configuration from older versions for transport-nagios NSCA backup reports no longer sends data to my check_mk server.
I've seen in patch notes that there was an update and improvement to the way reports are sent but I am having trouble adjusting the configuration.
So the server, port and key stays the same, but host and service should be adjusted. The old configuration was like this:

host: xo hostname as defined on nagios
service: service name as defined on nagios

I have tried to add {vm.name_label} to host and {job.name} to service as the description in GUI suggests but the monitoring server isn't getting any reports. Can anyone provide additional info on how this should be setup ?

Thanks

The update to latest commit seems to have fixed the issue. I have been checking the situation for the last two days and I have the correct number of backups on NAS.
Thank you @olivierlambert for your help.
Cheers.

@olivierlambert Thank you for your response. I have checked and the commit revision is 422a2.
I have now updated to ab110. I'll test again and report back.

Hi,

I am trying to figure out the delta backup retention. For example, here is the setup for 4 day retention:

When I check the NAS strorage though, I find more vhd-s then 4 days (example for one of the VM-s):

It would go on for more days, but the storage got full and it didn't do the backup last night.
Either the retention isn't working as intended or my understanding is not right and I configured something wrong
This was done on xo-server 5.86.3 xo-web 5.91.2 (installed from ronivay install script).
If you got any idea about what is going on, please let me know.
Thanks!

@wuchererbe Found any success ? I am facing similar issues mentioned here (XO from sources).