-
Notifications
You must be signed in to change notification settings - Fork 50
Closed
Description
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:
- Go to 'Data processing'
- Click on 'Azure'
- Edit the default filter and copy its content
- Add a new filter and paste the previously copied content
- Change the dataType to azure-test to see it in the filter file
- 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
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
Type
Projects
Status
✅ Done