This is archived documentation for InfluxData product versions that are no longer maintained. For newer documentation, see the latest InfluxData documentation.
Kapacitor uses a DSL named
The DSL is used to define the pipelines for processing data in Kapacitor.
The TICKscript language is an invocation chaining language. Each script has a flat scope and each variable in the scope defines methods that can be called on it. These methods come in two flavors.
- Property methods – Modifies the node they are called on and returns a reference to the same node.
- Chaining methods – Creates a new node as a child of the node they are called on and returns a reference to the new node.
The reference documentation lists each node’s
Chaining methods along with examples and descriptions.
Every TICKscript will have either a
batch variable defined depending on the type of task you want to run.
batch variables are an instance of a StreamNode or SourceBatchNode respectively.
Kapacitor uses TICKscripts to define data processing pipelines. A pipeline is set of nodes that process data and edges that connect the nodes. Pipelines in Kapacitor are directed acyclic graphs (DAGs) meaning each edge has a direction that data flows and there cannot be any cycles in the pipeline.
Each edge has a type, one of the following:
- StreamEdge – an edge that transfers data a single data point at a time.
- BatchEdge – an edge that transfers data in chunks instead of one point at a time.
When connecting nodes the TICKscript language will not prevent you from connecting edges of the wrong type but rather the check will be performed at runtime. So just be aware that a syntactically correct script may define a pipeline that is invalid.
stream |from() .measurement('app') |eval(lambda: "errors" / "total") .as('error_percent') // Write the transformed data to InfluxDB |influxDBOut() .database('mydb') .retentionPolicy('myrp') .measurement('errors') .tag('kapacitor', 'true') .tag('version', '0.2')