Deduplication rules with Amazon SQS

[DaliStabl]

I am currently working on reducing duplicate alerts emerging from SQS. Even after successfully integrating keep with SQS and being able to visualize alerts, I am still unable to add AmazonSQS as a provider to the deduplication rule. how can I fix that? I've attached screenshots.

[dosubot[bot]]

Hey @DaliStabl! I'm here to help you with any bugs, questions, or contributions. Let's tackle this deduplication issue together!

To add Amazon SQS as a provider to a deduplication rule in Keep, ensure that the provider is correctly tagged for use in deduplication rules. Keep filters providers based on the presence of the "alert" tag to determine their availability in the deduplication rule configuration interface. Here are the steps you can take:

1. Verify Provider Tags: Check that the Amazon SQS provider is tagged with "alert". This is necessary for it to appear in the provider selection dropdown for deduplication rules. You might need to update the provider configuration to include this tag.

2. Check Environment Configuration: Ensure that the KEEP_PROVIDERS environment variable is correctly set with the Amazon SQS provider details, including the necessary deduplication rule configurations.

3. Restart Keep: After making changes to the provider configuration or environment variables, restart Keep to ensure it reads the updated configurations.

If the Amazon SQS provider is correctly tagged and configured, it should appear in the provider dropdown for deduplication rules. If it still doesn't appear, double-check the configuration and tags, and ensure there are no errors in the setup.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[talboren]

Hey @DaliStabl, looks like it is a bug! It seems like SQS is not including the provider id when it's adding alerts to Keep and therefore you are not able to see the dedup rules.

I proposed the following fix for that: #3084

[talboren]

Created this issue to track it: #3085

[talboren]

@DaliStabl I pushed a small fix for that issue. Mind trying again and telling me if it worked? Inviting you to join our Slack community as well: https://slack.keephq.dev