Skip to content
This repository has been archived by the owner on Mar 16, 2021. It is now read-only.

Tweaked Search Service's Successful Request Telemetry Logic #193

Merged
merged 2 commits into from
May 24, 2017

Conversation

loic-sharma
Copy link
Contributor

The Search Service marked 400 and 404 response codes as unsuccessful requests on Application Insights, which causes lots of unwanted noise. This adds the TelemetryResponseCodeProcessor to the Search Service's Application Insights configuration to mark these responses' telemetry as successful.

@@ -5,6 +5,12 @@
<Add Type="Microsoft.ApplicationInsights.WindowsServer.TelemetryChannel.AdaptiveSamplingTelemetryProcessor, Microsoft.AI.ServerTelemetryChannel">
<MaxTelemetryItemsPerSecond>5</MaxTelemetryItemsPerSecond>
</Add>
<Add Type="NuGet.Services.Logging.TelemetryResponseCodeProcessor, NuGet.Services.Logging">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file resets every time you update AI nuget package version. Can we move the changes to code?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, I didn't know that. That sounds good to me.

@loic-sharma loic-sharma merged commit 266c65b into dev May 24, 2017
shishirx34 added a commit that referenced this pull request Jun 9, 2017
* Fixed Application Insights Sampling and Duplication Issues (#183)
* Removed Serilog's Request tracing
* Don't sample traces and exceptions
* Tweaked Search Service's Successful Request Telemetry Logic (#193)
* V3 monitoring job: emit validation status of packages to blob storage (#192)
* Enable blob snapshot (#177)
* Add V3 monitoring deployment scripts (#196)
* Fixed RoleInstance log value on Search Service (#194)
* Update telemetry processors (#198)
* V3 monitoring job: make RegistrationIdValidator case insensitive (#197)
@loic-sharma loic-sharma deleted the loshar-404fix branch May 1, 2018 20:03
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants