Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I want to use websocket as an input source #3367

Open
Maingol opened this issue Nov 11, 2024 · 7 comments
Open

I want to use websocket as an input source #3367

Maingol opened this issue Nov 11, 2024 · 7 comments

Comments

@Maingol
Copy link

Maingol commented Nov 11, 2024

I want to use websocket as an input source, I have read your documentation, and according to its operation, I can add a websocket type source configuration group through the api, but when I try to edit it, has been prompted by the lack of related plug-ins, but your plug-ins to download the entrance and does not provide a websocket connection, too many related bugs! I'm not sure if you really intend to support websocket input sources, or if I'm not using it in the right way, can you provide me with detailed steps to realize this requirement?

@ngjaying
Copy link
Collaborator

Which version do you use? @Maingol

@Maingol
Copy link
Author

Maingol commented Nov 11, 2024

I've tried both 1.13.4 and the latest 2.0

@ngjaying
Copy link
Collaborator

Please add your test case to reproduce? Do you use docker image? What tag do you use?

@Maingol
Copy link
Author

Maingol commented Nov 11, 2024

docker
lfedge/ekuiper:1.13.4-slim

@Yisaer
Copy link
Collaborator

Yisaer commented Nov 11, 2024

Hi @Maingol

How did you create websocket stream and the related rules? Did you create it with manager-ui. If so, the manager-ui isn't maintained now thus it may happened the unexpected bug. Please create stream/rules by rest api according to the documents:
https://ekuiper.org/docs/en/latest/api/restapi/streams.html

@Maingol
Copy link
Author

Maingol commented Nov 11, 2024

The introduction is too vague, what exactly do I have to do, can one api do it? Can an API specify both the stream creation and the websocket address? How do I specify the websocket address? Do I need to add a source configuration group with the api? Can you build a simple demo on your own machine to realize the need to read data from a websocket source, and then tell me the detailed steps?

@ngjaying
Copy link
Collaborator

All source configurations are alike. Using confkey to refer to the config in a yaml file for that source kind. Check out mqtt source as an example https://ekuiper.org/docs/en/latest/guide/sources/builtin/mqtt.html#configurations

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants