All Event processing logs can be found at below path. This have event spy logging information also, if enabled.
<DCF-Install>/Collecting/Collector-Manager/<INSTANCE>(ex:smarts-metrics-collect)/logs/collecting-0-0.log
Note: Latest processing log name will have "-0-0" appended to its name like above.
To enable logging, change the collecting configuration to push metrics/topology data to file connector like below. And after changing the configuration, operator need to restart the service to see the logging info in collecting-0-0.log.
Edit below file as specified:
File : <DCF-Install>/Collecting/Collector-Manager/<INSTANCE>(smarts-metrics-collect)/conf/collecting.xml --- <connector enabled="true" name="File" type="File-Connector" config="conf/file-connector.xml" /> ---
For example : "smarts-metrics-collect" is installed management pack name in the below example:
To check the status of the installed services:
<DCF-Install>/bin/manage-modules.sh service status all …. * Checking collector-manager smarts-metrics-collect'... [ running ] To restart the particular service: <DCF-Install>/bin/manage-modules.sh service restart collector-manager smarts-metrics-collect * Stopping collector-manager smarts-metrics-collect'... [ OK ] * Starting collector-manager smarts-metrics-collect'... [ OK ]
Sample output (JSON) of metrics data in Kafka :
{ "groupName":"group", "discoveryID":null, "jobID":"9999", "type":"Processor", "timestamp":1554098437, "value":0.0, "action":"r", "properties":{ "ismanaged":"true", "source":"INCHARGE-AM-PM", "type":"Processor", "datagrp":"SMARTS-PM-METRICS" }, "metrics":{ "CurrentUtilization":{ "properties":{ "name":"CurrentUtilization", "unit":"%" }, "value":10.0 } }, "relations":[ ], "forceRefresh":true, "initialized":true, "name":"PSR-w1-hs4-i2108.eng.vmware.com/30" }
Sample output (JSON) of topo data in Kafka :
{ "groupName":"group", "discoveryID":null, "jobID":"9999", "type":"Processor", "timestamp":1554098437, "value":0.0, "action":"r", "properties":{ "ismanaged":"true", "source":"INCHARGE-AM-PM", "type":"Processor", "datagrp":"SMARTS-PM-TOPO" }, "metrics":{ "id":{ "properties":{ "name":"id", "unit":"integer" }, "value":30.0 } }, "relations":[ { "type":"ProcessorGroup", "element":"PSRGROUP-w1-hs4-i2108.eng.vmware.com/0", "relationName":"PartOf" }, { "type":"Host", "element":"w1-hs4-i2108.eng.vmware.com", "relationName":"PartOf" } ], "forceRefresh":true, "initialized":true, "name":"PSR-w1-hs4-i2108.eng.vmware.com/30" }
Sample debugging (File Connector) output from collecting-0-0.log:
INFO -- [2019-04-01 02:59:58 EDT] -- CollectorManagerImpl::configure(): Parsing file '/opt/DCF/Collecting/Collector-Manager/Default/conf/collecting.xml' ... INFO -- [2019-04-01 02:59:59 EDT] -- CollectorManagerImpl::getComponentInstance(): Instantiating class com.watch4net.apg.v2.collector.plugins.FileConnector for connector File... INFO -- [2019-04-01 02:59:59 EDT] -- CollectorManagerImpl::getComponentInstance(): Configuring connector File (FileConnector v1.0 rM) with /opt/DCF/Collecting/Collector-Manager/Default/conf/file-connector.xml... INFO -- [2019-04-01 02:59:59 EDT] -- CollectorManagerImpl::configureConnectors(): Skipping disabled connector Kafka. INFO -- [2019-04-01 02:59:59 EDT] -- CollectorManagerImpl::getComponentInstance(): Instantiating class com.watch4net.apg.v2.collector.plugins.SmCollector for collector smarts-INCHARGE-AM-PM-0-metrics... INFO -- [2019-04-01 02:59:59 EDT] -- CollectorManagerImpl::getComponentInstance(): Configuring collector smarts-INCHARGE-AM-PM-0-metrics (SmCollector v5.9u2 rM) with /opt/DCF/Collecting/Smarts-Collector/Default/conf/smarts-INCHARGE-AM-PM-0-metrics.xml... INFO -- [2019-04-01 02:59:59 EDT] -- CollectorManagerImpl::getComponentInstance(): Instantiating class com.watch4net.apg.v2.collector.plugins.SmCollector for collector smarts-INCHARGE-AM-PM-0-topo...