manage-modules.sh service start collector-manager <instance>
Error similar to the following seen in Watch4net APG Collector Manager log file (<APG_INSTALL>/Collecting/Collector-Manager/<instance>/logs/collecting-0-0.log) after trying to start the Collector Manager:
$XmlValidationEventHandler::handleEvent(): cvc-id.1: There is no ID/IDREF binding for IDREF 'PropertyTaggingFilter'. File: /opt/APG/Collecting/Collector-Manager/Default/conf/collecting.xml, Line: 38, Col: 10 org.xml.sax.SAXParseException: cvc-id.1: There is no ID/IDREF binding for IDREF 'PropertyTaggingFilter'.
<collector enabled="true" name="APG_HEALTH" next="PropertyTaggingFilter" config="APG-Self-Monitoring-Collector/Default/conf/apg-self-monitoring-collector.xml" />
A valid PropertyTaggingFilter filter entry must exist in the collecting.xml file if it is being called by an APG_HEALTH collector, or the Watch4net APG Collector Manager service will fail to start.
The following sections show how to do each of these options to address this issue.
Creating a valid PropertyTaggingFilter filter entry in the collecting.xml file
The steps to create a valid PropertyTaggingFilter entry in the collecting.xml file are as follows:
Sending the APG_Health collector data directly to the Backend
You can address this issue by having the APG_Health collector send data directly to the Backend, and also avoid the errors seen in the collecting logs. To do this, change the "next" value in "<collector enabled/>" parameter from "next=PropertyTaggingFilter" to "next=Backend" as in the following::
<collector enabled="true" name="APG_HEALTH" next="Backend" config="APG-Self-Monitoring-Collector/Default/conf/apg-self-monitoring-collector.xml" />