Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Section
Column

Introduction

The following guides are just best practices and should help you with common tasks in a azeti SONARPLEX infrastructure. Please make small changes and monitor the performance of your device, adjust step by step. A lot of the success of optimizations depends on your configuration in detail. Make sure to test changes in a test environment first before deploying to your production system. You can use the free VAA (available on www.azeti.net) for testing.

Info

This guide relates to SONARPLEX Generation 5.

Security Optimization

  •  Agent Password: Use a strong azeti Agent Password, best is to use more than 16 letters, special chars and numbers (
    Insert excerpt
    _AdminWeb
    _AdminWeb
    nopaneltrue
     > Configuration > Network > Agent Configuration)
  •  IP Forward: Disable "IP Forwarding" (forwarding of ip packets between the network interfaces)
  •  SNMP Community: Change the default SNMP community strings, use strong strings instead of "public" (
    Insert excerpt
    _AdminWeb
    _AdminWeb
    nopaneltrue
     > Configuration > Network > SNMP Configuration
     and Configuration > System > Status Delivery Configuration for Distributed Monitoring)
  •  HTTPS: Enable HTTPS instead of unencrypted HTTP (
    Insert excerpt
    _AdminWeb
    _AdminWeb
    nopaneltrue
     > Configuration > Network > HTTP Configuration)
    , optionally change the HTTPS Port to something different than 443,444
  •  SSL Certificate: Use properly (signed by a trusted CA) signed SSL certificates instead of the default self-signed azeti certificate
  •  Passwords: Change the Administrator password and use a strong password (
    Insert excerpt
    _AdminWeb
    _AdminWeb
    nopaneltrue
     > 
    Configuration > Accounts > Administrator (admin))
  •  Accounts: Delete all unnecessary accounts or at least disable the web and admin GUI access for unprivileged users (
    Insert excerpt
    _AdminWeb
    _AdminWeb
    nopaneltrue
     > 
    Configuration > Accounts)
  •  Updates: Keep your SONARPLEX up to date, check portal.azeti.net regularly or enable Auto Updates if your SONARPLEX does have an internet connection

 

Column
width300px
Panel
bgColor#f4f4f4
borderStylesolid

On this page:

Table of Contents

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
    nopaneltrue
     > 
    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
    width600px
    Tip

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

...

Troubleshooting Distributed Monitoring

...