NetXMS Support Forum

Hi!

Quote from: jdl on March 10, 2010, 07:19:21 PM
- When creating a node, reverse lookup would be interesting. Sometimes one knows the IP but not the FQDN. If you enter an IP @ and push "resolve" you get IP @ of localhost (the one running the console) and no name.

Currently, you can enter IP address as node name, press "Resolve" to fill IP address field with same value. If node has IP address as it's name, it will be resolved via DNS or agent at first configuration poll. But yes, reverse lookup in dialog could be useful.

Quote from: jdl on March 10, 2010, 07:19:21 PM
- when defining a new event processing rule, we hav eto close the window to get asked if we want to save the story. Would be nice to have a drop down menu with options (like duplicate rule, etc...) among which "save" to save the current config if relevant (if no change then greyed out ;-)

You can use main menu Policy -> Save policy or just press Ctrl+S.

Best regards,
Victor

Hi!

In NXSL, you can use any integer value as boolean, where 0 means false and any-non-zero value means true. So, you can use errorCount attribute as boolean flag if you wish, like below:

if (dci->errorCount)
{
    // Processing if error
}
else
{
   // Processing if OK
}

You can also apply boolean logic operations to integer values, for example:

if (!dci->errorCount)
{
   // Processing if there are no errors
}


Best regards,
Victor

Hi!

I'll post updated NetXMS User Manual in a few days - it will have chapter about NXSL programming.

Best regards,
Victor

A kak vigljadit parametr Disk.Total i chto propisano v pole "instance" dlja parametra so skriptom? Problema pohoze v tom, chto formiruetsja nepravil'noe imja parametra, i FindDCIByName vozvraschaet NULL.

Hi all!

Vesrion 1.0.0-rc2 is out. It fixes some build problems found in rc1, and adds possibility to search objects by comments in Windows console.

Best regards,
Victor

Ja ispravil odin bag v configure i perepakoval 1.0.0-rc2 (https://www.netxms.org/download/netxms-1.0.0-rc2.tar.gz) - poprobujte novij variant.

Hi!

Yes, you can call library script from another library script in a same way.

I'll check script saving in MS SQL a bit later.

Best regards,
Victor

Hello!

It's very strange - there are no size limitation on scripts. What database you are using?

To call one script from another, called script must be in script library, and contain function(s) other than main(). Then in calling script you should add use statement, for example:

script in library, called my_script:


sub my_function()
{
   return "some value";
}


script in event processing policy:


use my_script;

sub main()
{
   value = my_function();
   // some further processing
}


Best regards,
Victor

Please try 1.0.0-rc2 (https://www.netxms.org/download/netxms-1.0.0-rc2.tar.gz) - this problem should be fixed.

Best regards,
Victor

It will require changes in very important part of code, and in turn will require additional tests - and I wouldn't want to do this until 1.0.0 release. However, I have added new attribute to DCI object - errorCount - which you can use to check from NXSL if given DCI had data collection error. This attribute will be 0 if last poll was completed succesfully, or > 0 if there was an error (will hold number of consecutive data collection errors).

Best regards,
Victor

Hi!

It is backslash, so

println "\"";

for example will print single quotation mark character. Maybe there are other error in your script?

Best regards,
Victor

Quote from: iwi on March 03, 2010, 11:43:02 AM
I thought I read the manual, but I only see %1-%99 events parameter numbers 1..99, but how can I determin what which number does? Is this the ID from Event Editor?

Numbered parameters are event-dependent, you can open Control Panel -> Events, open event of interest, and look at the description - for all predefined events there are list of parameters.

Best regards,
Victor

Добрый день!

Это баг в nxdbmgr. Он исправлен в 1.0.0-rc1 - попробуйте использовать nxdbmgr из новой версии.

Виктор

Problem with MySQL is already known, and I'll fix it in rc2. In the meantime, you could try to prefix ./configure with LDFLAGS=-lmysqlclient, like this:

LDFLAGS=-lmysqlclient ./configure --with-server --with-mysql

Nobody reports PostgreSQL problem so far. Could you please post config.log from failed PostgreSQL configuration?

Best regards,
Victor

Hi!

StatusPollingInterval is a global parameter, and if you reduce it, all nodes will be polled more often. Depending on number of nodes, this may cause performance problems. One possible problem is network traffic increase, other is increased CPU and database usage. But severity of both these problems depends on number of nodes.

It's strange that you don't get data collection errors on Agent.Uptime - looks like a bug, because "data collection error" threshold should fire in that case. I'll check this.

Unfortunately all possible workarounds involves local agent. You can enable watchdog for local agent to restart it automatically in case of agent's crash, but it's workaround for workaround The only good solution I see is to allow status polling interval configuration for each node - it's on my todo list for some time, but I cannot promise exact version where this feature will be implemented.

Best regards,
Victor