Page Comparison

...

Performance Optimization

•  Timeouts: Set timeouts for service checks if available, adjust timeouts slightly to find the appropriate values (depends on type and “cost” of check, network latency and the environment). Ideally checks do not execute longer than 3-5 seconds, try a timout of 5 seconds
•  Check Intervals #1: Set check intervals wisely, don’t check everything every minute if there is not need for this (most performance issues come from unnecessary short check intervals)
•  Check Intervals #2: Slowly changing metrics can be checked with bigger intervals, e.g. HDD usage could be checked every 15-20 minutes instead of every 3 minutes
•  PIng vs. ICMP: Use check_icmp instead of check_ping, this has a big impact on the performance
•  Check only what you really need to check, adjust parameters to get the needed information with the least effort, for example don’t do check_icmp with 10 packets if you just want to check if a connection is up, 3 packets should be enough
•  Slowly changing metrics can be checked with bigger intervals, e.g. HDD usage could be checked every 15-20 minutes instead of every 3 minutes Processes: Check http://<SONARPLEX-IP>/cgi-bin/ps.cgi to get detailed process and performance metrics, see the listing of every check with its individual execution time and latency to evaluate “evil” and “costly” service checks
•  Performance Data: Enable performance data only if needed, processing and storing of the data is costly
•  SLA: Enable SLA Processing (

  Insert excerpt
  _AdminWeb _AdminWeb nopanel true

   > Configuration > System > SLA) only if needed, the processing can produce a heavy load
•  

  Logging: Disable the logging facilities if your system runs stable. Logging has an impact on the overall I/O resources so only enable it if necessary. 

  Column
  width 600px
  Tip We have seen I/O boosts up to 20% with disabled logging, especially on azeti 600M and azeti NG.

...

Troubleshooting Distributed Monitoring

...