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

Topics - raindrop

#1
General Support / remote proxy broken internet
January 23, 2024, 01:03:47 PM
Hi All

Now have I got this wrong. You have a remote proxy server on a remote LAN and agents connecting to this proxy, and the proxy is on a tunnel to the XMS server.

If the internet goes down on either side, I was on the understanding that agent data will be held on the proxy till the xms server makes a call for info.

At present if the internet goes down esp at the xms server side we get node down messages for all remote nodes/agents from the different LANs with different tunnel proxies like the xms server is constantly pulling in.

andy

#2
General Support / emailing action variables
December 15, 2023, 01:17:20 PM
Hi,

I am hoping that someone can point me in the right direction with my query.  I have been searching both the forums and google, but so far not come up with an answer.

I am very new to NetXMS and still learning my way around it.

What I am hoping to achieve is that when an Alarm is triggered, an email gets sent to me with details about the alarm. I have managed to get quite a lot of information on the email based on the "macros for event processing" (https://www.netxms.org/documentation/adminguide/event-processing.html#macros-for-event-processing), however what I would like is to be able to include the Container Path of where the object is.

e.g. Under Infrastructure Services I have 3 containers:-

Company A
Company B
Company C

within each company I then have sub-containers called "Servers", "Workstation", "Switches", "Routers" etc.

If a server in Company B triggered a NODE_DOWN alarm, the email would include "Company B > Servers > Server Name".

I can get the Server Name using %n  but I cannot seem to find how I could get the container names.


I hope I have explained clearly what I want, and also that someone can point me in the right direction.

Thank you,
Phil