![]() The root cause is that Splunk will in these architectures erroneously retain the previous version of the codec_types lookup across an app update. Fixed a bug that affected customers who used SHC, and also Cloud customers on Victoria stacks, where after an upgrade searches would fail with an error about the codec_types lookup.This is now fixed and all users will get the message that they cannot upload new CSV files when using SHC. Prior to this release the upload would fail for admin users who had the capabilty list_search_head_clustering, but succeed for users lacking that capability, leading to an inconsistent state on the SHC. Fixed a bug around uploading new csv lookup files in the Setup pages, specifically when using SHC (Search-Head Clustering).This version and going forward will not create that problem and will moreover repair that damage when it sees it on disk. Critical – Fixed a bug in the app’s migration code where users upgrading from versions older than 6.3.5 would end up with an incorrect and unusable call_quality_thresholds lookup.Searches in that page are now approximately 6x faster and run with far fewer resources used. Worked around a problem in Splunk that was dragging down performance in the Call Concurrency and Gateway Utilization page.Reworked some health checks to reduce error messages if the user’s role has unusually restricted capabilities or permissions.Improved a core health check to detect whether the index specified in the “custom_index” macro actually exists.The matching will then occur as expected on both the “extensions with calls” and also the “extensions with no calls” sides. ![]() Fixed a bug in the Investigate Groups page, where you can now tell it to include groups/extensions with zero calls, and also at the same time use the “number” field to filter.Now clicking those table rows leads to the Call Detail view and the call is displayed correctly there. If users were in its “Calls over time” tab and attempted to drill down on one of the displayed calls it would not work. Fixed a bug in the Device Detail page.Functionality Form fields have been reordered across the various Investigate pages to improve consistency from page to page.Critical For customers using Search Head Clustering (SHC), users are now able to post lookup changes from the “Setup” screens, instead of being told to make their lookup changes on the Deployer.Critical For customers using Search head Clustering (SHC), the app’s config now specifies that existing lookups on the SHC members are to be preserved in all cases, even when the deployer push was done with preserve-lookups set to false.Fixed a bug where if the Canary app was missing entirely the app’s landing page loaded blank, displaying no error message about the need to install Canary.Also this panel now respects the field-ordering specified by the field picker (previously it listed them alphabetically). Fixed a bug in the Call Detail view, where the top right panel that can list any field values, could previously not display any CMR fields.Added a health check to detect whether the Devices Lookup contains any device names that are listed on more than one row. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |