A media company is designing a monitoring and log routing architecture for a new application. The application developers require Kusto Query Language (KQL) access to application performance telemetry for real-time debugging. The compliance team requires that raw HTTP access logs be retained for seven years for auditing purposes, though they will rarely be read. The security architecture must minimize ingestion and retention costs. Which diagnostic log routing and storage strategy should you recommend?
- Route the performance telemetry to a Log Analytics workspace, and route the HTTP access logs to an Azure Storage account configured with a lifecycle management policy.Cevap
- BRoute both the performance telemetry and the HTTP access logs to a single Log Analytics workspace with a seven-year retention period.
- CRoute the performance telemetry to an Azure Storage account configured with a lifecycle policy that moves data to the Archive tier, and route the HTTP access logs to a Log Analytics workspace.
- DConfigure an Azure Policy using the Deny effect to block the creation of any application resources unless they route all generated logs to both a Log Analytics workspace and a Storage account.
Cevap
Route the performance telemetry to a Log Analytics workspace, and route the HTTP access logs to an Azure Storage account configured with a lifecycle management policy.
The correct strategy separates logs based on their use case and cost. Telemetry required for developer debugging is routed to a Log Analytics workspace for KQL support. Raw HTTP logs, which are rarely accessed but must be retained for seven years, are routed to an Azure Storage account where a lifecycle policy moves them to cheaper storage tiers (like Archive) to minimize retention costs.
Adım Adım Çözüm
Anahtar Kavram
Log routing optimization based on query requirements and retention costs.