Manage tables in a Log Analytics workspace
Azure Monitor Logs stores log data in tables. Table configuration lets you define how to store collected data, how long to retain the data, and whether you collect the data for auditing and troubleshooting or for ongoing data analysis and regular use by features and services.
This article explains the table configuration options in Azure Monitor Logs and how to manage table settings based on your data analysis and cost management needs.
Table configuration settings
This diagram provides an overview of the table configuration options in Azure Monitor Logs:
In the Azure portal, you can view and set table configuration settings by selecting Tables from your Log Analytics workspace.
A Log Analytics workspace lets you collect logs from Azure and non-Azure resources into one space for data analysis, use by other services, such as Sentinel, and to trigger alerts and actions, for example, using Logic Apps.
Your Log Analytics workspace can contain the following types of tables:
|Table type||Data source||Setup|
|Azure table||Logs from Azure resources or required by Azure services and solutions.||Azure Monitor Logs creates Azure tables automatically based on Azure services you use and diagnostic settings you configure for specific resources.|
|Custom table||Non-Azure resource and any other data source, such as file-based logs.||Create a custom table.|
|Search results||Logs within the workspace.||Azure Monitor creates a search job results table when you run a search job.|
|Restored logs||Archived logs.||Azure Monitor creates a restored logs table when you restore archived logs.|
A table's schema is the set of columns that make up the table, into which Azure Monitor Logs collects log data from one or more data sources.
Azure table schema
Each Azure table has a predefined schema into which Azure Monitor Logs collects logs defined by Azure resources, services, and solutions.
You can add columns to an Azure table to store transformed log data or enrich data in the Azure table with data from another source.
Custom table schema
You can define a custom table's schema based on how you want to store data you collect from a given data source.
Reduce costs and analysis effort by using data collection rules to filter out and transform data before ingestion based on the schema you define for your custom table.
Search results and restored logs table schema
The schema of a search results table is based on the query you define when you run the search job.
A restored logs table has the same schema as the table from which you restore logs.
You can't edit the schema of existing search results and restored logs tables.
Log data plan
Configure a table's log data plan based on how often you access the data in the table. The Basic log data plan provides a low-cost way to ingest and retain logs for troubleshooting, debugging, auditing, and compliance. The Analytics plan makes log data available for interactive queries and use by features and services.
Retention and archive
Archiving is a low-cost solution for keeping data that you no longer use regularly in your workspace for compliance or occasional investigation. Set table-level retention policies to override the default workspace retention policy and to archive data within your workspace.
Learn how to:
Submit and view feedback for