In this section, we offer step-by-step instructions providing you with specific guidance to successfully install the Opsview Monitor Reports software module.
It’s important that you have reviewed section [Prerequisites](🔗) to ensure that any software and hardware dependencies, along with any limitations are fully understood prior to installation.
## Package Installation
Run the following command to update your OS packages, setup Opsview Monitor repositories on your server and install opsview-deploy package:
## Installing Reports
To install Reports, you need to edit /opt/opsview/deploy/etc/user_vars.yml file and add or uncomment the following opsview_module_reporting line:
For a Fresh install, follow the instructions in the [Advanced Automated Installation](🔗) page.
If, however, you are installing Reporting on an existing system (including Virtual Appliances), run the following command as root after activating Opsview:
In either case, ensure that the optional module is included in your Opsview license.
When running the reporting-install playbook, you may be prompted for a password. If you are prompted for a password, cancel the playbook execution (Ctrl-C) and run the below command to add the reporting database password to your user_secrets.yml file:
### Note about Upgrades from 6.3 or earlier
The reporting module requires Chromium to be installed in order to render reports. As part of the installation or upgrade process, Opsview Deploy will automatically set up an EPEL (Extra Packages for Enterprise Linux) repository on all Opsview Monitor Servers to pull the chromium package down from, unless you have set the `
opsview_manage_epel_repository` flag in your `
user_vars.yml` to `
False`. In this case, you will see the following message:
To continue the installation, you must either re-enable the deploy management of the EPEL repository or manually add it yourself.
Once enabled, you should run the setup-hosts.yml playbook followed by reporting-install.yml to setup the repository and continue the Reporting Module installation.
## Importing ODW DB
Reports rely on data stored within the ODW database. You must ensure ODW imports are enabled in the UI accessible via Configuration > My System, on the 'ODW' tab.
The data will be imported at 4 minutes past every hour via the opsview user's crontab. The process can also be run manually as the opsview user with the command:
## Logging into JasperServer
Opsview can use a ‘single sign-on’ method and, as such, a correctly authenticated user with the REPORTUSER access will be created in JasperServer. If the user also has REPORTADMIN, then they will receive additional privileges, specifically ROLE_ADMINISTRATOR in JasperServer.
A user that previously had ROLE_ADMINISTRATOR privileges will still retain that role even if REPORTADMIN is removed from them since the user databases are not synchronised. In this instance, a JasperServer administrative user will have to manually remove the role if required.
## Setting up Emails
Emails are sent via the local machine (where the Reports module is installed) by default and you should verify that the current email system works.
The email server configuration is stored in the file
To set the email server up, edit the following lines in the configuration to match your required config. The below example shows off emailing from the local machine.
If you change this file, then you will need to restart JasperServer:
If you experience any issues, you should review the logs that is located in
Please note, you may need to reapply the email settings after an upgrade