Site Recovery job fails - Query doesn't seem work.

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure

https://docs.microsoft.com/azure

Creative Commons Attribution 4.0 International

10.22k stars 21.38k forks source link

Site Recovery job fails - Query doesn't seem work. #38792

Closed sochan1 closed 5 years ago

sochan1 commented 5 years ago

AzureDiagnostics | where Category == "AzureSiteRecoveryJobs" | where OperationName == "Reprotect" | where ResultType == "Failed" | summarize count()

Error : 'where' operator: Failed to resolve column or scalar expression named 'ResultType' Support id: f943406f-3a35-45a5-a436-ad16b3

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ff08de1c-1661-5523-0f1a-eca1fd34c3e9
Version Independent ID: 64502dfc-db1c-ad5e-fa61-02e0163f85f6
Content: Monitor Azure Site Recovery with Azure Monitor Logs (Log Analytics)
Content Source: articles/site-recovery/monitor-log-analytics.md
Service: site-recovery
GitHub Login: @rayne-wiselman
Microsoft Alias: raynew

KrishnaG-MSFT commented 5 years ago

@sochan1 Thanks for the comment. We are actively investigating on the issue and will get back to you shortly with an update.

sochan1 commented 5 years ago

@KrishnaG-MSFT - any update?

KrishnaG-MSFT commented 5 years ago

@sochan1 Can you please double check whether you have the column / field named 'ResultType' in AzureDiagnostics table under 'Logs' tile of your Log Analytics workspace. Similarly, check 'Custom Fields' in 'Data' section under 'Advanced Settings' tile of your Log Analytics workspace.

For illustration, please check below screenshots.

@rayne-wiselman Do you have any visibility around this issue ?

KrishnaG-MSFT commented 5 years ago

@sochan1 Did you get chance to follow my above comment and validate ?

KrishnaG-MSFT commented 5 years ago

@sochan1 I hope the issue is resolved. If not then please let us know with an update so that we can assist you better with next action plan.

Closing this issue for now. If there are further questions regarding this matter or feedback on the referred Azure documentation, please reply and we will gladly continue the discussion.