This message was deleted.

If there are no error logs from the

otlp/new:

then it’s working but the log you shared doesn’t give full picture since it doesn’t show collector started to accept data yet.

Ok it was linked to the issue of pod never being Ready. I succeeded to deploy other pods and have a configuration Ready, I can see an error message:

2023-03-29T09:21:25.733Z	warn	zapgrpc/zapgrpc.go:191	[core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {
  "Addr": "apm.monitoring.svc.cluster.local:4318",
  "ServerName": "apm.monitoring.svc.cluster.local:4318",
  "Attributes": null,
  "BalancerAttributes": null,
  "Type": 0,
  "Metadata": null
}. Err: connection error: desc = "error reading server preface: http2: frame too large"	{"grpc_log": true}

This means the request payload is too large. Either configure the grpc server to receiver bigger streams or batch process with a size that doesn’t lead to very large payloads from exporter.

Yes thanks, I found it quickly how to change this, it worked after the changes.