NetXMS Support Forum

English Support => General Support => Topic started by: borisk on June 17, 2007, 10:15:32 PM

Title: ExternalParameter and proxy agent configuration (HTTPS check
Post by: borisk on June 17, 2007, 10:15:32 PM
I'm testing NetXMS in simple network consisting of Linux box running netxmsd and nxagentd and another Linux box running Web server.

Because Web server does not have NetXMS agent installed, NetXMS server is defined as poller for Web server.

I have need to check that certain URL is accessible by HTTPS. Thanks to ExternalParameter configuration option such a check is rather trivial to implement.

But I had found that when you define DCI for HTTPS service check in the context of Web server then service check does not run.

I can define all service checks using custom scripts in the context of NetXMS server, but this configuration would make ACL and alert configuration more complex to me.

Is it possible to schedule scripted checks for non-standard services as DCI for server which does not have NetXMS agen installed?
Title: ExternalParameter and proxy agent configuration (HTTPS check
Post by: Victor Kirhenshtein on June 18, 2007, 01:36:48 PM
Hello!

I see only one solution - to use push DCI. You can define DCIs on web server's node object, set their source to "Push Agent", and then on management server (or any other machine) run your custom checks by cron and use nxpush command line utility to push new values to DCIs on web server's node object.

I also have a plans to implement "internal push" operation which will allow automatic copy of values from one DCI to another, but for current release the only way is through nxpush utility.

Best regards,
Victor
Title: Re: ExternalParameter and proxy agent configuration (HTTPS check
Post by: jdl on November 08, 2010, 07:37:21 PM
Hi

Any news on this "internal push" operation?
That would be great to have a command that can be used in the NXSL script to perform similar task as with NXPUSH.

Best regards,

Jdamien
Title: Re: ExternalParameter and proxy agent configuration (HTTPS check
Post by: Victor Kirhenshtein on November 08, 2010, 07:46:21 PM
Hi!

This can be done by setting "proxy" attribute for a DCI. For example, if you need to have DCI on node A, but get information from node B, you can configure DCI on node A and set it's "proxy" attribute to node B. For security reasons, you must also add node A to list of trusted nodes for node B, or disable trusted nodes checking globally.

Best regards,
Victor