SOLVED

ConfigurationChange table weirdness

%3CLINGO-SUB%20id%3D%22lingo-sub-1019575%22%20slang%3D%22en-US%22%3EConfigurationChange%20table%20weirdness%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1019575%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20just%20added%20the%26nbsp%3BChange%20Tracking%20solution%20to%20my%20LA%20workspace.%20I%20have%20connected%202%20Az%20VMs%20running%20server%202019.%20All%20looks%20healthy%20(Event%2C%20Perf%2C%20Heartbeat%20data%20collected)%20but%20when%20I%20go%20to%20run%20a%20query%20against%20the%20ConfigurationChange%20table%2C%20sometimes%20it%20disappears.%20I%20will%20literally%20run%20a%20query%20that%20works%20then%20the%202nd%20time%20it%20fails%20because%20the%20table%20can't%20be%20found.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20help%20would%20be%20great.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1019575%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EQuery%20Language%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESolutions%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1039746%22%20slang%3D%22en-US%22%3ERe%3A%20ConfigurationChange%20table%20weirdness%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1039746%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F462742%22%20target%3D%22_blank%22%3E%40Anthony_Milic%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20was%20probably%20temporary%20issue%20with%20the%20Log%20Analytics%20service%20that%20should%20be%20fixed%20now.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Visitor

Hi all,

 

I just added the Change Tracking solution to my LA workspace. I have connected 2 Az VMs running server 2019. All looks healthy (Event, Perf, Heartbeat data collected) but when I go to run a query against the ConfigurationChange table, sometimes it disappears. I will literally run a query that works then the 2nd time it fails because the table can't be found.

 

Any help would be great.

1 Reply
Best Response confirmed by Stanislav Zhelyazkov (MVP)
Solution

@Anthony_Milic 

This was probably temporary issue with the Log Analytics service that should be fixed now.