Skip to content

[BUG] Mutate not order filters added as spected #193

@c3s4rfred

Description

@c3s4rfred

Describe the bug
When you add a filter to an integration data processing, the filter is placed at random position of the filter file in the container, not at the top as expected

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Data processing'
  2. Click on 'Azure'
  3. Edit the default filter and copy its content
  4. Add a new filter and paste the previously copied content
  5. Change the dataType to azure-test to see it in the filter file
  6. Give a name to the filter and Save

Expected behavior
The new filter must be always at the bottom of the filter file in the pipelines/cloud_azure 111-filter.conf inside Logstash container

Screenshots
image

Environment

  • UTMStack v10

Possible solution
Order de filters using the id in the database, new filters always has bigger ids

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status

✅ Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions