Users Guide

Best Practices: Performance and Monitors | Performance Monitoring
444 OMNM 6.5.3 User Guide
monitorTargetDown Event Interval
By default, OpenManage Network Manager only creates the monitorTargetDown event every 30
minutes, even if the polling interval is shorter. This behavior is configurable. There are properties
through which you can either tell the system to always create these so-called availability events
every time it finds the target unreachable.
You can also change the time threshold for which it will create another monitorTargetDown event
if you want to have these created more or less often then once every 30 minutes in circumstances
where a polling target remains unreachable for an extended period of time.
To configure this interval, modify (or better, override) the following properties (from
.../
owareapps/performance/lib/pm.properties
)
#Monitor alarm settings
#
#pm.monitor.AlwaysReemitAlarm=true
#pm.monitor.AlarmReemitTimeout=15
Notice that these are commented out by default, so monitorTargetDown appears by 30 minute
intervals, and the default for
AlwaysReemitAlarm is false . Restart application server for edits
to take effect. In a cluster, all edits must be consistent.
64 GB RAM 50000 8 GB Synergy Web Server heap, 16
GB Application Server heap, 24 GB
Database buffer
8+ core, 400 GB+ disk
space
128 GB RAM
(recommended)
50000 12 GB Synergy Web Server heap, 24
GB Application Server heap, 48 GB
Database buffer
16+ core, 400 GB+ disk
space
Note:
• The VPN tunnel is assumed to be available to cloud services.
• The suggested target numbers are for latency under 50ms. You may have to scale down numbers of
targets when latency is greater than 50ms.
RAM Max Targets
(5 minute poll
intervals)
Heap Memory Settings Recommended CPU Cores
and Disk Space