You can use one Log Analytics workspace to store any type of log required for any purpose. For example:
High-volume, verbose data that requires cheap long-term storage for audit and compliance
App and resource data for troubleshooting by developers
Key event and performance data for scaling and alerting to ensure ongoing operational excellence and security
Aggregated long-term data trends for advanced analytics and machine learning
Table plans let you manage data costs based on how often you use the data in a table and the type of analysis you need the data for. This article explains and how to set a table's plan.
For information about what each table plan offers and which use cases it's optimal for, see Table plans.
Permissions required
Action
Permissions required
View table plan
Microsoft.OperationalInsights/workspaces/tables/read permissions to the Log Analytics workspace, as provided by the Log Analytics Reader built-in role, for example
Set table plan
Microsoft.OperationalInsights/workspaces/write and microsoft.operationalinsights/workspaces/tables/write permissions to the Log Analytics workspace, as provided by the Log Analytics Contributor built-in role, for example
Set the table plan
You can set the table plan to Auxiliary only when you create a custom table by using the API. Built-in Azure tables don't currently support the Auxiliary plan. After you create a table with an Auxiliary plan, you can't switch the table's plan.
All tables support the Analytics plan and all DCR-based custom tables and some Azure tables support the Basic log plan. You can switch between the Analytics and Basic plans, the change takes effect on existing data in the table immediately.
When you change a table's plan from Analytics to Basic, Azure monitor treats any data that's older than 30 days as long-term retention data based on the total retention period set for the table. In other words, the total retention period of the table remains unchanged, unless you explicitly modify the long-term retention period.
Note
You can switch a table's plan once a week.
Portal
API
CLI
PowerShell
Analytics is the default table plan of all tables you create in the portal. You can switch between the Analytics and Basic plans, as described in this section.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
You can use the search box at the top of the table viewer to enter a query to filter the data, or you can use the column filters to narrow down the data by specific values.
You can use the search box at the top of the table viewer to enter a query to filter the data, or you can use the column filters to narrow down the data by specific values.
From the Log Analytics workspaces menu, select Tables.Select Create and then New custom log (DCR-based).Specify a name and, optionally, a description for the table. You don't need to add the _CL suffix to the custom table's name - this is added automatically to the name you specify in the portal.
A Log Analytics workspace is a data store into which you can collect any type of log data from all of your Azure and non-Azure resources and applications.
You can add existing tables to workspaces by clicking on the "+ Add table" button on the tab bar within a workspace, and selecting the "Add existing table" option from the menu. Important notes: When you add an existing table to a workspace, the data you see is the actual table data, not a copy of the table.
The Azure Monitor Log Analytics API response is a JSON string that contains an array of table objects. The tables property is an array of tables that represent the query result. Each table contains name , columns , and rows properties: The name property is the name of the table.
In conclusion, Azure Monitor and Log Analytics collectively offer a robust solution for monitoring Azure resources. While Azure Monitor provides a lot of features including aggregation of logs, real-time insights and performance metrics, Log Analytics allows advanced query capabilities and extensive log data analysis.
To list all tables belonging to some user, you need to log in to that user's account and query the USER_TABLES data dictionary: SELECT * FROM user_tables; This query brings the list of all tables owned by the current user from the entire Oracle database. An Oracle user owns one schema.
Hobby: Flower arranging, Yo-yoing, Tai chi, Rowing, Macrame, Urban exploration, Knife making
Introduction: My name is Madonna Wisozk, I am a attractive, healthy, thoughtful, faithful, open, vivacious, zany person who loves writing and wants to share my knowledge and understanding with you.
We notice you're using an ad blocker
Without advertising income, we can't keep making this site awesome for you.
