promoteQueueData should not be stored on the events table.

On a customer site, I saw that this event became the most popular one on the event table, taking the first position of the event histogram.

This event has more than the 50% of the events stored on the DB, where the event table has more than 4 millions of events.

This can make the DB actually slow, because the auto_vacuum feature doesn't work well with a storm of write operations, and this event can cause an event storm if the user is trying to generate lots of graphs, which BTW is the case.

The solution is to change the logMessage's destination from logonly to donotpersist.