Little background story: we have a processing service that sometimes will hang (network connectivity pb). This cause the IS trigger to ‘wait’ and not consume any other document (until a restart)
One workaround was to increase the number of threads so even if one ‘hangs’ the others will keep processing documents.
This is of course not a final solution.
But in the meantime we want to be able to identify the problem. One easy way to monitor our triggers with the Broker was to check the number of documents in the queue.
But I cannot find a way to monitor UM to know the number of documents not consumed (we know they are pilling up somewhere, because when we restart the trigger, they all get processed).
Any advice on how we can do that ? can do it by physically monitoring UM’s files ?
any advice will help,