Withdraw of the 6.9.2 Release
Unfortunately, due to critical issues identified with version 6.9.2, we have decided to remove it and ensure it's no longer available for download. These issues impacted the ability to install or upgrade but none were security-related. We are diligently working to resolve these issues and are planning to release an updated version 6.9.3 in early May.
What if you've already upgraded?For customers who have already upgraded to 6.9.2, no immediate action is required, as none of these issues are security-related. Once it's available, you will still be able to upgrade to 6.9.3 as normal. We appreciate your patience and trust as we continue to enhance our software to better serve you. Thank you for your understanding.
Component DEBUG logs
Most of the micro-services Opsview uses can be put into debug mode.
Using the Scheduler as an example, as the root user edit the file /opt/opsview/scheduler/etc/scheduler.yaml
; within the file you will see these lines:
logging:
loggers:
opsview:
level: NOTICE
Keeping the indentation the same (do not use tab characters, only spaces), change NOTICE
to DEBUG
, save the file. Now restart the service by running
/opt/opsview/watchdog/bin/opsview-monit restart opsview-scheduler
All the debug messages will be logged in /var/log/opsview/opsview.log
.
A list of all the micro-services can be found at Distributing Functionality
Note
Runningopsview-deploy
at this point will reset the logging back to defaults on all components on all servers.