If more information is needed to analyze the information being passed, please use the following steps.

The steps are needed as the login, usage, and troubleshooting of the MTM is required by the Support team.

All MTM versions

A: Set up MTM logging from Clarity

1. Enable Fiddler-tracing to capture MTM traffic to the proxy (Clarity) server.

2. Enable Clarity MTM-component logging 

a. Go to NSA via URL: http://<server>:8090
   click servername > Logs > Edit Configuration

b. For each server, the following components should be set accordingly:

Priority Name                    Appender
WARN com.niku                   STDOUT          
FATAL org.jgroups                STDOUT                     
FATAL org.logicalcobwebs.proxool STDOUT
ERROR com.niku.blobcrack         STDOUT             
ERROR com.niku.njs               STDOUT
INFO  odata.in.json            (add to the "other name" column) STDOUT
INFO  odata.out.json           (add to the "other name" column) STDOUT
INFO  odata.out.xml            (add to the "other name" column) XML
INFO  odata.out                (add to the "other name" column) STDOUT
INFO  odata.metadata.load      (add to the "other name" column) STDOUT
INFO  odata.function.metadata  (add to the "other name" column) STDOUT
INFO  odata.function.runtime   (add to the "other name" column) STDOUT

c. Is there a checkmark on 'Detect Log Configuration Changes Automatically'?

   If checked, the BG service does not have to be restarted.
   If it is not checked, the BG does have to be restarted.

B. Setup Fiddler profile for smartphone running Apple iOS.

C: Recreate the issue in the MTM App.

1. Provide the username performing the MTM test.

2. Verify the MTM information is written to the logs.

3. In a ZIP/RAR file, send the following logs(from all servers):
Clarity_HOME\logs\app-ca.log
Clarity_HOME\logs\app-system.log