![]() You can now install, configure, and update opsview-results-exporter with opsview-deploy.The Monitoring Collectors page has been replaced by the Collector Management page, which has been updated to ensure that all elements are aligned and styled consistently throughout the user interface.The updated packages should have the specific versions: On Centos, OL, and RHEL systems: curl -sLo- | sudo bash -s -A repo & sudo yum makecache & sudo yum install -y opsview-deploy & sudo /opt/opsview/deploy/bin/opsview-deploy /opt/opsview/deploy/lib/playbooks/orchestrator-install.yml.On Ubuntu and Debian systems: curl -sLo- | sudo bash -s -A repo & sudo apt update & sudo apt install -y opsview-deploy & sudo /opt/opsview/deploy/bin/opsview-deploy /opt/opsview/deploy/lib/playbooks/orchestrator-install.yml.To fix this, make sure that you have the latest relevant 6.8.6 packages and configuration on your orchestrator system as follows: There is a known issue that can cause Remote Collectors to fail to register with the error message Failed to install Opsview Deploy. For more information, see the Remote Collector Management documentation.This command downloads and installs the Opsview software and registers the collector with the Orchestrator. Collectors can now be installed and registered using a single command, which makes the process much easier. ![]() You can conveniently view the upgrade progress in the UI, with upgrade activities also logged and displayed.Remote Collectors can be upgraded to later versions directly from the user interface, without the need for command-line access (CLI). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |