Bring back "Kusto"

%3CLINGO-SUB%20id%3D%22lingo-sub-108377%22%20slang%3D%22en-US%22%3EBring%20back%20%22Kusto%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-108377%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20query%20language%20needs%20a%20unique%2C%20searchable%20name.%3C%2FP%3E%3CP%3EWe%20need%20a%20way%20to%20refer%20to%20the%20query%20language%20and%20to%20share%20content%20with%20the%20community.%3C%2FP%3E%3CP%3EAs%20my%20skills%20with%20the%20query%20language%20grows%2C%20I%20can%20write%20lots%20of%20blog%20articles%20to%20help%20others%20with%20their%20search%20for%20help%20with%20the%20language.%20But%20as%20is%2C%20those%20articles%20will%20never%20be%20read%2C%20because%20they%20will%20never%20be%20found%20with%20a%20search%20engine.%3C%2FP%3E%3CP%3EIf%20people%20can't%20find%20answers%20to%20their%20questions%2C%20the%20learning%20curve%20will%20be%20too%20steep%2C%20and%20adoption%20of%20OMS%20Log%20Analytics%20will%20be%20suffer%20dramatically.%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20query%20language%20needs%20a%20unique%2C%20searchable%20name%2C%20and%20it%20needs%20one%20as%20soon%20as%20possible.%20We%20need%20to%20bring%20back%20%22Kusto%22.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-108377%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EQuery%20Language%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-108579%22%20slang%3D%22en-US%22%3ERe%3A%20Bring%20back%20%22Kusto%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-108579%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20if%20we%20standardize%20on%20the%20acronym%20and%20start%20calling%20it%20Azure%20LAQL%20or%20more%20often%20as%20just%20LAQL%2C%20pronounced%20layquel.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

The query language needs a unique, searchable name.

We need a way to refer to the query language and to share content with the community.

As my skills with the query language grows, I can write lots of blog articles to help others with their search for help with the language. But as is, those articles will never be read, because they will never be found with a search engine.

If people can't find answers to their questions, the learning curve will be too steep, and adoption of OMS Log Analytics will be suffer dramatically.

The query language needs a unique, searchable name, and it needs one as soon as possible. We need to bring back "Kusto".

1 Reply
Highlighted

What if we standardize on the acronym and start calling it Azure LAQL or more often as just LAQL, pronounced layquel.