What this PR does / why we need it: This PR is needed because we currently cannot use both a storage policy filter and consumer service filter inside m3aggregator for a single consumer, we can only use one filter. This limits us from being able to filter on shardSet and storage policy which may be required. Here we currently register filters in a map keyed by serviceID, so if a service has more than one filter it gets overwritten.
Special notes for your reviewer: N/A
Does this PR introduce a user-facing and/or backwards incompatible change?: No
Does this PR require updating code package or user-facing documentation?: No
What this PR does / why we need it: This PR is needed because we currently cannot use both a storage policy filter and consumer service filter inside m3aggregator for a single consumer, we can only use one filter. This limits us from being able to filter on shardSet and storage policy which may be required. Here we currently register filters in a map keyed by serviceID, so if a service has more than one filter it gets overwritten.
Special notes for your reviewer: N/A
Does this PR introduce a user-facing and/or backwards incompatible change?: No Does this PR require updating code package or user-facing documentation?: No