The below splunk surfaces a few different "bad" kafka error messages:

• Could not connect to the Kafka topic: Local: Broker transport failure (-195)
• attempted 6 restart(s): Kafka $emit encountered error -192: Local: Message timed out
• KafkaConsumerOperator failed to get committed offsets: Local: Timed out (-185)

We should figure out how to flow more information from librdkafka to return a better error message to the customer.

https://splunk.corp.mongodb.com/en-US/app/cloud/search?earliest=1740675600&latest=1741283656&q=search%20index%3Dmhouse%20source%3Dstreams-spm%20(projectID!%3D%2265094f059e0776665611598b%22%20AND%20projectID!%3D%226695222fc5479449e1e8d2be%22)%20%22TransitionToFailed%22%20%0A%60%60%60%0AThe%20below%20clause%20filters%20error%20failures%20during%20create%20validation%2C%20which%20are%20frequent%2C%20noisy%2C%20and%20most%20likely%20the%0Auser%27s%20fault.%0A%60%60%60%0AAND%20errorMsg!%3D%22*cluster%20is%20paused%22%0AAND%20streamProcessorID!%3D%22000000000000000000000000%22%0AAND%20(%22Kafka%22%20OR%20%22offsets%22)%0A%7C%20eval%20command%3Dif(isnotnull(commandName)%2C%20commandName%2C%20%22background%22)%0A%7C%20stats%20count%20by%20_time%2C%20errorMsg%2C%20command%2C%20errorCode%2C%20isInternalError%2C%20projectID%2C%20tenantID%2C%20streamProcessorID&display.page.search.mode=smart&dispatch.sample_ratio=1&display.page.search.tab=statistics&display.general.type=statistics&sid=1741283724.4798469