With a large config, the configuration diff when selecting "Mark as Ignored" is blank

[racompton]

We are using a large config.yaml file for Artemis. It has over 12K lines. When we view an alert and select "Mark as Ignored" the "Configuration diff (Learn new rule" window that comes up is blank. See screenshot.

[vkotronis]

Could you please clarify what type of alert are you using to learn? E.g., 'E|0|...'. Also please check if there are updates associated with it in the underlying table.

[vkotronis]

Also I assume that this is related to the renderer on the frontend (the backend does not have issues handling such configs), have you tried adding the rule and checking the diff post-change in the config comparison section?

[racompton]

The alert type is E|1|-|-
There are numerous "Related BGP Updates" at the bottom of the page for these alerts.
I do not see the post-change config being updated.

[vkotronis]

OK. I will try to replicate in current frontend and will notify also when a new react-based frontend that is currently under work and in the integration stage is in for further testing. Will need to find out if it is a renderer or a backend issue or a combination of both.

[vkotronis]

Replicated locally. Seems to be not a renderer issue but a problem with the configuration microservice timeout due to the size of the config (it takes time to respond and in the meanwhile the JS library times out). Since this is related to the general way we handle the config file in the on-premise setup, and we will do a total revamping of this for speed and scale, I will add it to the enterprise SaaS requirements we are working on for collecting and managing the BGP data needed to keep ARTEMIS ground truth correct and up-to-date (incl. learning from hijack events and from other sources, like the local network).

[vkotronis]

leaving open since it also applies to the new frontend. Will be solved in a SaaS version due to the scale of the config file.