Error seen for mule applications deployed RTF Error: Container "anypoint-monitoring" - CrashLoopBackOff

SYMPTOM

The RTF application deployed on Self-managed ( BYOK) Goes into "Not Running" Status.

An error showing "anypoint-monitoring" pod  in "CrashloopBackOff" comes up on the Anypoint platform.

The Logs on the Anypoint-monitoring sidecar container show a Fatal Error

pipelines or are using Logstash pipelines, you can ignore this warning.
2023-05-18T04:29:07.400Z    WARN    [cfgwarn]    log/input.go:89    DEPRECATED: Log input. Use Filestream input instead.
unexpected fault address 0xeb6dee57
fatal error: fault
[signal SIGSEGV: segmentation violation code=0x2 addr=0xeb6dee57 pc=0x8ddf310]

goroutine 77 [running]:
runtime.throw({0xa6c6911, 0x5})
    /usr/local/go/src/runtime/panic.go:992 +0x6a fp=0xde41d40 sp=0xde41d2c pc=0x8a8b4da
runtime.sigpanic()
    /usr/local/go/src/runtime/signal_unix.go:825 +0x1e7 fp=0xde41d58 sp=0xde41d40 pc=0x8aa2387
crypto/tls.(*Conn).Write(0xdd46600, {0xdde6000, 0x5045, 0x9a0a})

CAUSE

SOLUTION

After removing the Third Party Monitoring service the anypoint-monitoring container came up Fine.

In few cases, excluding few specific monitoring capabilities ( What to exclude depends on the monitoring capabilities added)  on the third-party Service, also helped to recover from the issue.