Problem

There may be occasions that a managed connector fails and the underlying connector error message is not displayed in the Console UI.

On these occasions it can be useful for troubleshooting to look at the actual connector log file to find a more helpful error.  

Solution 

In the current release of Redpanda Cloud,  log file messages for managed connectors are stored in an internal redpanda topic :   

_internal_connectors_logs

The Key for this topic is based on the Connector Name.

To provide an example ...   

We have configured a MM2 Connector  called mirror-source-connector-urlp
but it is an "UNHEALTHY" state.   Clicking on "View Details" tells us there are no tasks running which is not good.. but we do not know the exact cause.

To investigate further, we want to look at the connector logs.

Navigate to :

Console > Topics  > _internal_connectors_logs

If you have many connectors, you can set a filter setting the key to the connector came. 

Click Filter button, click +  to enter the filter ..  mirror-source-connector-urlp is the connector name in this example

if (key =="mirror-source-connector-urlp") return true
//allow all messages

Click Refresh. Now only the entries for the filtered connector are displayed  

The topic message Value field contains the log file entries... 
In this case we can see there are ERRORS being reported... 
Expand (+) the message to expand the error message.

In this example.. it was down to MM2 connector parameter "Source cluster SASL mechanism" being set to "PLAIN" when is not a valid Client SASL mechanism on the source cluster so the config can be rectified.
----

Note:
In future releases of Redpanda Cloud , the connector log file will be directly accessible via a drill down on the relevant connector in the Cloud Console UI. Additionally improvements to propagate some of these errors to the UI.