[Task] <support monitoring WebSocket metrics>

[tomsun28]

Description

support monitoring WebSocket metrics, available, response time and more.

Task List

• [ ] support monitoring WebSocket metrics
• [ ] add help doc

[ZY945]

I made a request through the Java. net. Socket class, but its connect method seems to be unable to set a timeout, Here are the relevant discussions https://stackoverflow.com/questions/12976608/whats-the-connection-timeout-of-a-socket-created-with-a-connecting-constructor

[ZY945]

https://github.com/TooTallNate/Java-WebSocket This is also an option

[tomsun28]

Hi we can consider not supporting users to set connect timeout. About thrid library, it's up to you to decide whether to use it.👍

[tomsun28]

hi how about use java websocket api instead of socket. tcp protocol -> http protocol -> websocket protocol maybe like this, i am not sure it's ok.

   WebSocketClient client = new WebSocketClient();
   container.connectToServer(client, new URI(uri));

[hertzbeat]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

hi how about use java websocket api instead of socket. tcp protocol -> http protocol -> websocket protocol maybe like this, i am not sure it's ok.

   WebSocketClient client = new WebSocketClient();
   container.connectToServer(client, new URI(uri));

[ZY945]

hi how about use java websocket api instead of socket. tcp protocol -> http protocol -> websocket protocol maybe like this, i am not sure it's ok.

   WebSocketClient client = new WebSocketClient();
   container.connectToServer(client, new URI(uri));

The socket I'm using returns the following, I can try replacing it with websocket

[ZY945]

hi how about use java websocket api instead of socket. tcp protocol -> http protocol -> websocket protocol maybe like this, i am not sure it's ok.

   WebSocketClient client = new WebSocketClient();
   container.connectToServer(client, new URI(uri));

The websocket seems to be asynchronous and cannot confirm whether it is appropriate to store the serverHandshake response in the map

[ZY945]

hi how about use java websocket api instead of socket. tcp protocol -> http protocol -> websocket protocol maybe like this, i am not sure it's ok.

   WebSocketClient client = new WebSocketClient();
   container.connectToServer(client, new URI(uri));

The websocket seems to be asynchronous and cannot confirm whether it is appropriate to store the serverHandshake response in the map If I use CountDownLatch to wait, it will keep blocking, I don't know why

[ZY945]

hi how about use java websocket api instead of socket. tcp protocol -> http protocol -> websocket protocol maybe like this, i am not sure it's ok.

   WebSocketClient client = new WebSocketClient();
   container.connectToServer(client, new URI(uri));

The websocket seems to be asynchronous and cannot confirm whether it is appropriate to store the serverHandshake response in the map If I use CountDownLatch to wait, it will keep blocking, I don't know why

Import error..

[tomsun28]

hi try the uri like this String uri = "ws://localhost:8080/your-websocket-endpoint";

[tomsun28]

👍👍 Great！It's work, you decide which one way we use.

[ZY945]

hi try the uri like this String uri = "ws://localhost:8080/your-websocket-endpoint";

You're right, it's true that I wrote the wrong uri，It works and nedd the dependency

        <dependency>
            <groupId>org.java-websocket</groupId>
            <artifactId>Java-WebSocket</artifactId>
            <version>1.5.2</version>
            <scope>compile</scope>
        </dependency>

[ZY945]

👍👍 Great！It's work, you decide which one way we use.

Extra packages needed to be introduced, and at the same time it seemed that there wasn't enough information to get the handshake, so I used the socket

[tomsun28]

Extra packages needed to be introduced, and at the same time it seemed that there wasn't enough information to get the handshake, so I used the socket !

👍👍！