You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Kapacitor features node outputs, in which processed data from kapacitor can be output to a certain service. Kapacitor has two types of node output implemented out of the box and ready to use: HTTPOutputNode and InfluxOutputNode. It is also possible to define custom output nodes. TICKscripts which process data and output it to a certain endpoint may or may not trigger alerts.
It would be a great feature for kapacitor-unit to test node outputs.
Test flow:
Define the test configuration (which data to load, which tick script to load, what are the output expected after the data processing)
Load tick script
Load task
Inspect output data
Compare expected data with output data
Open points
A) How to pipe data coming from an output node to inspect its contents and compare with the expected data defined in the test definition?
kapacitor-unit should be able to consume processed data coming from any type of NodeOuput, predefined or custom.
B) How would the test definition look like?
C) Add way to split configuration tests so that it's easier to manage them? (e.g. to have a test configuration for alerts and another for data processing (OutputNode) type of tests.
The text was updated successfully, but these errors were encountered:
What
Kapacitor features node outputs, in which processed data from kapacitor can be output to a certain service. Kapacitor has two types of node output implemented out of the box and ready to use: HTTPOutputNode and InfluxOutputNode. It is also possible to define custom output nodes. TICKscripts which process data and output it to a certain endpoint may or may not trigger alerts.
It would be a great feature for kapacitor-unit to test node outputs.
Test flow:
Open points
A) How to pipe data coming from an output node to inspect its contents and compare with the expected data defined in the test definition?
kapacitor-unit should be able to consume processed data coming from any type of NodeOuput, predefined or custom.
B) How would the test definition look like?
C) Add way to split configuration tests so that it's easier to manage them? (e.g. to have a test configuration for alerts and another for data processing (OutputNode) type of tests.
The text was updated successfully, but these errors were encountered: