Upgrade Steps

• Download opTrend from the Opmantek website.
  Copy the opTrend tarball to the server in question, using scp or sftp or similar. Make a record of where you put the tarball (likely root's home directory).

• Become root and unpack the tarball:

  # become root sudo sh # if the tarball was saved in a different location, adjust the following command cd /tmp ./opTrend-Linux-x86_64-1.6.2.run

• Start the interactive installer and follow its instructions

• 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. Collections in opTrend are no longer capped, each entry is set to expire after 21 days.  This value is configurable, adjust opCommon: 'optrend_seds_expire_after_seconds'

2. Set expire_at value on existing documents, be sure to change the date to a date that makes sense for you: 

   db.getCollection('seds').update( { expire_at: {$exists: false}}, { $set: { expire_at: Date("2017-06-20T01:01:01")}}, { multi: true } ); db.getCollection('seds_ev').update( { expire_at: {$exists: false}}, { $set: { expire_at: Date("2017-06-20T01:01:01")}}, { multi: true } );

3. opTrend documents for the current week need to be replaced with the newer format, to do this force an update which will replace them:

   /usr/local/omk/bin/optrend.pl act=update force=1