Avamar MCCLI Monitoring Help

Thanks @Amr Abdelrahman we have all this in place as well. But yeah I will probably reach out to support for additional help.

That looks good. At this point I think It’d be best to continue troubleshooting within a support case so an engineer can take a look on the actual resource on your portal and run further tests on Avamar modules to help identifying what could be the issue

Sounds good, one additional step to check is making sure that the collector user has access on the avamar directory. This can either be done on the server itself or via collector debug by using !dir followed by the path
For example 
!dir /usr/local/avamar 
If the issue was missing permissions, running the above command would have a permission denied error.
The following article has steps to access collector debug console for reference https://www.logicmonitor.com/support/collectors/collector-troubleshooting/using-the-collector-debug-facility

Oh thanks. when checking it looks like I do. 

So are the property and data sources in LM using the logicmonitor user or the avamar user to run their scripts?