Details
-
Bug
-
Resolution: Fixed
-
Major
-
Columnar 1.0.0
-
Untriaged
-
0
-
Unknown
-
Analytics Sprint 46
Description
Current Scenario :
- Currently if a user is using incorrect_credentials/API_keys_info while creating the Kafka Confluent/MSK link or while editing the link. We get "Unable to reach kafka cluster. Reason: 'org.apache.kafka.common.errors.SaslAuthenticationException: Authentication failed" message.
- And this is not incrementing the following metrics : `cbas_link_invalid_credentials_total`, `cbas_link_connect_failed_total` for create/connect link.
- Issue : The Invalid credentials and Link connect Alert won't get generated for Kafka Confluent/MSK link if these metrics are not incrementing.
Expectation :
Following Metrics `cbas_link_invalid_credentials_total`, `cbas_link_connect_failed_total` should get incremented for Kafka Confluent/MSK as well in the events: where wrong credentials/certificates/API keys are used while creating or updating link.
So that the Invalid credentials and Link connect Alert can be generated against Kafka Confluent/MSK links as well.
More Details :
For instance :
- Tried creating the Kafka Confluent link and intentionally used the wrong API secret and got this error "Unable to reach kafka cluster. Reason: 'org.apache.kafka.common.errors.SaslAuthenticationException: Authentication failed". Metric cbas_link_invalid_credentials_total was not increased. Screenshots below
- Then I connected successfully to Kafka Confluent link by using correct API key details
- Then I disconnected the link and tried updating the link with wrong API Key and I again got the same error "Unable to reach kafka cluster. Reason: 'org.apache.kafka.common.errors.SaslAuthenticationException: Authentication failed" as shown below and metric cbas_link_invalid_credentials_total and cbas_link_connect_failed_total didn't get updated