MustGather: Instana Self-Hosted Synthetic PoP

• Kubernetes version
• Helm chart version

  • helm list -n <namespace>

Additional output & files to collect:

• Run the pdcollect.sh script and upload the output to the support case
  • For additional information, please follow the instructions
  • To increase log level to debug (if needed):
    •  If the initial pdcollect.sh output does not provide enough information for analysis, you may be asked to increase the log level, reproduce the issue, and run pdcollect.sh again.  
    • To change the trace level of each component, you can pass the traceLevel values via helm as follows to make an upgrade on your PoP: 

      • --set controller.traceLevel="DEBUG" \
        --set http.traceLevel="DEBUG" \
        --set javascript.traceLevel="DEBUG" \
        --set browserscript.traceLevel="DEBUG" \
        --set ism.traceLevel="DEBUG" \
        --set redis.traceLevel="DEBUG"

    • You can also dynamically change the trace level of PoP controller without restarting the pod by running the set_trace_level.sh command in the container. 
      • Exec into the synthetic-pop-controller pod

        • kubectl exec -it -n <namespace> <pop_controller_pod_name> -- bash 

      • run set_trace_level.sh command to change trace level to DEBUG 

        • ./set_trace_level.sh DEBUG 

• Capture Synthetic Locations page and Synthetic PoP health page screenshots 
  • In addition to collecting logs using pdcollect.sh, capture screenshots of the Synthetic Locations page and the PoP health page
    • Login to Instana UI 
    • Go to Synthetic monitoring 
    • Click on Locations tab 
    • Capture a screenshot 
    • If the Location name is clickable, click on the Location name, capture a screenshot of the PoP health page