Fixed Issues in Streams Messaging Manager
This section lists the issues that have been fixed since the previous version.
- The Condition field in the Alert Policy UI displays incorrect values
- Bug ID: CSP-734
- Exception in the SMM UI - Not displaying any data
- Bug ID: CSP-875Apache JIRA: N/AComponent: Streams Messaging ManagerSummary: If the topic (or) producer name contains keywords such as clientId/topic/partition, then SMM would not display the metrics for those resources. This is due to the bug in regular expression which captures the topic (or) partition information from the metric name. SMM also throws "For Input String" error in the UI when there exists another topic whose name is a suffix of the first one. For example, for a topic named with "hello.topic.world", SMM would not display the metrics for the resource as the topic name contains the keyword "topic". If there exists another topic named as world whose name is a suffix of the first one, then SMM throws "For Input String" error in the UI.
- Cannot read property 'indexOf' thrown when ETELatencyMetrics is disabled
- Bug ID: CSP-778Apache JIRA: N/AComponent: Streams Messaging ManagerSummary: If latency metrics is disabled and you click the latency tab on the Topic Profile page in the SMM UI, then the following error appears: Cannot read property ‘indexOf’ of null.
- SMM logs are not moving to the custom location
- Bug ID: CSP-838Apache JIRA: N/AComponent: Streams Messaging ManagerSummary: SMM logs are not created in the custom location.
- SMM throws error if Service Monitor is not on CM host
- Bug ID: CSP-798Apache JIRA: N/AComponent: Streams Messaging ManagerSummary: If the Cloudera Manager Service Monitor and Cloudera Manager Server are deployed on different hosts, SMM is unable to fetch metrics correctly. As a result, historic data for consumer offsets and lag are not displayed, only the latest data is available.
