This is archived documentation for InfluxData product versions that are no longer maintained. For newer documentation, see the latest InfluxData documentation.
An HTTPOutNode caches the most recent data for each group it has received.
The cached data is available at the given endpoint. The endpoint is the relative path from the API endpoint of the running task. For example if the task endpoint is at "/task/<task_name>" and endpoint is "top10", then the data can be requested from "/task/<task_name>/top10".
Example:
stream
.window()
.period(10s)
.every(5s)
.mapReduce(influxql.top('value', 10))
//Publish the top 10 results over the last 10s updated every 5s.
.httpOut('top10')
Chaining Methods
Chaining methods create a new node in the pipeline as a child of the calling node. They do not modify the calling node.
Deadman
Helper function for creating an alert on low throughput, aka deadman's switch.
- Threshold – trigger alert if throughput drops below threshold in points/interval.
- Interval – how often to check the throughput.
- Expressions – optional list of expressions to also evaluate. Useful for time of day alerting.
Example:
var data = stream.from()...
// Trigger critical alert if the throughput drops below 100 points per 10s and checked every 10s.
data.deadman(100.0, 10s)
//Do normal processing of data
data....
The above is equivalent to this Example:
var data = stream.from()...
// Trigger critical alert if the throughput drops below 100 points per 10s and checked every 10s.
data.stats(10s)
.derivative('collected')
.unit(10s)
.nonNegative()
.alert()
.id('node \'stream0\' in task \'{{ .TaskName }}\'')
.message('{{ .ID }} is {{ if eq .Level "OK" }}alive{{ else }}dead{{ end }}: {{ index .Fields "collected" | printf "%0.3f" }} points/10s.')
.crit(lamdba: "collected" <= 100.0)
//Do normal processing of data
data....
The id and message alert properties can be configured globally via the 'deadman' configuration section.
Since the AlertNode is the last piece it can be further modified as normal. Example:
var data = stream.from()...
// Trigger critical alert if the throughput drops below 100 points per 1s and checked every 10s.
data.deadman(100.0, 10s).slack().channel('#dead_tasks')
//Do normal processing of data
data....
You can specify additional lambda expressions to further constrain when the deadman's switch is triggered. Example:
var data = stream.from()...
// Trigger critical alert if the throughput drops below 100 points per 10s and checked every 10s.
// Only trigger the alert if the time of day is between 8am-5pm.
data.deadman(100.0, 10s, lambda: hour("time") >= 8 AND hour("time") <= 17)
//Do normal processing of data
data....
node.deadman(threshold float64, interval time.Duration, expr ...tick.Node)
Returns: AlertNode
Stats
Create a new stream of data that contains the internal statistics of the node. The interval represents how often to emit the statistics based on real time. This means the interval time is independent of the times of the data points the source node is receiving.
node.stats(interval time.Duration)
Returns: StatsNode