Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Victor Kirhenshtein

#2386
General Support / Re: interface id on state change
September 28, 2016, 05:46:25 PM
Hi,

You can use custom attribute or comment field on interface. The only trick here is that event source is a node, not an interface. To access custom attribute (or comment) of an interface for interface event you can use the following script:


iface = GetInterfaceObject($node, $5);
return iface->comments;
// For custom attribute replace with
// return GetCustomAttribute(iface, "attribute_name");


You can create such script in script library and then use %[script_name] macro in your messages.

Best regards,
Victor
#2387
You can add any DCI value to map link. Right click on map link, go to properties, and add DCIs to show on "data sources" page.

Best regards,
Victor
#2388
General Support / Re: Performance Graphs
September 28, 2016, 05:34:13 PM
There is "Performance" tab in node properties - those are selected DCIs for selected node. This is probably what you are talking about. But you can open "Last values" tab for node, select any DCI, and open graph for it (by double click or from context menu). On that graph you can add additional data sources as described earlier.

Best regards,
Victor
#2389
General Support / Re: View OID subtree in NetXMS??
September 28, 2016, 05:31:52 PM
I suppose currently it's not possible with tables - you need something like "diff" for table row but table thresholds operates only on current table value. You can try to use instance discovery - it will create DCI for each OID, and then you can use diff threshold to detect individual OID value change.

Best regards,
Victor
#2390
Yes, currently diff threshold ignores number of samples. I can make a patch for this (and I'll include this change into next release).

Best regards,
Victor
#2391
General Support / Re: sms driver websms.ru
September 26, 2016, 12:38:15 PM
Hi,

it looks like another HTTP/JSON API - should be fairly easy to create driver from existing one. I can try to build one in next few days (please remind me if I forgot :) ).

Best regards,
Victor
#2392
Hi,

usually there is $object global variable when relevant.

Best regards,
Victor
#2393
Hi,

you need C++ compiler to build NetXMS agent. Try to install one.

Best regards,
Victor
#2394
Hi,

just try to follow instruction from configure and run it as

ACCEPT_INFERIOR_RM_PROGRAM=yes ./configure --with-agent

Best regards,
Victor
#2395
Hi,

I got similar requests from other users too. I'm currently considering adding "exclude from topology" option for nodes - then all topology functionality will be turned off, but node will be checked in status and conf poll using primary name and data collection will work.

Best regards,
Victor
#2396
Hi,

could it be that you have DCI marked as "used for status calculation"?

Best regards,
Victor
#2397
Hi,

currently you can use nxpush tool (from client package) to push data to server.

Best regards,
Victor
#2398
General Support / Re: DCI checks over SSH
September 08, 2016, 11:17:34 AM
For using SSH.Command parameter you only need to build agent. Version 2.1 will also include new data source "SSH" which will simplify configuration.

First release in 2.1 branch - 2.1-M1 - will be available in few days.

Best regards,
Victor
#2399
So basically you need some "exclude from network topology" option for the node (we have it already for interfaces). I think it won't be that hard to implement, I'll try to make it in 2.1. I've registered it as feature request - https://dev.raden.solutions/issues/1287.

Best regards,
Victor
#2400
General Support / Re: How to setup webproxy for NetXMS
September 08, 2016, 08:54:59 AM
Hi,

for geo maps you have to configure proxy in console settings (File -> Preferences -> HTTP Proxy).

What subagent you are using for HTTP service check? If you are using netsvc, which is built on libcurl, you can set environment variable http_proxy. Format description from libcurl manual:

The proxy environment variable contents should be in the format "[protocol://][user:password@]machine[:port]". Where the protocol:// part is simply ignored if present (so http://proxy and bluerk://proxy will do the same) and the optional port number specifies on which port the proxy operates on the host. If not specified, the internal default port number will be used and that is most likely *not* the one you would like it to be.

Best regards,
Victor