An ASP.NET application using the Application Insights SDK sends very high telemetry rates and experiences ingestion throttling. To lower telemetry volume and keep correct correlation while controlling per-second throughput, what should you do?

The correct approach is to verify adaptive sampling is enabled and set the maxTelemetryItemsPerSecond value. Adaptive sampling dynamically adjusts the volume of telemetry sent, ensuring that your application doesn't exceed ingestion limits while maintaining correct correlation between related telemetry items (requests, dependencies, traces). Setting maxTelemetryItemsPerSecond directly controls the maximum number of telemetry items sent per second, providing a hard limit to prevent throttling. Setting a daily cap on the Log Analytics workspace or modifying its pricing tier does not address the high telemetry volume at the source or control per-second throughput. These are billing or storage management options, not volume control mechanisms for ingestion. Similarly, setting retention and archive policies or purging data only affects how data is stored and managed after ingestion, not the volume being sent to Application Insights.