Share via

log analytics workspace agent connectivity not possible for region germany west central?

Holger Gerling 21 Reputation points
2022-09-26T17:16:11.66+00:00

hej hej, actually and since friday (23.09.2022, near 1 AM UTC) the agents and OMS Gateway is no longer able to bring information into the log analytics workspace.
we checked this article https://learn.microsoft.com/en-us/troubleshoot/azure/azure-monitor/log-analytics/ssl-connectivity-mma-windows-powershell and were able to find out, that other regions (e.g. west europe) works, but no log analytics workspace located at germany west central - no existing or new created.

error message (in german): WARNUNG: Ausnahme beim Aufrufen von ".ctor" mit 2 Argument(en): "Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehle
rhaft, da der verbundene Host nicht reagiert hat 51.116.155.245:443" / ......oms.opinsights.azure.com

can someone help or has any other advice?

Azure Monitor
Azure Monitor
An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.
3,037 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,635 questions
Microsoft Sentinel
Microsoft Sentinel
A scalable, cloud-native solution for security information event management and security orchestration automated response. Previously known as Azure Sentinel.
1,065 questions
0 comments
Accepted answer
  1. Carlos Villagomez 1,106 Reputation points Microsoft Employee
    2022-09-26T18:50:16.383+00:00

    Hello @Holger Gerling ,

    Thank you for your post! I spoke to my team and based off your screenshots and investigation I did with our Azure Support Team, we think it's best for you to work more closely with our Support Engineers to get this issue resolved.

    Please run the data collection tool on your OMS Gateway computer found here and per the article, choose the Agent not reporting data or heartbeat data missing option under the Scenario Covered section of this article. Then once this the diagnostic report has completed, there will be a zip file which Azure Support can help you troubleshoot.

    If you already have a support plan then to find the root cause of the issue here, I recommend you reach the Azure technical support team by raising a support ticket as mentioned here.

    Otherwise, if you don't have a support plan then to find the root cause of the issue here, please send an email with subject "Attn:Carlos" to AzCommunity@microsoft.com with your subscription ID and a link of this question for context and we will assist you with engaging Azure technical support for a free technical support request.

    Thank you again for your time and patience throughout this issue.

    Carlos V.

    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Holger Gerling 21 Reputation points
    2022-09-27T07:13:04.12+00:00

    hej hej @Carlos Villagomez , thanks for the quick reply!

    it seems to work now, something happened over night. we are now able to get informations from the oms gateway into the workspace.

    CheckSSL now returns:
    ...............oms.opinsights.azure.com / 51.116.250.154 

    SslProtocol               : Tls  
CipherAlgorithm           : Aes256  
HashAlgorithm             : Sha1  
KeyExchangeAlgorithm      : 44550  
IsAuthenticated           : True  
IsEncrypted               : True  
IsSigned                  : True  
CheckCertRevocationStatus : False  
  
  
Subject      : CN=dewc-oi-oms.la.trafficmanager.net  
Issuer       : CN=Microsoft RSA TLS CA 01, O=Microsoft Corporation, C=US  
FriendlyName :   
NotBefore    : 03.06.2022 00:10:01  
NotAfter     : 03.06.2023 00:10:01  
Thumbprint   : 268FDB3DFB9B899695DCEC4987C3B19354EEC322

    so by now i think this topic can be closed.

    Thank you and best regards,

    holger

    0 comments