User Tools

Site Tools


products:promonitor:latest:installguide:installredpeaks

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
products:promonitor:latest:installguide:installredpeaks [2026/02/11 18:32] – [Migrate from 6.8 to 7.0] jtbeduchaudproducts:promonitor:latest:installguide:installredpeaks [2026/02/20 17:43] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== Install Redpeaks on Linux ======
 +
 +===== Installation prerequisites =====
 +
 +  * Install JAVA openjdk, **required version is V21 minimum.**
 +
 +  * **No ''/opt/Redpeaks'' folder must exist, otherwise the install script will not install the application**
 +
 + 
 +===== Install or Upgrade Redpeaks using Shell Script =====
 +
 +==== Install Redpeaks ====
 +
 +  * Download the TarGZ file on the server. As root user, un-compress the archive in /home/[loggued user] **DO NOT USE /OPT TO UNTAR !**:
 +    * ''tar -zxvf [ARCHIVE FILE NAME]''
 +  * Then, run installation script as root, wait for the installation to be finished in /opt (default setting)
 +    * ''./install.sh''
 +  * Start Redpeaks with systemctl\\
 +    * ''systemctl start redpeaks''
 +
 +==== Update Redpeaks ====
 +
 +  * Perform a configuration snapshot (recommended)
 +  * Stop the service: ''systemctl stop redpeaks''
 +  * Download the TarGZ file on the server. As root user, un-compress the archive in the /home/[loggued user] directory : **DO NOT USE /OPT TO UNTAR !**
 +    * ''tar -zxvf [ARCHIVE FILE NAME]''
 +  * Then, run update script as root, wait for the update to be finished in /opt (default setting):
 +    * ''./update.sh''
 +  * Start Redpeaks with systemctl\\
 +  * ''systemctl start redpeaks''
 +
 +==== Open the application ====
 +  * Once the service is started, visit http://localhost:8888 to access the application
 +  * Default credentials
 +    * User: admin
 +    * Password: admin
 +
 +==== Default ports ====
 +
 +  * By defaults Redpeaks servers listens on 8888 for HTTP and 8443 for HTTPS
 +  * You can change those ports in the ''/opt/Redpeaks/bin/setenv.sh''
 +    * -Dport.http.nonssl=8888
 +    * -Dport.http.ssl=8443
 +
 +==== Application memory ====
 +  * You can modify dedicated application heap memory from ''setenv.sh'' file
 +  * Set the **Xmx** parameter using a ''sed'' command as such:
 +    * ''sed -i 's/Xmx2048/Xmx4096/g' setenv.sh''
 + 
 +==== Firewall ====
 +
 +To be able to configure and use Redpeaks, the admin port (by default 8888) should be open
 +
 + * Check if Network Firewall is enabled
 +    * On CENTOS or REDHAT
 +      *'' systemctl status firewalld  ''
 +
 +{{.:pasted:20190107-140523.png}}
 +
 +If the state is Active and Loaded, this means that it has been started
 +
 +  * Other Linux
 +        *  ''sudo iptables -L''
 +        * This will shows the firewall rules, check if rules are applied to the different chains. Please see the Firewall Section below
 +
 +  * On REDHAT / CENTOS 7 
 +  * Use the following command to open port 8888 and reload configuration
 +    * ''sudo firewall-cmd --zone=public --add-port=8888/tcp --permanent''
 +    * ''sudo firewall-cmd  --reload''
 +
 +  * Other Linux
 +  * Use the following command to open port 8888
 +    * ''sudo iptables -I INPUT -p tcp -m tcp --dport 8888 -j ACCEPT''
 +    * ''sudo service iptables save''
 +
 +===== Redpeaks life cycle =====
 +  * To start, stop or restart Redpeaks, it is recommended to use its service controls directly.
 +    * ''systemctl start/stop redpeaks''
 +  * A restart can also be triggered from the Settings->Admin menu->Maintenance
 +
 +===== Proxy settings =====
 +  * To use a proxy for outgoing HTTP and HTTPS connections, edit **bin/setenv.sh** file from redpeaks server
 +  * Add to the JAVA_OPTS variable the following parameters:
 +    * **-Dhttps.proxyPort=<HTTPS proxy port>** and **-Dhttps.proxyHost=<HTTPS proxy host>**
 +    * **-Dhttp.proxyPort=<HTTP proxy port>** and **-Dhttp.proxyHost=<HTTP proxy host>**
 +
 +====== UNINSTALL Redpeaks ======
 +  * Stop redpeaks service: ''systemctl stop redpeaks''
 +  * Remove service file: ''rm /etc/systemd/system/redpeaks.service''
 +  * Remove Redpeaks application and data: ''rm -rf /opt/Redpeaks''
 +  * Remove Redpeaks user and group
 +
 +====== Migrate from 6.8 to 7.0 ======
 +  * Deploying a V7.0 base version over a V6.8 can only be done from Linux shell.
 +  * Java **OpenSDK 21** is a prerequisite for using V7.0.
 +  * If you are on RHEL/Red Hat, you can upgrade Java using dnf ''sudo dnf install -y java-21-openjdk'' 
 +  * If you are on Debian/Ubuntu (or any non-RHEL distro), use the provided ./install_java.sh script to upgrade Java (internet access required)
 +  * If you updated java, make sure you switched the JVM using ''alternatives --config java''
 +
 +
 +  * The Redpeaks update package provides a migration script which will do the following:
 +    * Install a new instance of redpeaks, aside from Pro.Monitor.
 +    * Migrate pre-existing artefacts such as keystore, reports, drivers and snapshots to the new instance
 +    * Apply the latest snapshot in the new instance to recover the existing monitoring configuration
 +    * Apply any existing license
 +  * Existing plugins, integrations, agents and failover connections will continue working as before.
 +
 +  * Before executing migration script, do the following:
 +    * Perform a configuration snapshot from Snapshot menu
 +    * Restart the collector service
 +
 +
 +  * **Migration:** 
 +    * Log into the VM via SSH and run following commands:
 +
 +  systemctl stop promonitor
 +  tar zxvf Redpeaks-7.0.0_77.tar.gz
 +  ./migrate.sh
 +
 +  * Follow the instructions of the migration script
 +  * Once the new instance is online and running fine, you can remove old ''Pro.Monitor'' folders, users and services.
 +
 +**Note:** 
 +  * The update script has been tested on most Linux distributions, however, it might sometimes fail to start the service of the new instance.
 +  * If that happens, try restarting the service.
 +
 +**Reverting the migration:**
 +  * Shall you need to revert from V7.0 to V6.8, you just need to restart repdeaks service
 +
 +
 +
  
products/promonitor/latest/installguide/installredpeaks.txt · Last modified: by 127.0.0.1