Support ClientCustomerId in the summary logs

[phamtri]

I am trying to use SOAP Logs with Google AdWords to troubleshoot something.

I am able to connect with the server from my local machine and make changes via Visual Studio that will be immediately present in the UI, so, in that sense at least, there is not a connection problem (though there could be others that just aren't seen at the moment).

I am using the instructions in Option 1 (ie, using the web.config) to record the logs, and have copied and pasted the relevant code into my web.config. I have manually created the relevant directories, as well as the files. https://github.com/googleads/googleads-dotnet-lib/wiki/How-to-capture-SOAP-messages

Despite all of the above, no logs are produced. Is there something else I should be doing? Is there a setting that I am not enabling / disabling?

Any help on this would be much appreciated.

Thanks,

[AnashOommen]

Does the ASP.NET account have write permissions to the folder you created? Typically, it doesn't have permissions to write to C:\Logs (i.e. a path outside the website root directory).

[phamtri]

I had permissions to write to C:\Logs. I to use "Option 3: Use System.Net tracing" is good, but "Opttion 1" is not.

[AnashOommen]

Apologies for the delay. Could you attach a very basic asp.net application illustrating the issue? You may also email it to [email protected] if you can't attach it.

[ducaihua]

I think I have exactly the same issue as phamtri, there is no log generated by using opt 1. I believe the issue start to show since v201705? Previous version can generate the soap log without any issues.

[AnashOommen]

Could you attach a simple code example to replicate this issue? A very minimal ASP.NET application should be enough.

[ducaihua]

Hi @AnashOommen , I think I found the logging issue. Basically the help doc here is out of date I believe: https://github.com/googleads/googleads-dotnet-lib/wiki/How-to-capture-SOAP-messages

In order to support the soap message, I have added the following according to the code samples and it works well.

<source name="AdsClientLibs.DetailedRequestLogs" switchName="AdsClientLibs.DetailedRequestLogs" switchType="System.Diagnostics.SourceSwitch"> <listeners> <add name="detailedRequestLogListener" type="System.Diagnostics.ConsoleTraceListener" initializeData="true"/> <!-- Use the following to log to file. Modify the initializeData attribute to control the path to the detailed request log file. <add name="detailedRequestLogListener" type="System.Diagnostics.TextWriterTraceListener" initializeData="C:\Logs\AdWords\detailed_logs.log"/> --> <remove name="Default"/> </listeners> </source> <source name="AdsClientLibs.SummaryRequestLogs" switchName="AdsClientLibs.SummaryRequestLogs" switchType="System.Diagnostics.SourceSwitch"> <listeners> <add name="summaryRequestLogListener" type="System.Diagnostics.ConsoleTraceListener" initializeData="true"/> <!-- Use the following to log to file. Modify the initializeData attribute to control the path to the summary request log file. <add name="summaryRequestLogListener" type="System.Diagnostics.TextWriterTraceListener" initializeData="C:\Logs\AdWords\summary_logs.log"/> --> <remove name="Default"/> </listeners> </source>

BTW, when I check the logs, I found we don't put clientCustomerId in the AdsClientLibs.SummaryRequestLogs . Is there some places we can enable clientCustomerId in the summary log? It will really helpful to troubleshooting.

Thanks
Caihua.

[ducaihua]

@AnashOommen hey Anash, just wondering if you get a chance to check this request, it will help us to send escalation in AdWords API forum:

BTW, when I check the logs, I found we don't put clientCustomerId in the AdsClientLibs.SummaryRequestLogs . Is there some places we can enable clientCustomerId in the summary log? It will really helpful to troubleshooting.

[AnashOommen]

Hi Caihua,

Apologies for the delay, I'll take a look at this request. It should hopefully be simple enough to support.

[ducaihua]

@AnashOommen thank you Anash. Please let me know if we can have an improvement on this log, and we will have a try once it's there.