A quartz-spire web app still pastes only an instrumentation key into configuration. What should the developer use for Application Insights ingestion settings?
Select an answer to reveal the explanation.
Short Explanation
Connection string is the current required/recommended setting—it names the ingestion endpoints. Ikey-only is legacy; Redis and public Blob are nonsense here.
Full Explanation
Current Application Insights configuration prefers a connection string so ingestion endpoints are explicit. For the quartz-spire web app that still pastes only an instrumentation key, the developer should set the Application Insights connection string (for example APPLICATIONINSIGHTS_CONNECTION_STRING or the SDK config equivalent). Connection strings encode where telemetry is sent; instrumentation-key-only is legacy and incomplete relative to current guidance.
Keeping only a leftover instrumentation key forever, ignoring connection-string guidance, fails because ikey-only omits endpoint details Microsoft now expects for reliable ingestion across clouds and regions.
A Redis connection string labeled as Application Insights fails because Redis endpoints have nothing to do with Insights ingestion; mislabeling does not create telemetry.
A public Blob URL containing the instrumentation key as the sole config fails because Blob URLs are not Insights connection strings, and exposing keys in public blobs is a credential leak.
Exam caveat: when migrating, place the connection string in app settings or Key Vault references and remove reliance on ikey-only; some older samples still show ikey—prefer docs’ connection-string examples. Operational check: set the connection string, restart the app, send traffic, and confirm telemetry arrives in the correct Insights resource (and region) within minutes.