...
opReports works almost completely "out of the box" and requires just a very few configuration settings to be adjusted initially:
Linking to NMIS
Many reports contain clickable links to NMIS, which require that the setting for nmis_host_base
is correct. It is also important that the configuration setting opreports_url_base
is correct, or your report will display badly. These are set in /usr/local/omk/conf/opCommon.nmis
; see the next item for details on how to modify this file safely.
The nmis_host_base configuration is required to make sure that graphs and other linked things can find the server correctly from a report which has been emailed.
Code Block |
---|
'nmis_host_base' => 'http://nmis.yourcompany.com',
'opreports_url_base' => 'http://nmis.yourcompany.com', |
Emailing Reports
If you plan to email reports out (via the CLI tool or the GUI), then it's vital that the email configuration is adjusted to reflect your environment.Open /usr/local/omk/conf/opCommon.nmis
with an editor of your choice, look for the section labelled "email
" and change the values as required.
When you're done making these adjustments, restart the Opmantek Web service with
sudo service omkd restart
.
Configuring the Scheduler for Frequent Reporting
If you want to run scheduled reports very frequently, then the default frequency for the opReports scheduler may be insufficient.
By default opReports installs a cron file (in /etc/cron.d/opreports
) which runs opreports-scheduler.pl once per hour. Feel free to modify that cron file to your liking.