DX Application Performance Management

 View Only
  • 1.  Can´t connect to my DX APM SaaS

    Posted Jul 27, 2021 07:46 PM
    Hello,

    Anybody can help me to resolve this issue:

    We have a BizOps Starter Edition with DX APM however we can`t able to conect an agent since 4 week ago:

    the logs tell this:

    7/27/21 04:48:44 PM COT [ERROR] [IntroscopeAgent.IsengardMessaging] WebSocket handshake failed:Invalid handshake response getStatus: 403 Forbidden

    7/27/21 04:48:44 PM COT [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at apmgw.dxi-na1.saas.broadcom.com:443,com.wily.isengard.client.t

    ransport.websocket.SSLWebSocketFactory (io.netty.handler.codec.http.websocketx.WebSocketClientHandshakeException:Invalid handshake response getStatus: 403 Forbidden).

    7/27/21 04:48:44 PM COT [INFO] [IntroscopeAgent.Agent] Callback already set.

    the workstation log tells the same:

    7/27/21 04:54:37 p. m. COT [INFO] [Workstation] Introscope Workstation Versi?n 21.6.0.26 (Compilaci?n 990026)
    7/27/21 04:54:37 p. m. COT [INFO] [Workstation] Using Java VM version "Java HotSpot(TM) 64-Bit Server VM 11.0.11" from Oracle Corporation
    7/27/21 04:54:37 p. m. COT [INFO] [Workstation] Using Introscope installation at: C:\Users\rafae\Downloads\workstation20\.
    7/27/21 04:54:37 p. m. COT [INFO] [Workstation] DX APM Wily Introscope(R) Version 21.6.0.26
    7/27/21 04:54:37 p. m. COT [INFO] [Workstation] Copyright (c) 2021 Broadcom. All Rights Reserved.
    7/27/21 04:54:37 p. m. COT [INFO] [Workstation] Introscope(R) is a registered trademark of DX APM.
    7/27/21 04:54:37 p. m. COT [INFO] [Workstation] Starting Introscope Workstation...
    7/27/21 04:54:37 p. m. COT [INFO] [Workstation] re-loading configuration resource C:\Users\rafae\Downloads\workstation20\config\IntroscopeWorkstation.properties
    7/27/21 04:54:45 p. m. COT [INFO] [Workstation] Introscope Workstation started.
    7/27/21 04:55:29 p. m. COT [INFO] [Workstation.Login] transport.https.fips.third.party.api=null (default)
    7/27/21 04:55:29 p. m. COT [INFO] [Workstation.Login] SSL socket factory supported ciphers are: [TLS_AES_128_GCM_SHA256, TLS_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_DSS_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_DSS_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_RSA_WITH_AES_256_CBC_SHA256, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384, TLS_DHE_RSA_WITH_AES_256_CBC_SHA256, TLS_DHE_DSS_WITH_AES_256_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_DSS_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_EMPTY_RENEGOTIATION_INFO_SCSV]
    7/27/21 04:55:29 p. m. COT [INFO] [Workstation.Login] SSL socket factory configured cipher TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 is not supported by JVM
    7/27/21 04:55:29 p. m. COT [INFO] [Workstation.Login] SSL socket factory configured cipher TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 is not supported by JVM
    7/27/21 04:55:29 p. m. COT [INFO] [Workstation.Login] Setting SSL socket ciphers to: [TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256]
    7/27/21 04:55:48 p. m. COT [ERROR] [Workstation.Login] WebSocket handshake failed:Invalid handshake response getStatus: 403 Forbidden
    7/27/21 04:55:48 p. m. COT [WARN] [Workstation] Error attempting to connect to the Enterprise Manager "apmgw.dxi-na1.saas.broadcom.com".
    7/27/21 04:56:18 p. m. COT [INFO] [Workstation.Login] WebSocket socket channel closed.



    Adicional the Experience Collector show disconected of the agent list:



    Any idea of what is happen?

    Best Regards



    ------------------------------
    Consultor Senior APM
    Netready Colombia SAS
    ------------------------------


  • 2.  RE: Can´t connect to my DX APM SaaS

    Broadcom Employee
    Posted Jul 28, 2021 11:00 AM
    This has been my first Community post in a long time. As a workaround try another protocol like http, https


  • 3.  RE: Can´t connect to my DX APM SaaS

    Posted Jul 28, 2021 11:32 AM
    I try with https and make the same:





    Best Regards

    ------------------------------
    Consultor Senior APM
    Netready Colombia SAS
    ------------------------------



  • 4.  RE: Can´t connect to my DX APM SaaS

    Broadcom Employee
    Posted Jul 28, 2021 11:48 AM
    > BizOps Starter Edition with DX APM
    Not sure if still supported



  • 5.  RE: Can´t connect to my DX APM SaaS

    Broadcom Employee
    Posted Jul 29, 2021 10:47 AM
    The easiest way around the issue is to setup DX Cloud Proxy and point your workstation client at it.

    Honestly, there is no reason at all to use the workstation client; you're losing functionality by using it and no enhancements are being planned for it. Use your browser to connect.

    ------------------------------
    Solution Engineering
    Broadcom
    ------------------------------



  • 6.  RE: Can´t connect to my DX APM SaaS

    Posted Jul 29, 2021 02:47 PM
    Hello Haruhiko,

    From DX Colud Proxy i recived this:


    the other thing is that Experience Collector is disconnected, this Experience Collector is on SaaS and i dont have right to administrate:



    Best Regrads

    ------------------------------
    Consultor Senior APM
    Netready Colombia SAS
    ------------------------------



  • 7.  RE: Can´t connect to my DX APM SaaS

    Broadcom Employee
    Posted Jul 29, 2021 03:24 PM
    Workstation client requires Java 8; Cloud Proxy requires Java 11. Please make sure you have the right JREs.

    Aside from that, there seems to be an issue with your tenant. If you haven't do so already, please open a support ticket to have our SaaS ops folks look at your tenant and see if any of the pods needs restarting.