| Table of Contents |
|---|
A while ago we enabled Custom Scripts to be run on Linux Servers. Due to your feedback, we've made some changes. Thanks!
The information displayed would include the command used as well as the result. We have This has been changed this to return only the result, so that if users receive an alarm alarming on a specific result then that information is clearly definedresult is more accurate.
- Set up your custom scripts on the Custom Scripts tab from the Manage Equipment page, on the Custom Scripts tab
- Raise an alarm if required, using the information received from the custom script
- Custom Script results can also be viewed on the Linux Server dashlet
For information about Custom Scripts, read more here...
Bug Fixes
Threshold fixes:
- CPU and Memory Thresholds for Windows Servers can now be edited once added.
- CPU and Memory Thresholds has been reinstated for All Equipment in Threshold configuration. It is no longer necessary to set up thresholds individually for each Linux server .
Information from the Services pane on the Session Manager & Windows dashlets were mis-reported on the System Health Summary Dashlet. This has now been fixed
Microsoft User Feedback was showing in the Call Records but not populating on the User Feedback page. This has now been fixed.
When reloading configuration at Machine Proxy 2 there was an intermittent issue with the heartbeat document, that caused the machine to look offline or down. This has been fixed.
The setting to raise an alarm in equipment network form did not set to true, so no alarm was raised. .
This now sets to true and an alarm is raised.
The Server Availability report was incorrectly added to Reports classic. This is now available in Reports 2.0 currently accessible for Business Partners, using the menu option named "Report - Preview".