Using Monaco: Handling Rule Reordering in Configurations

[anaidu]

Hi Team,

Hope you're doing well!

Monaco is effective and efficient for transferring or updating configurations. However, when it comes to configurations that require a specific rule order, such as Application Detection Rules / Service Detection Rules,  etc, be cautious. Monaco may deploy the rules in a random order rather than the one you originally set (e.g., placing rules a, b, c, and d out of sequence). I'm not sure if this issue has been addressed in the latest versions of Monaco or if it's still being worked on. Since the order of these rules is crucial for proper configuration, if anyone has encountered this and found a workaround, your suggestions would be appreciated.

Regards,

Ajay Naidu

[AntonPineiro]

Hi,

Have you try InsertAfter parameter?

Best regards

[anaidu]

Hi @AntonPineiro ,

We haven't tried this but even if we had to try this it would take time for following reason:-

1. When we have more than 30-40 rules in application detection, it would be complex to identify the config IDs and change the yaml.

What we instead did is to manually rearrange the rules on UI once onboarded as that was easy and not time consuming. Even with SaaS Upgrade this was the scenario.

Regards,

Ajay