products:promonitor:latest:installguide:installredpeaks
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| products:promonitor:latest:installguide:installredpeaks [2026/02/11 18:32] – [Migrate from 6.8 to 7.0] jtbeduchaud | products: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 ''/ | ||
| + | |||
| + | |||
| + | ===== Install or Upgrade Redpeaks using Shell Script ===== | ||
| + | |||
| + | ==== Install Redpeaks ==== | ||
| + | |||
| + | * Download the TarGZ file on the server. As root user, un-compress the archive in / | ||
| + | * '' | ||
| + | * Then, run installation script as root, wait for the installation to be finished in /opt (default setting) | ||
| + | * '' | ||
| + | * Start Redpeaks with systemctl\\ | ||
| + | * '' | ||
| + | |||
| + | ==== Update Redpeaks ==== | ||
| + | |||
| + | * Perform a configuration snapshot (recommended) | ||
| + | * Stop the service: '' | ||
| + | * Download the TarGZ file on the server. As root user, un-compress the archive in the / | ||
| + | * '' | ||
| + | * Then, run update script as root, wait for the update to be finished in /opt (default setting): | ||
| + | * '' | ||
| + | * Start Redpeaks with systemctl\\ | ||
| + | * '' | ||
| + | |||
| + | ==== Open the application ==== | ||
| + | * Once the service is started, visit http:// | ||
| + | * 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 ''/ | ||
| + | * -Dport.http.nonssl=8888 | ||
| + | * -Dport.http.ssl=8443 | ||
| + | |||
| + | ==== Application memory ==== | ||
| + | * You can modify dedicated application heap memory from '' | ||
| + | * Set the **Xmx** parameter using a '' | ||
| + | * '' | ||
| + | |||
| + | ==== 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 | ||
| + | *'' | ||
| + | |||
| + | {{.: | ||
| + | |||
| + | If the state is Active and Loaded, this means that it has been started | ||
| + | |||
| + | * Other Linux | ||
| + | * '' | ||
| + | * 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 | ||
| + | * '' | ||
| + | * '' | ||
| + | |||
| + | * Other Linux | ||
| + | * Use the following command to open port 8888 | ||
| + | * '' | ||
| + | * '' | ||
| + | |||
| + | ===== Redpeaks life cycle ===== | ||
| + | * To start, stop or restart Redpeaks, it is recommended to use its service controls directly. | ||
| + | * '' | ||
| + | * A restart can also be triggered from the Settings-> | ||
| + | |||
| + | ===== Proxy settings ===== | ||
| + | * To use a proxy for outgoing HTTP and HTTPS connections, | ||
| + | * Add to the JAVA_OPTS variable the following parameters: | ||
| + | * **-Dhttps.proxyPort=< | ||
| + | * **-Dhttp.proxyPort=< | ||
| + | |||
| + | ====== UNINSTALL Redpeaks ====== | ||
| + | * Stop redpeaks service: '' | ||
| + | * Remove service file: '' | ||
| + | * Remove Redpeaks application and data: '' | ||
| + | * 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 '' | ||
| + | * If you are on Debian/ | ||
| + | * If you updated java, make sure you switched the JVM using '' | ||
| + | |||
| + | |||
| + | * 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, | ||
| + | |||
| + | * 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 | ||
| + | ./ | ||
| + | |||
| + | * Follow the instructions of the migration script | ||
| + | * Once the new instance is online and running fine, you can remove old '' | ||
| + | |||
| + | **Note: | ||
| + | * The update script has been tested on most Linux distributions, | ||
| + | * 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
