Child pages
  • opTrend Installation Guide

Versions Compared


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


Installation Steps

As of February 2016, opCharts is distributed in a self-extracting download format that simplifies the installation process quite a bit. More information on running the installer can be found HERE: The Opmantek Installer

Transfer the opTrend installer file onto the server in question, either by direct download from the Opmantek website, or from your desktop with scp or sftp or a similar file transfer tool.

  • Start the interactive installer and follow its instructions:

    Code Block
    sudo sh ./
    opTrend (3.0.7) Installation script
    This installer will install opTrend into /usr/local/omk.
    To select a different installation location please rerun the
    installer with the -t option.

  • The installer will interactively guide you through the steps of installing opTrend. Please make sure to read the on-screen prompts carefully.
  • When the installer finishes, opTrend is installed into /usr/local/omk, and the default configuration files are in /usr/local/omk/conf, ready for your initial config adjustments.
  • A detailed log of the installation process is saved as /usr/local/omk/install.log, and subsequent upgrades or installations of other Opmantek products will add to that logfile.
  • For detailed information about the interactive installer please check the Opmantek Installer page.

Post Installation Steps

  1. The opTrend installer will create cron entries to keep the opTrend database up-to-date but an initial "update" is required to prime the database for the current week. Run the following command to do this: 

    Code Block
    /usr/local/omk/bin/ act=update

  2. The wiredTiger storageEngine is suggested for opTrend to improve performance.

  3. The opTrend installer will attempt to "cap" the "seds" collection to limit the database size somewhat (asking first).  This only happens if the wiredTiger storageEngine setting is set because not all versions of Mongo support collection updates that opTrend requires.  The "seds_ev" and "ev_billboard" collections are not capped.  Capping can be done post-install by running act=setup-db

  4. History can be created if your NMIS installation has the data, to do this run the updates for the weeks you have.  I suggest doing this oldest to newest so that the Billboard information can be calculated correctly: 

    Code Block
    /usr/local/omk/bin/ act=update date="4 weeks ago" force_end_of_week=1 force=1
    /usr/local/omk/bin/ act=update date="3 weeks ago" force_end_of_week=1 force=1
    /usr/local/omk/bin/ act=update date="2 weeks ago" force_end_of_week=1 force=1
    /usr/local/omk/bin/ act=update date="1 week ago" force_end_of_week=1 force=1

Post Installation Upgrade Steps

  1. New datasets have been introduced that the GUI will not show unless the config is updated, update opConfigopCommon.nmis with this setting:

    Code Block
    'optrend_topn_sections' => [ {"Node Health" => [{ 'cpuLoad' =>'cpu' }, { 'MemoryUtil' =>'memory' },{ 'tcpCurrEstab' => 'tcp'},{'hrSystemProcesses' => 'processes'} ]}, {'Interface Trend' => [{ 'ifInUtil' =>'interface' }, { 'ifOutUtil' =>'interface' },{ 'ifInErrors' =>'packets' },{ 'ifOutErrors' =>'packets' },{ 'ifInDiscards' =>'packets' },{ 'ifOutDiscards' =>'packets' }]}],

  2. You may also want to set the control settings to: 'optrend_exceptions_to_make_condition' => 3,