<![CDATA[nxevent]]>Hello,

I'd be very usefull to enhance nxevent utility for ability to send event by using event's name (instead of event_id code).

Another not so important notes:

  • nxevent command should exit with non zero return code if sending of event was not successfull.

  • implementation of any kind of persistence (e.g. buffering of events at the sender's side) is welcomed for event sending utility to overcome situations like: short lasting server unavailability or broken network communication
      note: nxevent -w parameter seems it is not applied for this use case

And thanks for nice software.

Kind Regards,
Roman

]]>https://forum.netxms.org/topic/3182/nxeventRSS for NodeFri, 13 Nov 2026 13:10:17 GMTFri, 30 May 2014 16:01:21 GMT60<![CDATA[Reply to nxevent on Tue, 03 Jun 2014 13:08:29 GMT]]>Hi,

Thank you for quick reply 🙂 

During testing I've found following behaviour which I suppose is not correct:

During import of configuration (e.g. events), user events (id > 100000) are not correctly replaced in the case event name and/or event id already exist. Events are always appended as new ones (with new id) regardless any checkbox is selected. Also more events can have the same name as uniqueness of name is not checked (there is no constrain).

tested on 1.2.14, windows version

Kind Regards,
Roman

]]>https://forum.netxms.org/post/14050https://forum.netxms.org/post/14050Tue, 03 Jun 2014 13:08:29 GMT<![CDATA[Reply to nxevent on Mon, 02 Jun 2014 21:53:54 GMT]]>Hi!

I've implemented #1 and #2 (event identification by name and correct return codes). #3 is a bit more complicated so I'll do it later 🙂

Best regards,
Victor

]]>https://forum.netxms.org/post/14043https://forum.netxms.org/post/14043Mon, 02 Jun 2014 21:53:54 GMT