Frédéric MOHIER

I will try to find some time to do it ... 2015-04-14 9:32 GMT+02:00 Radu Gheorghe [email protected]: > Hello and thanks for your feedback! > > Would you be able...

Please note that this is a rela problem to me because I am using intensively registry collected information for more than 3k computers that report inventory only twice a day...

Thanks @tabad A great workaround !

IMHO, the best task order would be: 1. Deploy 1. Collect 1. Inventory 1. WakeOnLan 1. NetDiscovery 1. NetInventory 1. ESX Deploy first and then collect host information before inventorying...

Thanks @g-bougard The main point for the collected information is that the rules engine is only running when an inventory is managed by the server. As such, the information are...

No. I simply explain what I discussed with @ddurieux . The information collected by the collect task are inserted into the computer information tab but ... if you define some...

Collect and Inventory are two separate features ... you can collect information from files or Windows registry that are not related at all to your computer Inventory. IMHO, Collect and...

I agree with you @ortagh for Deployment to take place before Inventory. Indeed, Collect should also take place before Inventory because of the current server behavior: the collected information rules...

After some time (around 15 minutes), the problem is back ... My (simplified) source code: ``` $adapter = new Prometheus\Storage\APCng(); self::$registry = new CollectorRegistry($adapter); ... / ... $counter = self::$registry->getOrRegisterCounter('cron',...

To get rid of this problem I had to downgrade the package version to 2.6.2 ! The problem did not existed in my application before the upgrade to the most...