This sprint we've been working on fixing a few bugs as well as a few other things in the back end of the product to improve data collection and screen responses.
| Table of Contents |
|---|
Tagging now able to be sorted
Business Partners using Tags to manage their customers found that Tag Values and Keys could not be sorted and did not default sort into a logical order.
...
For information about using Tags, read more here...
Custom Scripts for Linux Servers
A while ago we enabled Custom Scripts to be run on Linux Servers.
The information displayed would include the command used as well as the result. We have changed this to return only the result, so that when users choose to receive an alarm on a specific result that information is clearly defined.
- Set up your custom scripts on the Custom Scripts tab from the Manage Equipment page
- Raise an alarm using the information received from the custom script
- Results can also be viewed on the Linux Server dashlet
For information about Custom Scripts, read more here...
Bug Fixes
In the Overriding Alarm Responses, if the response level was set to anything other than customer then the customer column would always show the customers location name instead of the customer name. Now the Customer Column will always show the Customer Name.
For some customercustomers, Call Details Detail records were not showing for 'Previous Day'. This has now been fixed.
In MS Teams call records, the Network Interface details were sometimes blank. This These are now populated.
An upgrade of VSM-E caused duplicate records to appear in the grid. Duplicates have been removed and the fix ensures duplication no longer occurs.
For some customers, in the MOS reports there were days appearing to have no data. You should now be able to see MOS data for all days with traffic.