Actions do not import from .ndjson imports through API or Web Interface [Security Solution] #116363
Labels
bug
Fixes for quality problems that affect the customer experience
Team: SecuritySolution
Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
triage_needed
Describe the bug
I discovered this when trying to create rules that would automatically alert to slack on import - not sure this is the right place to report, so if it isn't please let me know.
You can add the following to a rule .toml to enable slack reporting:
Generating the rule for export via
python -m detection_rules export-rules --directory rules --outfile test_rules.ndjson
results in a valid .ndjson with valid entries that show the rule actions.But when you import the rules into either the UI using the Import button or via the API:
Then the rule actions are missing...
Even stranger, if you use the create rule API and you load the same rules one by one from the .ndjson where the actions aren't being imported, the rule actions are present and work as expected.
Kibana/Elasticsearch Stack version:
v 7.15.0
Original install method (e.g. download page, yum, from source, etc.):
Not installed - purchased through Elastic Cloud
Functional Area (e.g. Endpoint management, timelines, resolver, etc.):
Detection rules
To Reproduce
Expected behavior
When I import a rules .ndjson with rule actions, I expect the rule actions to be present on the imported rule. This is the same behavior I see when I import rules that have rule actions using the create rule API.
The text was updated successfully, but these errors were encountered: