Application signals rules not working for traces

[hemalgadhiya]

Describe the bug
A clear and concise description of what the bug is.

In the cloudwatch agent configuration when we set the rules for application signals to drop certain metrics and traces under logs --> metrics_collected --> application_signals section, the traces are not getting filtered based on the rules. It works for metrics only. The documentation says it applies to traces_collected also implicitly

Steps to reproduce
If possible, provide a recipe for reproducing the error.

What did you expect to see?

I expect the traces also to be filtered

What did you see instead?

What version did you use?
Version: latest

What config did you use?
Config:
{ "agent": { "debug": true }, "traces": { "traces_collected": { "application_signals": { "rules": [] } } }, "logs": { "metrics_collected": { "application_signals": { "rules": [ { "rule_name": "rule_1", "selectors": [ { "dimension": "RemoteService", "match": "169.254.170.2" }, { "dimension": "Service", "match": "*" }, { "dimension": "RemoteOperation", "match": "*" } ], "action": "drop" } ] } } } }

Environment
OS: (e.g., "Ubuntu 20.04")

Additional context
Add any other context about the problem here.

[agarakan]

Can you please include your Logs with debug enabled for us to investigate?

[hemalgadhiya]

I won't be able to provide the logs because of the sensitivity of the information in logs. Ideally when I provide drop rules in cloudwatch config for application signal under metrics_collected I expect the them to work for both metrics and traces as per documentation. It only works for metrics, traces are not getting dropped. I also tried to put the drop rules under traces_collected section of the config but that also doesn't work