Custom "correlation Id" for complex correlation and deduplication scenarios

[satterly]

sherif84 @sherif84 Jun 26 04:00 hi @satterly , what are your thought's on adding additional deduplication fields ? currently deduplication works on alerts with the same Environment-Event-Resource. we have use cases that some alerts we are ingesting in the system need to be deduped by additional attributes, such as a version, datacenter and other criteria . the way we plan on getting around it is by jamming these into the resource field e.g. 172.168.0.1:v2:atlanta , or v19.1:www.example.com:aws:xrm6. which works fine but it pollutes the resource fields making it unreadable . a proposal is to add a new field into the alert "customIdentifier" that empty by default but can be used for additional deduplication capability Environment-Event-Resource-CustomIdentifier and customIdentifier=v2:atlanta. just a thought i wanted to present and get your feedback on . Thanks for the effort

[satterly]

This can be solved by using a "display resource" alert attribute that is the resource you want to see in the web UI while leaving the resource used for de-duplication and correlation as it is. eg. "resource_" ?

[sherif84]

sure ,that will work