What Naming Convention Works Best for Large Azure Log Analytics Workspaces?
Asked by
MellowCedar42
Our organization expects to collect data from more than 50 sources, resulting in hundreds of tables and custom tables in Azure Log Analytics. What naming convention would keep the tables easy to identify, search, and manage as the environment grows?
Answers
In some environments, teams avoid creating many custom tables by using the standard .NET Application Insights SDK. For application separation, deploying a separate Log Analytics Workspace per application can also keep the data easier to manage, although that may not fit every organization’s architecture.
Reply to this answer
Custom Log Analytics table names can be up to 256 characters, and custom tables need to end with the `_CL` suffix. PascalCase is a reasonable choice because it makes longer names easier to scan, but the most important thing is to define a consistent structure—such as source, service, and event type—and apply it everywhere.
Reply to this answer
Add your answer
Answers are reviewed before publication.
MellowCedar42: The goal is to bring many different kinds of data into a shared Log Analytics Workspace. With hundreds of tables, I’m concerned that searching and using the data will become difficult without a clear naming standard.