NetXMS Support Forum

Hi!

Quote from: borislavl on March 17, 2010, 09:07:06 PM
1. Export for the NetXMS actions, event processing rules and script library

Agree.

Quote from: borislavl on March 17, 2010, 09:07:06 PM
2. Or backup of the entire server configuration

In fact, you can do this by backing up database or exporting it using nxdbmgr. If you wish to backup only server configuration without collected data, you can just skip idata_xx, event_log, alarms, snmp_trap_log, and audit_log tables.

Quote from: borislavl on March 17, 2010, 09:07:06 PM
3. Actions to be able to return a value(response from the command) to a specified DCI.

How this is different from DCI with external parameter as a source?

Quote from: borislavl on March 17, 2010, 09:07:06 PM
4. Or to call action from NXSL and receive/not receive value as response

I'm not sure that this is needed in DCI transformation and event filtering scripts. Main concern here is performance - for example, if event filtering script calls external action and waits for it's completion, it potentially could block event processing for significant amount of time.

Quote from: borislavl on March 17, 2010, 09:07:06 PM
5. From NXSL to be possible to set DCI values (activating their Thresholds as configured)

Could be implemented, but probably for "push" DCIs only (I mean allow to set value only for push DCIs).

Quote from: borislavl on March 17, 2010, 09:07:06 PM
6. Updated version for the DRBD subagent

This is one of priority changes - we have support request for this, so it should be ready soon.

Best regards,
Victor

I kak vigljadit konfig agenta?

A est' vozmoznost' proverit' bez ECS subagenta?

Ochen' stranno. Ja proveril na svoem testovom NetWare 6.5 - vrode rabotaet. A kakaja versija NetWare?

Vrode ispravil. Poprobujte postavit' agenta iz prilozennogo arhiva.

Yes, you can use 1.0.0-rc2 - so far only few minor issues was reported, and most likely it will become 1.0.0 release with only minor fixes.

Best regards,
Victor

Hello!

What database you are using? Also, when starting netxmsd after nxdbmgr -X, what is in netxmsd log?

Best regards,
Victor

Hi!

Do you use FreeTDS ODBC driver for connecting to MS SQL server? It has known problem with UCS-2 encoding, which is used by NetXMS by default. Try to add the following line to your netxmsd.conf:


DBDrvParams = unicode=false


Best regards,
Victor

Hello!

I've fixed that. You can try to install 1.1.0-rc11 - https://www.netxms.org/download/agent_packages/nxagent-1.1.0-rc11-x64.exe.

Best regards,
Victor

Yes, it will work under WINE.

GUI pod Linux poka net. Mi sejchas pishem novij portabel'nij GUI (ja cherez neskol'ko dnej vilozu preview), no projdet nekotoroe vremja, poka pojavjatsja vse funkcii starogo GUI. Nineshnij GUI napisan pod Windows s ispol'zovaniem MFC, tak chto sportit' ego vrjad-li udastsja. On rabotaet pod WINE, no eto konechno ne sovsem to.

A parametr Disk.Total(D:) sobiraetsja?

There are currently no management console for Linux. We are working on new portable management console (I'll publish a preview in a few days), but it will take some time until all functionality of existing Widnows console will be implemented.

Best regards,
Victor

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