Turning on Trace Logging to Troubleshoot ADA/MTP Synchronization

Document ID : KB000030169
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

This article describes how to turn on trace logging to view the XML feed and other information generated during an ADA/MTP sync.

 

Solution:

This is done by editing the Web.config file on the console in the NetQoS\SuperAgent\dotnet\SuperAgentInternal folder and changing the value for “LogWebServices” to “true”  (by default it is “false”).   The log file generated will be in the NetQoS\logs folder with a name SAWebServiceLog_YYYY-MM-DD.log.   It will give a large amount of details regarding the sync including the contents of the XML feed.

For one MTP simply resync only that MTP by going to the monitor properties/gear icon in the top right, synchronize monitor device.

 

If there are 2 MTPs, it will be easiest to isolate this if only one is asking for the config at a time.  This is what is suggested for this process:

    1/  From the MTP UI, stop nqmetricd on one of the MTPs so it is not trying to start up and get its config.

    2/  Update the Web.config file to trace the web requests.

    3/  From the other MTP web UI, start/restart the nqmetricd process.

 

 The feed in the log will look something like this:

 

<NewDataSet>

  <Table>

    <app_id>1</app_id>

    <master_app_id>0</master_app_id>

  </Table>

  <Table>

    <app_id>2</app_id>

    <master_app_id>0</master_app_id>

  </Table>

  <Table>

    <app_id>3</app_id>

    <master_app_id>0</master_app_id>

  </Table>

  <Table>

    <app_id>5</app_id>

    <master_app_id>0</master_app_id>

  </Table>

  <Table>

    <app_id>6</app_id>

    <master_app_id>0</master_app_id>

  </Table>

  <Table>

    <app_id>8</app_id>

    <master_app_id>0</master_app_id>

  </Table>

  <Table>

    <app_id>9</app_id>

    <master_app_id>0</master_app_id>

  </Table>

  <Table>

    <app_id>10</app_id>

    <master_app_id>0</master_app_id>

  </Table>

  <Table>

    <app_id>11</app_id>

    <master_app_id>0</master_app_id>

  </Table>

  <Table>

    <app_id>12</app_id>

    <master_app_id>0</master_app_id>

  </Table>

  <Table>

    <app_id>13</app_id>

    <master_app_id>0</master_app_id>

  </Table>

  <Table>

    <app_id>14</app_id>

    <master_app_id>0</master_app_id>

  </Table>

  <Table>

    <app_id>15</app_id>

    <master_app_id>0</master_app_id>

  </Table>

  <Table>

    <app_id>16</app_id>

    <master_app_id>0</master_app_id>

  </Table>

  <Table>

    <app_id>17</app_id>

    <master_app_id>0</master_app_id>

  </Table>

  <Table>

    <app_id>18</app_id>

    <master_app_id>0</master_app_id>

 

  </Table>

 

You can copy out the XML formatted section of the feed and save it as an XML document with the appropriate starting and ending tags, then open the feed document you just created in a browser like Firefox to get more information on the XML formatting. This can allow you to tell if there are foreign characters (like from European keyboards) that do not show up in the normal feed but can break the sync, as well as checking for any other formatting or other issues with the XML feed that syncs the monitor configuration down from the ADA console to the MTP.