[🐛 Bug]: Service Topology screen does not show related alerts

[YoannD42]

Hello,

I have a mapping rule, that picked "service", or "environment" from incoming alert, and enrich alerts, from my service topology.

From the logs, it looks like it is working, and alerts are effectively enriched :

[2025-04-02T09:03:06.249611] Running mapping rules for incoming alert
[2025-04-02T09:03:06.251131] Checking alert against mapping rule
[2025-04-02T09:03:06.251473] Alert matched a mapping rule for matcher: ['service', 'environment']
[2025-04-02T09:03:06.251702] Alert matched a mapping rule, enriching...
[2025-04-02T09:03:06.826131] Alert enriched

However, in the Service Topology Map, I don't see the alerts listed (cf screenshot). While, from the alert, I see indeed the service well discovered.

Alert :

If I look at service topology doc, it used to have dots, with the number of alerts next to each https://docs.keephq.dev/overview/servicetopology

[dosubot[bot]]

The issue you're experiencing, where enriched alerts are not appearing in the Service Topology Map, could be related to the configuration or the criteria used by the Topology Processor in Keep. Here are a few things to check:

1. Topology Processor Activation: Ensure that the Topology Processor is enabled. This can be done by setting the environment variable KEEP_TOPOLOGY_PROCESSOR=true. Without this, the processor won't correlate alerts with the topology data.

2. Processor Interval and Look-back Window: Check the settings for KEEP_TOPOLOGY_PROCESSOR_INTERVAL and KEEP_TOPOLOGY_PROCESSOR_LOOK_BACK_WINDOW. These define how often the processor runs and the time window it considers for correlating alerts. Make sure these are set appropriately to capture the alerts you expect to see.

3. Service Association: Verify that the enriched alerts are correctly associated with services present in your topology data. The Topology Processor only considers alerts linked to services defined in the topology.

4. Logs and Debugging: Review the logs for any errors or warnings that might indicate why the alerts are not being displayed. The logs you provided show that the alerts are being enriched, but there might be additional logs related to the topology processing that could provide more insights.

5. Documentation Review: Double-check the documentation for any additional configuration settings or known issues that might affect the visibility of alerts in the Service Topology Map.

By ensuring these configurations are correct, you should be able to resolve the issue with alerts not appearing in the Service Topology Map.

To continue talking to Dosu, mention @dosu.

---

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

[YoannD42]

@talboren This issue occurs again, for a few versions. Testing now with release 0.47.0.