The workspace() expression is now causing syntax errors when its used on Azure Gov CSP

%3CLINGO-SUB%20id%3D%22lingo-sub-1025303%22%20slang%3D%22en-US%22%3EThe%20workspace()%20expression%20is%20now%20causing%20syntax%20errors%20when%20its%20used%20on%20Azure%20Gov%20CSP%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1025303%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20week%2C%20the%20workspace(%22workspacename%22).perf%20expression%20now%20throws%20syntax%20errors%3C%2FP%3E%3CP%3EWorked%20perfectly%20as%20recently%20as%20monday%20this%20week.%20Is%20this%20a%20permanent%20change%20or%20is%20it%20just%20another%20bug%20in%20log%20analytics%20to%20add%20to%20the%20long%20list%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1025303%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EQuery%20Language%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1026372%22%20slang%3D%22en-US%22%3ERe%3A%20The%20workspace()%20expression%20is%20now%20causing%20syntax%20errors%20when%20its%20used%20on%20Azure%20Gov%20CSP%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1026372%22%20slang%3D%22en-US%22%3EI%20have%20no%20idea%20if%20there%20was%20a%20change%2C%20but%20perf%20should%20be%20Perf%20(with%20a%20capital)%20and%20my%20queries%20are%20still%20working...in%20Azure%20Commercial%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1037618%22%20slang%3D%22en-US%22%3ERe%3A%20The%20workspace()%20expression%20is%20now%20causing%20syntax%20errors%20when%20its%20used%20on%20Azure%20Gov%20CSP%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1037618%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F465197%22%20target%3D%22_blank%22%3E%40brian_weatherill%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20had%20a%20breaking%20change%20that%20probably%20caused%20this.%20It%20was%20quickly%20fixed%20in%20public%20instances%2C%20it%20takes%20a%20bit%20more%20time%20on%20isolated%20instances.%20Please%20let%20me%20know%20if%20the%20problem%20linger.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%2C%3C%2FP%3E%0A%3CP%3EMeir%20%3A%26gt%3B%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

This week, the workspace("workspacename").perf expression now throws syntax errors

Worked perfectly as recently as monday this week. Is this a permanent change or is it just another bug in log analytics to add to the long list?

2 Replies
I have no idea if there was a change, but perf should be Perf (with a capital) and my queries are still working...in Azure Commercial

Hi @brian_weatherill,

 

We had a breaking change that probably caused this. It was quickly fixed in public instances, it takes a bit more time on isolated instances. Please let me know if the problem linger.

 

Thanks,

Meir :>