NetXMS Support Forum

Please login or register.

Login with username, password and session length
Pages: [1] 2 3 ... 10
 on: August 20, 2019, 07:21:23 pm 
Started by paul - Last post by paul
Thanks for the feedback - appreciated.

Memory I can add - will go to 24GB and see if noticeable difference. Being windows, shared buffers tops out at 512MB I believe(Windows limit), and to use effective_cache_size instead.

Found that exclusions for ativir were not working - getting them fixed to leave postgres folders alone!!

As we are SAN based flash, it is fast, but not local, so will leave the commit and WAL settings where they are for the moment.

Plugged in 24GB and 2 more cores and got the following. Confirms effective_cache vs shared buffers for windows. Will see how these go.

# DB Version: 9.6
# OS Type: windows
# DB Type: oltp
# Total Memory (RAM): 24 GB
# CPUs num: 8
# Data Storage: san

max_connections = 300
shared_buffers = 512MB
effective_cache_size = 18GB
maintenance_work_mem = 1536MB
checkpoint_completion_target = 0.9
wal_buffers = 16MB
default_statistics_target = 100
random_page_cost = 1.1
work_mem = 6844kB
min_wal_size = 2GB
max_wal_size = 4GB
max_worker_processes = 8
max_parallel_workers_per_gather = 4

 on: August 20, 2019, 04:30:24 pm 
Started by Akira - Last post by Akira

 on: August 20, 2019, 04:23:43 pm 
Started by itreydxb - Last post by huskybob

is there a generic bandwidth monitoring template for the netxms client?

any help appreciated  :D

 on: August 20, 2019, 04:21:24 pm 
Started by itreydxb - Last post by huskybob
Victor Kirhenshtein thank you for your reply

please find the configuration for the DCI Template called " DataUsage "

the daily count the daily or monthly traffic:

1) Create one DCI to collect the delta "in" on the interface (Step1-A-B)
2) Create a DCI to sum the daily consumption (Step2-A-B-C)
3) Create a DCI to sum the monthly consumption (Step3-A-B-C)

Same story for the "out" counter.

 on: August 20, 2019, 04:00:30 pm 
Started by clifford - Last post by Victor Kirhenshtein

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,

 on: August 20, 2019, 03:57:32 pm 
Started by jermudgeon - Last post by Victor Kirhenshtein
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,

 on: August 20, 2019, 03:54:50 pm 
Started by itreydxb - Last post by Victor Kirhenshtein

you have to provide actual configuration for those DCIs and information about node you are collecting them from - otherwise it's hard to tell what goes wrong.

Best regards,

 on: August 20, 2019, 02:31:32 pm 
Started by paul - Last post by paul
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.

 on: August 20, 2019, 02:06:26 pm 
Started by ntnam - Last post by ntnam
Yes. Thanks you very much.

 on: August 20, 2019, 01:05:50 pm 
Started by ntnam - Last post by Victor Kirhenshtein

interface alias is not passed to SYS_IF_DOWN. You can create script in script library called GetInterfaceAlias with the following code:
Code: [Select]
return GetInterfaceObject($node, $event->parameters[5])->alias;

and then use macro %[GetInterfaceAlias] in message text.

Best regards,

Pages: [1] 2 3 ... 10