NetXMS Support Forum

Hi Victor,

Please, see here: https://netxms.org/documentation/nxsl-latest/#func-right
It says:  [color=rgba(0, 0, 0, 0.6)]This function is deprecated starting from version 5.0.[/color][color=rgba(0, 0, 0, 0.6)] Please use [/color]String::right()

Regards,

Leo

Thank you, Filipp, for your quick reply. After another turn of script corrections they seem to be working now.
It is unfortunate that documentation has not been updated. And compilation diagnostics has not been updated too. We wasted quite a few hours because of that. And, as compilation does not catch deprecated code, we cannot be sure we have not missed some places which can fail on execution.

Regards,

Leo

Hi,

We've upgraded our NetXMS installation from 4.5.0 to 5.0.2. Then we had to replace all deprecated functions in our EPP scripts. Now EPP scripts are being compiled successfully.
However, actual execution generates an error - Script (EPP::1) execution error: Script load failed
When we try to Execute Script on a node, even simple
String::right("Test", 2);
gives the following error: 
Cannot execute script: Script compilation error (Error 16 in line 1:Requested module not found or cannot be loaded)

Any recommendations on how to fix the issue?

Thank you,

Leo

Thank you, Filipp!

Hi Filipp,

Thank yo for your prompt reply. For example, let's take the Security log Event ID 4624 (An account was successfully logged on). To check if the logged in account is an intruder, the following fields are needed:

Subject: Account Name; Account Domain
Logon Information: Logon Type; Virtual Account; Elevated Token
New Logon: Account Name; Account Domain
Network Information: Workstation Name; Source Network Address


Some of these fields should be used in the matching regular expression to select just a subset of 4624 events, some are required for future event processing to make the final decision if it an intrusion, a suspicious activity, or a legitimate usage scenario.
I would argue that using a regular expression against well-structured XML is a much better way to extract all the information than processing formatted text of the message.

When you say that it could be possible to pass XML as a parameter of generated events, does it mean that there is a way to do that in the current implementation. If yes, how it can be done? It can be useful for in-depth analysis of some events.

Thank you,

Leo

Hi,

Windows Event Log Record Details windows shows XML representation of a logged event in the Details tab. Is there any way to parse the XML representation, not just the Message field?

Thank you,

Leo

OK, I think I figured it out. There is no direct way to start Action, we have to use PostEvent. Correct?

Hi,

I'd like to have different notification levels for same events. For example, for "NODE DOWN", SMS should be send for the router node, direct email to system administrators should be sent for a critical server node, email to our ticketing system for a not-so-important server node. The same for other events. Can it be done by NXSL action script? I am quite sure it is not a problem to get information about the event source, but I cannot find any way to fire an action from the script (to send email, for example)... Is it possible?

Thank you,
Leo