Experiment with JavaScript as a pipeline language #19351
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a prototypical implementation of JavaScript as a pipeline language. It should enable us to evaluate whether using JavaScript is generally feasible. The implementation is expected to have many rough edges and may cut corners.
How to test this:
Create a JavaScript test rule in a file called
test.js
:Upload it with httpie:
Remember the ID of the created rule, and, if you want to modify it later, upload the changed code like this:
Use the Graylog UI to assign the rule to a pipeline and then send messages with a
json
field set. You should see the additional fields set on the message./nocl Not planned as a feature right now