NetXMS Support Forum

You have to edit conf files if you wish to execute commands remotely via NetXMS agent. In that case you should add appropriate Action entries in agent configuration files.

Best regards,
Victor

Hello!

To run command on management server itself, you don't need to change server's configuration file. You just need to specify your executable under "Command". If you wish to run .bat or .cmd file, you may need to use form of

cmd.exe /C <your_cmd>

Executable can be located anywhere, but if it is not in system PATH, you should add full path to it when defining action.

Best regards,
Victor

Hi!

Your setup is very impressive It was a pleasure to read your post

Quote from: borislavl on January 29, 2010, 08:38:35 PM
The idea of pushing events between the servers is very good and helpful. Is there a other way to transfer values?

Not yet (except action + push mechanism you already using). I plan to add support for full-scale distributed monitoring, event forwarding is a first step in this direction.

Quote from: borislavl on January 29, 2010, 08:38:35 PM
Is the Event processing the only way of setting the Situation attributes?

Yes.

Quote from: borislavl on January 29, 2010, 08:38:35 PM
Can we for example do something like: s->status = "updated" (s - situation)?

Not yet. But it's very easy to implement, so I'll add it until next release.

Quote from: borislavl on January 29, 2010, 08:38:35 PM
Can we see the current Situation attribute state in NetXMS console?

Yes, via View -> Situation. You should see situations - instances - attributes tree.

Quote from: borislavl on January 29, 2010, 08:38:35 PM
Is there a way to change Custom Atributes?

Only manually via console, or by writing your own tool via C or Java API.

Quote from: borislavl on January 29, 2010, 08:38:35 PM
Can we send parameters to the actions?

Yes (I suppose you mean actions on agents). In action definition you can use placeholders $1, $2, etc. - they will be replaced by appropriate parameter. Parameters should be separated by space - like for calling external command. For example, you can define on agent:

Action = Test:echo $1

and on server define remote action like

Test "%n"

Of course, if security is not a concern, you can define "universal" action like this:

Action = Execute:$1 $2 $3 $4 $5 $6 $7 $8 $9

and then just use any command you want without defining additional actions, like

Execute /my_script "%n" "%m"

Quote from: borislavl on January 29, 2010, 08:38:35 PM
Can we write DCI value to a file (using actions)?

Yes. You can call action with a parameter with macro expansion using NXSL, and access DCI data for current node as usual.

Best regards,
Victor

See https://www.netxms.org/forum/index.php/topic,832.0.html

Hello!

Unfortunatelly, answers to all questions is "no". However, they all looks useful, so I will add them to feature request list.

Best regards,
Victor

Hi!

For example, we want to send email for every critical event in Windows "Application" event log. To achieve that, we should:

1. Create new event in NetXMS (via Control Panel -> Events). Remember ID assigned to new event. For example, let's call our new event EVENTLOG_ERROR and assume that ID 100001 was assigned to it. Set message template to

ERROR: %1

2. Create parser configuration file. To generate event with code 100001 on each error message it will looks like following:

<parser>
  <file>*Application</file>
  <rules>
    <rule>
      <severity>1</severity>
      <match>(.*)</match>
      <event params="1">100001</event>
    </rule>
  </rules>
</parser>

3. Configure LogWatch subagent:

in main section of nxagentd.conf:
SubAgent = logwatch.nsm

in LogWatch section:
*LogWatch
Parser = our_parser_file.xml

4. Restart agent

5. Add appropriate rule to event processing policy (send e-mail for each EVENTLOG_ERROR event)

That's all - now server should send e-mails for every error message written to application event log.

Best regards,
Victor

Hello!

You have to configure UPS subagent. Add to agent's configuration file the following:

in main section:

SubAgent = ups.nsm


at the end of file:

*UPS
Device = 1:"COM1:":APC

Replace COM1 with actual port name. If your have UPS other than APC, change communication protocol to BCMXCP or MICRODOWELL, depending on what your UPS supports. Restart agent.

After that, you'll be able to collect information about UPS. All parameters require device id, which is set to 1 in our example.

Best regards,
Victor

Hi!

First, you have to specify your requirement in more details. How status of your application can be monitored? Do you have a script or command line tool which returns current status of your application?

Best regards,
Victor

Hello!

I've fixed this problem in next release. For building 0.2.31, replace line 339 in file net.cpp (it should looks like


if (rti_info[RTAX_DST] != NULL && !(rtm->rtm_flags & RTF_WASCLONED))


) with


if (rti_info[RTAX_DST] != NULL)


Best regards,
Victor

You can download it at https://www.netxms.org/download/dev/scilexer.lib.

Best regards,
Victor

I check my setup - i have two different scilexer.lib for some reasons. One of them contains these functions (and looks like static library), other are not (and looks like import library for scilexer.dll). Check what scilexer.lib you are linking.

Best regards,
Victor

Hi!

Snapshots does not contain configure script - it is created as part of distribution preparation. In the root of NetXMS source tree there are script called reconf which will create configure - but you must have autoconf, automake, and libtool installed.

Best regards,
Victor

Hi!

What version of Scintilla library you are using? Class PropSet defined in PropSet.h from Scintilla library. I use version 1.67, which probably outdated - may be this is the problem.

Best regards,
Victor

A kakoj u faila pravil'nij timestamp? Ne zabivajte, chto eti parametri vozvraschajut UNIX timestamp, t.e. kolichestvo sekund s 1 Jan 1970 00:00:00 UTC. Esli nado perevesti v drugoj format, to eto mozno sdelat' cherez transformation script dlja DCI.

Currently we don't have blackberry device for testing, and I have no idea how hard development for blackberry could be. It's not very popular in my country, so I just forgot to include it in the list. However, I'll add blackberry to the list to see how big is demand for blackberry client.

Best regards,
Victor