Hi, you can execute two actions for sending emails - one immediately, and one with specific timer and key (set to delay when you want your reminder). With SYS_NODE_UP event you can cancel that timer. If SYS_NODE_UP happens before timer expires then second email will not be sent. Best regards, Victor

Yes, NetXMS uses explicit cutoff points for dropping chunks. But please note that TimescaleDB support in 2.2.16 is quite immature - we have improved it significantly in 3.0 branch. Best regards, Victor

Having such huge values which are not an accurate reflection throws out completely the ability to use the data. Given that the "events" are not being truly processed, probably more like a bug. Would be nice to have some of these things ti be able to set as an exception, or have them report properly in the first place. As for performance - headache continues - more performance testing today, hitting our newer 600 EPM and backlog occurring. Good news though, having managed to get to 600 EPM through the Postgres settings, plus some EPP disabling, we caught up rather than triggering a bounce. I have since disabled more EPP - down to 100 active - I can get the disabled events from Event log if I really need them. Not an ideal situation - but what options do I have - EVERYTHING else has been tried On a positive note - my Network guys have agreed to stop the MAC move traps. On a negative note - they said they had done it - but traps keep coming. Will get that sorted tomorrow. Holistically speaking, Event Processor Queue needs to be a DCI item as being behind can be a calamity if a mission critical alarm was to be delayed by an hour.  Faith in NetXMS is either there or it is not. If e cannot rely on alarms showing when the event comes in - what is the point of NetXMS? If we cannot even monitor when this is happening - how can we have faith? I have an exception set for Events Processed in last minute of > 500 for last 4 polls;  indicating NetXMS "might" be under stress. Having a monitor for Event Processor Queue > 1,000 would be much, much, much better. Even nicer would be the capacity to process 1,000 events per minute AND have 200 EPP's. My friendly Network guys made their change - what a difference it made!! Fixes my immediate problem - but NetXMS still needs better way of reporting when Event Processing starts banking up. [image: MAC move effect.png]

that sums it up quite good! great stuff, thanks. with debug console i actually meant the server console from the Tools menu.

Another fantastic explanation. Thanks Victor. Most important statement: Is unreachable universal? = yes In both 2.2 and 3.0 "unreachable" means that NetXMS server cannot reach the node for any reason. Second most important: Clarity on flags - same flag different value - or separate flags: "NETWORK_PATH_PROBLEM is an additional indicator " Will look at undoing my customization at some point, though I do like my last time up and last time down custom attributes I current add

Hello Millenium7, did you get ssh script working ? I could use some examples also, how to get basic ssh commands working. Egert

has there been any change regarding the support of vmgr subagent on a windows agent?

Thank you Victor,

For device specific monitoring, unless someone already posted templates in https://www.netxms.org/forum/general-support/sharing-standard-templates-for-netxms/ (I am pretty sure there are Microtik templates in there), you will need to build your own templates (which you can then auto-apply to all your devices). Installing the MIBs in NetXMS will make that process a lot easier, as you will be able to browse the devices for the information you are looking for. Once you developed your templates and if you are willing to share them, please post them in the thread linked above to allow other users with such devices to benefit as well.

Depending on how you are using server it could be commit 3ab06f4e1c ("fixed server deadlock after action configuration import", 2019-06-19). Best regards, Victor

yes i created a DCI parameter on the node and selecting the agent as "origin" i then selected the BytesIn. When i do that, it sets it to BytesIn(*). So i did some assumption it would enumerate something. All comes down to better understand data collection and instance discovery. I'll read up further.

ah my bad indeed on the Free vs Available part. classic mistake. sorry. understood.

ahhh ok so they do come from the template orginally. I got confused by the column name being "template" and a node name showing up over there besides the actual template name used. I'll read up a bit more/again using suggested documentation. Thanks!

Changing the community name on a node inside NetXMS does not require a restart. However, adding "EnableSNMPProxy = yes" into an agent's configuration does.

Yes, it is there for some time already: https://track.radensolutions.com/issue/NX-593. Best regards, Victor

Hi, you should go to data collection configuration on the node, then edit DCI object - then you will see "Thresholds" page. You can also post some screenshots. Best regards, Victor

Hello all, I have the web management console installed on a windows server. I have setup IIS ARR to do reverse proxy w/ SSL offload to this console, but I want to restrict the web console itself to only listen to traffic from the reverse proxy server (localhost/127.0.0.1). How is it possible to do this? I tried to modify jetty.xml to set the jetty.host parameter but was unsuccessful.

Fantastic - thanks Victor. Coding style - mine is mostly a hack and slash approach to something else I have seen as an example or that I know works. Once it works, rather than go back and clean it up - more trial and error - I move onto the next highest priority task. The more I do with NetXMS, the better I will get. Between this and the runtime flag for unreachable - very, very happy person I am today

Here is the ISILON-MIB.txt and ISILON-TRAP-MIB.txt. Cheers, ISILON-MIB.txt ISILON-TRAP-MIB.txt

So server process is crashing. Please enable core dumps and either send coredump to us or get stack trace from it with gdb. You can also run netxmsd under debugger and get stack trace directly from there. Here is short instruction: https://wiki.netxms.org/wiki/Running_NetXMS_under_debugger Best regards, Victor