Microsoft docs log in1/3/2024 ![]() ![]() When you increase the retention policy, the new retention period applies to all data that's already been ingested into the table and hasn't yet been purged or removed. You can purge data immediately when required. When you shorten an existing retention policy, Azure Monitor waits 30 days before removing the data, so you can revert the change and prevent data loss in the event of an error in configuration. Adjustments to retention and archive settings The archive period can only be set at the table level, not at the workspace level. You can access archived data by running a search job or restoring archived logs. When you set a total retention period that's longer than the interactive retention period, Log Analytics automatically archives the relevant data immediately at the end of the retention period. ![]() When you no longer use the logs, but still need to keep the data for compliance or occasional investigation, archive the logs to save costs.Īrchived data stays in the same table, alongside the data that's available for interactive queries. You can set a different retention policy on individual tables.ĭuring the interactive retention period, data is available for monitoring, troubleshooting, and analytics. How retention and archiving workĮach workspace has a default retention policy that's applied to all tables. To configure set data retention and archiving, you must have at least contributor rights. This article describes how to configure data retention and archiving. Archiving lets you keep older, less used data in your workspace at a reduced cost. ![]() Retention policies define when to remove or archive data in a Log Analytics workspace. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |