Validate Data Flowing to OpsBridge Agent

If you are not seeing metrics, events and topology data in Micro Focus OpsBridge Manager, then use the following guide.

Step-by-step guide

Metrics

To validate metrics are coming into the agent, run the command ‘ovcodautil showds’ on the OBM Rest endpoint server

  1. On the Agent that has the StreamWeaver Web Service Listener policy deployed, run the following
    ovcodautil showds
  2. The list of Data Sources will appear.  If you see one that has the name of the Source, then you have confirmed that the agent received metric data from the StreamWeaver Platform

To see the latest value for all of the metrics collected of that data source

  1. On the Agent that has the StreamWeaver Web Service Listener policy deployed, run the following
    ovcodautil -dumpds [Data Source]

Topology

To validate topology is coming into the agent, check the delta detection XML Files (if enabled in OBM Policy)

  1. On the Agent that has the StreamWeaver Web Service Listener policy deployed, go to the topo directory and review the folders there.  (Linux Path example: /var/opt/OV/datafiles/topo)

  2. There should be some directories there with names that correspond to UUIDs of OBM Policies.  

  3. Each should contain 3 files 'delta.xml','payload.xml','repository.xml' 
  4. payload is the data from StreamWeaver 
    repository is the current content of OBM RTSM
    delta is the differences that will be uploaded
  5. if you find these files then you can check the content to confirm that the data looks correct.
  6. Once these have been created once, they will only be adjusted if the topology changes and then only with the differences.
  7. If you want you can delete these files and then rerun StreamWeaver, they should get created again.
Example of Delta.xml content
<?xml version='1.0' encoding='UTF-8' standalone='yes'?>
<Service
   bsmc_origin_policyId="83ac15f9-2a53-9cee-2a19-12a3c16fca66"
   origin_node="opscx.streamweaver.com"
   origin_policyId="83ac15f9-2a53-9cee-2a19-12a3c16fca66"
   origin_type="BSMC">
 <NewInstance
     ref="dynatracemanaged_Application:APPLICATION-EA7C4B59F27D43EB">
   <Std>DiscoveredElement</Std>
   <Virtual/>
   <Key>dynatracemanaged_Application:APPLICATION-EA7C4B59F27D43EB</Key>
   <Attributes>
     <Attribute
         name="hpom_citype"
         value="business_application"/>
     <Attribute
         name="ucmdb_data_externalid"
         value="APPLICATION-EA7C4B59F27D43EB"/>
     <Attribute
         name="ucmdb_monitored_by"
         value="dynatracemanaged"
         datatype="string_list"/>
     <Attribute
         name="ucmdb_name"
         value="APPLICATION-EA7C4B59F27D43EB"/>
     <Attribute
         name="ucmdb_user_label"
         value="easyTravel Web"/>
   </Attributes>
 </NewInstance>
 <NewInstance
     ref="dynatracemanaged_Host:HOST-2E509E89884F934B">
   <Std>DiscoveredElement</Std>
   <Virtual/>
   <Key>dynatracemanaged_Host:HOST-2E509E89884F934B</Key>
   <Attributes>
     <Attribute
         name="hpom_citype"
         value="host_node"/>
     <Attribute
         name="ucmdb_monitored_by"
        datatype="string_list"/>
     <Attribute
         name="ucmdb_name"
         value="HOST-2E509E89884F934B"/>
     <Attribute
         name="ucmdb_user_label"
         value="easytravel-backend"/>
   </Attributes>
 </NewInstance>
 <NewInstance
     ref="dynatracemanaged_Host:HOST-C5FCC2782CBE8F12">
   <Std>DiscoveredElement</Std>
   <Virtual/>
   <Key>dynatracemanaged_Host:HOST-C5FCC2782CBE8F12</Key>
   <Attributes>
     <Attribute
         name="hpom_citype"
         value="host_node"/>
     <Attribute
         name="ucmdb_monitored_by"
         value="dynatracemanaged"
         datatype="string_list"/>
     <Attribute
         name="ucmdb_name"
         value="HOST-C5FCC2782CBE8F12"/>
     <Attribute
         name="ucmdb_user_label"
         value="easytravel-frontend"/>
   </Attributes>
 </NewInstance>



Turn on Debug for Topology on 2020.10 +

  1. cd  /opt/HP/BSM/ucmdb/conf/log
  2. In the following yaml files
    log4j2_root_all.yaml
    log4j2_root.yaml
  3. Change ERROR to DEBUG
    - name: “reconciliation.loglevel
    value: “ERROR”

Look for Reconciliation errors

  1. cd /opt/HP/BSM/ucmdb/runtime/log
  2. vi error.log

Events

To validate events are coming into the agent, check the agent queue for event text

  1. On the Agent that has the StreamWeaver Web Service Listener policy deployed, go to the agent queue directory and search for strings related to your example events.  (Linux Path example: /var/opt/OV/tmp/OpC/msgagtq)
  2. Run the following command and review the strings that are human readable for indicators of the source tool's example events.
    cat msgagtq
  3. On busy systems, you may need to add a search filter with a keyword via grep as follows
    cat msgagtq | grep -i "CPU Utilization"

You may also want to use visual panels to communicate related information, tips or things users need to be aware of.

Related articles

Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.



 

  • 23.1.02
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*