Using message.insert on the Socket/ISM interface

[krisztian]

Hi,
I've been experimenting with using the socket interface (ISM source) to push messages into Traverse from external machines.
What I noticed though is that messages entered using the message.insert command show up fine in the Event Manager, however when I try to run a query (Custom -> Messages Report), these messages do not show up at all.
If I send a different message one that matches the rule defined in the Traverse supplied etc/messsages/ism/99_rule_ism_test.xml file it shows up in the Event Manager AND it shows up in the above mentioned query.
Is this how it was designed?

Thanks,
Krisztian

[rajib]

Krisztian,

This was indeed a bug (#65) where events inserted via "message.insert" command were not archived in the DGE database. As a result, Custom/Messages Report could not locate those events from same databases. Other events, including SNMP trap, syslog or ISM that matched a rule (ie. didn't use message.insert command) were not affected. This issue was resolved in build 4.8.088.

Thanks