Rules

Rules are defined by JSON, below is an example.

{
  "id": "rule1",
  "sql": "SELECT demo.temperature, demo1.temp FROM demo left join demo1 on demo.timestamp = demo1.timestamp where demo.temperature > demo1.temp GROUP BY demo.temperature, HOPPINGWINDOW(ss, 20, 10)",
  "actions": [
    {
      "log": {}
    },
    {
      "mqtt": {
        "server": "tcp://47.52.67.87:1883",
        "topic": "demoSink"
      }
    }
  ]
}

The following 3 parameters are required for creating a rule.

Parameters

id

The identification of the rule. The rule name cannot be duplicated in the same Kuiper instance.

sql

The sql query to run for the rule.

Options

The current options includes:

For detail about qos and checkpointInterval, please check state and fault tolerance.

The rule options can be defined globally in etc/kuiper.yaml under the rules section. The options defined in the rule json will override the global setting.

Sources

• Kuiper provides embeded following 3 sources,
  • MQTT source, see MQTT source stream for more detailed info.
  • EdgeX source by default is shipped in docker images (opens new window), but NOT included in single download binary files, you use make pkg_with_edgex command to build a binary package that supports EdgeX source. Please see EdgeX source stream for more detailed info.
  • HTTP pull source, regularly pull the contents at user’s specified interval time, see here for more detailed info.
• See SQL for more info of Kuiper SQL.
• Sources can be customized, see extension for more detailed info.

Sinks/Actions

Currently, below kinds of sinks/actions are supported:

• log: Send the result to log file.
• mqtt: Send the result to an MQTT broker.
• edgex: Send the result to EdgeX message bus.
• rest: Send the result to a Rest HTTP server.
• nop: Send the result to a nop operation.

Each action can define its own properties. There are several common properties:

property name	Type & Default Value	Description
concurrency	int: 1	Specify how many instances of the sink will be run. If the value is bigger than 1, the order of the messages may not be retained.
bufferLength	int: 1024	Specify how many messages can be buffered in memory. If the buffered messages exceed the limit, the sink will block message receiving until the buffered messages have been sent out so that the buffered size is less than the limit.
runAsync	bool:false	Whether the sink will run asynchronously for better performance. If it is true, the sink result order is not promised.
retryInterval	int:1000	Specify how many milliseconds will the sink retry to send data out if the previous send failed. If the specified value <= 0, then it will not retry.
retryCount	int:3	Specify how many will the sink retry to send data out if the previous send failed. If the specified value <= 0, then it will not retry.
cacheLength	int:1024	Specify how many messages can be cached. The cached messages will be resent to external system until the data sent out successfully. The cached message will be sent in order except in runAsync or concurrent mode. The cached message will be saved to disk in fixed intervals.
cacheSaveInterval	int:1000	Specify the interval to save cached message to the disk. Notice that, if the rule is closed in plan, all the cached messages will be saved at close. A larger value can reduce the saving overhead but may lose more cache messages when the system is interrupted in error.
omitIfEmpty	bool: false	If the configuration item is set to true, when SELECT result is empty, then the result will not feed to sink operator.
sendSingle	true	The output messages are received as an array. This is indicate whether to send the results one by one. If false, the output message will be {“result”:”${the string of received message}”}. For example, {“result”:”[{\”count\”:30},”\”count\”:20}]”}. Otherwise, the result message will be sent one by one with the actual field name. For the same example as above, it will send {“count”:30}, then send {“count”:20} to the RESTful endpoint.Default to false.
dataTemplate	true	The golang template (opens new window) format string to specify the output data format. The input of the template is the sink message which is always an array of map. If no data template is specified, the raw input will be the data.

Data Template

User can refer to Use Golang template to customize analaysis result in Kuiper for more detailed scenarios. If sendSingle is true, the data template will execute against a record; Otherwise, it will execute against the whole array of records. Typical data templates are:

For example, we have the sink input as

[]map[string]interface{}{{
    "ab" : "hello1",
},{
    "ab" : "hello2",
}}

In sendSingle=true mode:

• Print out the whole record

"dataTemplate": "{\"content\":{{json .}}}",

• Print out the ab field

"dataTemplate": "{\"content\":{{.ab}}}",

if the ab field is a string, add the quotes

"dataTemplate": "{\"content\":\"{{.ab}}\"}",

In sendSingle=false mode:

• Print out the whole record array

"dataTemplate": "{\"content\":{{json .}}}",

• Print out the first record

"dataTemplate": "{\"content\":{{json (index . 0)}}}",

• Print out the field ab of the first record

"dataTemplate": "{\"content\":{{index . 0 \"ab\"}}}",

• Print out field ab of each record in the array to html format

"dataTemplate": "<div>results</div><ul>{{range .}}<li>{{.ab}}</li>{{end}}</ul>",

Actions could be customized to support different kinds of outputs, see extension for more detailed info.

Functions supported in template

Kuiper extends several functions that can be used in data template.

• json para1: The json function is used for convert the map content to a JSON string.
• base64 para1: The base64 function is used for encoding parameter value to a base64 string.
• add para1 para2: The add function is used for adding two numeric value.