-
Notifications
You must be signed in to change notification settings - Fork 48
apply the wcf telemetry on two environments, One is getting the API operation contract logging, but another env didn't log properly #166
Comments
a fairly generic question. so you are just looking for troubleshooting ideas?
too many things... but that should get you something |
@haldiggs yes, our situation is to enable detailed wcf API operation logs without re-complying the whole code base. https://github.com/microsoft/ApplicationInsights-SDK-Labs/tree/master/WCF followed this link and it seems doing the work under our UAT env. but when move to another env, well the result turns out to be different. so I am thinking if there are any dependencies related with Server components. originally I want to ask the right question to find out what is the difference between this two environments (AppInsights WCF logging working for one, but not for the other). did lots of file comparison, I couldn't see the difference |
@haldiggs in UAT env, we have web.config and applicationinsights.config files under the wcf service directories. the Telemetry modules are defined inside the applicationinsights.config file, don't see TelemetryCorrelationHttpModule inside our applicationsinsights.config file.
instrumentationkey is inside applicationinsights.config file
I don't see ApplicationInsightsWebTracking inside the web.config
|
TelemetryCorrelationHttpModule is setup in the web config. If it's working
in UAT I would imagine you should be able to detect missing parts.
Hal D. on my Android
…On Mon, Oct 14, 2019, 6:34 PM EdmondAndy ***@***.***> wrote:
@haldiggs <https://github.com/haldiggs> in UAT env, we have web.config
and applicationinsights.config files under the wcf service directories. the
Telemetry modules are defined inside the applicationinsights.config file,
don't see TelemetryCorrelationHttpModule inside our
applicationsinsights.config file.
===========ApplicationInsights.config========================
core.windows.net
core.chinacloudapi.cn
core.cloudapi.de
core.usgovcloudapi.net
<!--
Use the following syntax here to collect additional performance counters:
<Counters>
<Add PerformanceCounter="\Process(??APP_WIN32_PROC??)\Handle Count" ReportAs="Process handle count" />
...
</Counters>
PerformanceCounter must be either \CategoryName(InstanceName)\CounterName or \CategoryName\CounterName
NOTE: performance counters configuration will be lost upon NuGet upgrade.
The following placeholders are supported as InstanceName:
??APP_WIN32_PROC?? - instance name of the application process for Win32 counters.
??APP_W3SVC_PROC?? - instance name of the application IIS worker process for IIS/ASP.NET counters.
??APP_CLR_PROC?? - instance name of the application CLR process for .NET counters.
-->
</Add>
<Add Type="Microsoft.ApplicationInsights.Extensibility.PerfCounterCollector.QuickPulse.QuickPulseTelemetryModule, Microsoft.AI.PerfCounterCollector" />
<Add Type="Microsoft.ApplicationInsights.WindowsServer.DeveloperModeWithDebuggerAttachedTelemetryModule, Microsoft.AI.WindowsServer" />
<Add Type="Microsoft.ApplicationInsights.WindowsServer.UnhandledExceptionTelemetryModule, Microsoft.AI.WindowsServer" />
<Add Type="Microsoft.ApplicationInsights.WindowsServer.UnobservedExceptionTelemetryModule, Microsoft.AI.WindowsServer">
<!--</Add>
<Add Type="Microsoft.ApplicationInsights.WindowsServer.FirstChanceExceptionStatisticsTelemetryModule, Microsoft.AI.WindowsServer">-->
</Add>
<Add Type="Microsoft.ApplicationInsights.Web.RequestTrackingTelemetryModule, Microsoft.AI.Web">
<Handlers>
<!--
Add entries here to filter out additional handlers:
NOTE: handler configuration will be lost upon NuGet upgrade.
-->
<Add>System.Web.Handlers.TransferRequestHandler</Add>
<Add>Microsoft.VisualStudio.Web.PageInspector.Runtime.Tracing.RequestDataHttpHandler</Add>
<Add>System.Web.StaticFileHandler</Add>
<Add>System.Web.Handlers.AssemblyResourceLoader</Add>
<Add>System.Web.Optimization.BundleHandler</Add>
<Add>System.Web.Script.Services.ScriptHandlerFactory</Add>
<Add>System.Web.Handlers.TraceHandler</Add>
<Add>System.Web.Services.Discovery.DiscoveryRequestHandler</Add>
<Add>System.Web.HttpDebugHandler</Add>
</Handlers>
</Add>
<Add Type="Microsoft.ApplicationInsights.Web.ExceptionTrackingTelemetryModule, Microsoft.AI.Web" />
<Add Type="Microsoft.ApplicationInsights.Web.AspNetDiagnosticTelemetryModule, Microsoft.AI.Web" />
<Add Type="Microsoft.ApplicationInsights.Wcf.RequestTrackingTelemetryModule, Microsoft.AI.Wcf"/>
<Add Type="Microsoft.ApplicationInsights.Wcf.ExceptionTrackingTelemetryModule, Microsoft.AI.Wcf"/>
============================================ instrumentationkey is inside
applicationinsights.config file Add the service serviceTelemetry key inside
the web.config ============================================
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#166?email_source=notifications&email_token=AAM5KUR7VKHMSHY533LSKPTQOT6Y5A5CNFSM4JAI4OV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBG53NA#issuecomment-541973940>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAM5KUT4IQVS4D5E5SFLHETQOT6Y5ANCNFSM4JAI4OVQ>
.
|
I may not see your whole file here but I also don't see an
instrumentationkey
That is definitely needed for your system won't know where to send
information
Hal D. on my Android
…On Mon, Oct 14, 2019, 6:34 PM EdmondAndy ***@***.***> wrote:
@haldiggs <https://github.com/haldiggs> in UAT env, we have web.config
and applicationinsights.config files under the wcf service directories. the
Telemetry modules are defined inside the applicationinsights.config file,
don't see TelemetryCorrelationHttpModule inside our
applicationsinsights.config file.
===========ApplicationInsights.config========================
core.windows.net
core.chinacloudapi.cn
core.cloudapi.de
core.usgovcloudapi.net
<!--
Use the following syntax here to collect additional performance counters:
<Counters>
<Add PerformanceCounter="\Process(??APP_WIN32_PROC??)\Handle Count" ReportAs="Process handle count" />
...
</Counters>
PerformanceCounter must be either \CategoryName(InstanceName)\CounterName or \CategoryName\CounterName
NOTE: performance counters configuration will be lost upon NuGet upgrade.
The following placeholders are supported as InstanceName:
??APP_WIN32_PROC?? - instance name of the application process for Win32 counters.
??APP_W3SVC_PROC?? - instance name of the application IIS worker process for IIS/ASP.NET counters.
??APP_CLR_PROC?? - instance name of the application CLR process for .NET counters.
-->
</Add>
<Add Type="Microsoft.ApplicationInsights.Extensibility.PerfCounterCollector.QuickPulse.QuickPulseTelemetryModule, Microsoft.AI.PerfCounterCollector" />
<Add Type="Microsoft.ApplicationInsights.WindowsServer.DeveloperModeWithDebuggerAttachedTelemetryModule, Microsoft.AI.WindowsServer" />
<Add Type="Microsoft.ApplicationInsights.WindowsServer.UnhandledExceptionTelemetryModule, Microsoft.AI.WindowsServer" />
<Add Type="Microsoft.ApplicationInsights.WindowsServer.UnobservedExceptionTelemetryModule, Microsoft.AI.WindowsServer">
<!--</Add>
<Add Type="Microsoft.ApplicationInsights.WindowsServer.FirstChanceExceptionStatisticsTelemetryModule, Microsoft.AI.WindowsServer">-->
</Add>
<Add Type="Microsoft.ApplicationInsights.Web.RequestTrackingTelemetryModule, Microsoft.AI.Web">
<Handlers>
<!--
Add entries here to filter out additional handlers:
NOTE: handler configuration will be lost upon NuGet upgrade.
-->
<Add>System.Web.Handlers.TransferRequestHandler</Add>
<Add>Microsoft.VisualStudio.Web.PageInspector.Runtime.Tracing.RequestDataHttpHandler</Add>
<Add>System.Web.StaticFileHandler</Add>
<Add>System.Web.Handlers.AssemblyResourceLoader</Add>
<Add>System.Web.Optimization.BundleHandler</Add>
<Add>System.Web.Script.Services.ScriptHandlerFactory</Add>
<Add>System.Web.Handlers.TraceHandler</Add>
<Add>System.Web.Services.Discovery.DiscoveryRequestHandler</Add>
<Add>System.Web.HttpDebugHandler</Add>
</Handlers>
</Add>
<Add Type="Microsoft.ApplicationInsights.Web.ExceptionTrackingTelemetryModule, Microsoft.AI.Web" />
<Add Type="Microsoft.ApplicationInsights.Web.AspNetDiagnosticTelemetryModule, Microsoft.AI.Web" />
<Add Type="Microsoft.ApplicationInsights.Wcf.RequestTrackingTelemetryModule, Microsoft.AI.Wcf"/>
<Add Type="Microsoft.ApplicationInsights.Wcf.ExceptionTrackingTelemetryModule, Microsoft.AI.Wcf"/>
============================================ instrumentationkey is inside
applicationinsights.config file Add the service serviceTelemetry key inside
the web.config ============================================
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#166?email_source=notifications&email_token=AAM5KUR7VKHMSHY533LSKPTQOT6Y5A5CNFSM4JAI4OV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBG53NA#issuecomment-541973940>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAM5KUT4IQVS4D5E5SFLHETQOT6Y5ANCNFSM4JAI4OVQ>
.
|
@haldiggs the instrumentation key already appended at the bottle of the applicationinsights.config file. |
I am following the instruction of https://github.com/microsoft/ApplicationInsights-SDK-Labs/tree/master/WCF to set up WCF detailed logging for traditional WCF applications under two envs. the same instruction and same packages added into the WCF app directories. however only one env can log detailed API contacts info. I used file differ tools to compare the app directories under these two env, they are identical. anyone can throw some ideas to narrow down the issue why not working under one env?
The text was updated successfully, but these errors were encountered: