Collection plans contain configuration and state information which allows collectors to schedule and run host checks and service checks. Additionally, collection plans facilitate executing event handlers and sending notifications.
A collector’s collection plan is stored in encrypted json format in this location:
When you Apply Changes, new collection plans are distributed to each collector.
If you see this file is failing to update after an Apply Changes, check your collector is ONLINE and therefore contactable
If it is, then you may have a build up of messages on your opsview-messagequeue for this collector-queue_<machine.ref>
- Find your Opsview - machine.ref
If you do not have a backlog or need to send an empty collection plan to a collector, then you may do so with the below
- run from your orchestrator
/opt/opsview/orchestrator/venv3/bin/orchestratorgenerate -e <machine.ref>
If you do not supply the "-e machine.ref>" information, empty collection plans will be sent to all collectors, which isn't a problem as you will now be Applying Changes on your system after this to push out populated collection plans.
Opsview - Apply changes