|
před 5 roky | |
---|---|---|
.. | ||
Dockerfile | před 5 roky | |
README.md | před 5 roky | |
docker-entrypoint.sh | před 5 roky |
Dockerfile
linksWeb
Documents
Where to file issues:
https://github.com/emqx/kuiper/issues
amd64
, arm64v8
, arm32v7
, i386
, ppc64le
The emqx/kuiper
images come in many flavors, each designed for a specific operate systems.
emqx/kuiper:<tag>
This is a stable release image that you can use with confidence.
emqx/kuiper:<tag>-<number>-<commit>
This is an unstable version. It is an image built according to the commit number. You can use it to experience the latest features.
EMQ X Kuiper is an edge lightweight IoT data analytics / streaming software implemented by Golang, and it can be run at all kinds of resource constrained edge devices. One goal of Kuiper is to migrate the cloud streaming software frameworks (such as Apache Spark,Apache Storm and Apache Flink) to edge side. Kuiper references these cloud streaming frameworks, and also considered special requirement of edge analytics, and introduced rule engine, which is based on Source
, SQL (business logic)
and Sink
, rule engine is used for developing streaming applications at edge side.
User scenarios
It can be run at various IoT edge use scenarios, such as real-time processing of production line data in the IIoT; Gateway of Connected Vehicle analyze the data from data-bus in real time; Real-time analysis of urban facility data in smart city scenarios. Kuiper processing at the edge can reduce system response latency, save network bandwidth and storage costs, and improve system security.
Features
Lightweight
Cross-platform
Data analysis support
Highly extensibile
Plugin system is provided, and it supports to extend at Source, SQL functions and Sink.
Execute some command under this docker image
docker run -d -v `pwd`:$somewhere emqx/kuiper:$tag $somecommand
For example
docker run -d --name kuiper -e MQTT_BROKER_ADDRESS=$MQTT_BROKER_ADDRESS emqx/kuiper:$tag
tcp://broker.emqx.io:1883
. broker.emqx.io
is a public MQTT test server hosted by EMQ. docker run -d --name kuiper -e MQTT_BROKER_ADDRESS=tcp://broker.emqx.io:1883 emqx/kuiper:$tag
broker.emqx.io
, and those data will be processed in your LOCAL RUN Kuiper docker instance. Below steps will create a stream named demo
, and data are sent to devices/device_001/messages
topic, while device_001
could be other devices, such as device_002
, all of those data will be subscribed and handled by demo
stream. -- In host
# docker exec -it kuiper /bin/sh
-- In docker instance
# bin/cli create stream demo '(temperature float, humidity bigint) WITH (FORMAT="JSON", DATASOURCE="devices/+/messages")'
Connecting to 127.0.0.1:20498...
Stream demo is created.
# bin/cli query
Connecting to 127.0.0.1:20498...
kuiper > select * from demo where temperature > 30;
Query was submit successfully.
devices/device_001/messages
of server tcp://broker.emqx.io:1883
with any MQTT client tools. Below sample uses mosquitto_pub
. # mosquitto_pub -h broker.emqx.io -m '{"temperature": 40, "humidity" : 20}' -t devices/device_001/messages
bin/cli query
window. Please try to publish another message with temperature
less than 30, and it will be filtered by WHERE condition of the SQL. kuiper > select * from demo WHERE temperature > 30;
[{"temperature": 40, "humidity" : 20}]
If having any problems, please take a look at log/stream.log
.
To stop the test, just press ctrl + c
in bin/cli query
command console.
Next for exploring more powerful features of EMQ X Kuiper? Refer to below for how to apply EMQ X Kuiper in edge and integrate with AWS / Azure IoT cloud.
Use the environment variable to configure etc/mqtt_sources.yaml
on the Kuiper container.
Options | Default | Mapped |
---|---|---|
MQTT_BROKER_ADDRESS | tcp://127.0.0.1:1883 | default.servers |
MQTT_BROKER_SHARED_SUBSCRIPTION | true | default.sharedSubscription |
MQTT_BROKER_QOS | 1 | default.qos |
MQTT_BROKER_USERNAME | default.username | |
MQTT_BROKER_PASSWORD | default.password | |
MQTT_BROKER_CER_PATH | default.certificationPath | |
MQTT_BROKER_KEY_PATH | default.privateKeyPath |
Use the environment variable to configure etc/sources/edgex.yaml
on the Kuiper container.
Options | Default | Mapped |
---|---|---|
EDGEX_PROTOCOL | tcp | default.protocol |
EDGEX_SERVER | localhost | default.server |
EDGEX_PORT | 5570 | default.port |
EDGEX_TOPIC | events | default.topic |
EDGEX_SERVICE_SERVER | http://localhost:10080 | default.serviceServer |
If you want to configure more options, you can mount the configuration file into Kuiper container, like this:
$ docker run --name kuiper -v /path/to/mqtt_sources.yaml:/kuiper/etc/mqtt_sources.yaml -v /path/to/edgex.yaml:/kuiper/etc/sources/edgex.yaml emqx/kuiper:$tag
If you'd like to know more about the project, please refer to Github project.