Description of problem:

When creating a audit log record, there is an option to assign a custom id string to the record, this is use for example when dealing with interfaces where the custom id value gets the interface name in order to handle event flooding correctly.
However, the custom is value is used when generating the key for the audit log cache but since it is not persisted to the database, each record in the cache that has a non-empty custom id value will not be cleaned from the cache since the key for searching this record will have always an empty custom id value.

This behavior may lead to cache flooding and memory leak.

Version-Release number of selected component (if applicable):


How reproducible:

Internal to code, can be tested only in developer environment using the debugger.


Steps to Reproduce:
1.
2.
3.

Actual results:

custom id is not persisted to he database causing some events not to be cleared from cache


Expected results:

custom id should be persisted to the database in order that the key stored in the cache and the key generated to search the cache will have the same value.

Additional info: