You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some exporters have different log entry size limits. Google Cloud Logging has a limit of 256KB and will issue the following error when breached.
Error
rpc error: code = InvalidArgument desc = Log entry with size 388.3K exceeds maximum size of 256.0K
error details: name = Unknown desc = log_entry_errors:{key:16 value:{code:3 message:"Log entry with size 388.3K exceeds maximum size of 256.0K"}} log_entry_errors:{key:17 value:{code:3 message:"Log entry with size 323.0K exceeds maximum size of 256.0K"}}
To get around this error it's possible to use the filelogreceiver to split the log lines.
However, there are many other receiver types which don't have the capability to split logs. The OTLP receiver allows setting max_recv_msg_size_mib however that would cause the log to simply not be sent, and doesn't allow for splitting.
One additional use-case could be using two exporters which allow for different sized logs. In the following example the smaller exporter googlecloud requires the logs be cut smaller than the the googlecloudpubsub exporter.
Component(s)
No response
Describe the issue you're reporting
Some exporters have different log entry size limits. Google Cloud Logging has a limit of 256KB and will issue the following error when breached.
Error
To get around this error it's possible to use the
filelogreceiver
to split the log lines.However, there are many other receiver types which don't have the capability to split logs. The OTLP receiver allows setting max_recv_msg_size_mib however that would cause the log to simply not be sent, and doesn't allow for splitting.
One additional use-case could be using two exporters which allow for different sized logs. In the following example the smaller exporter
googlecloud
requires the logs be cut smaller than the thegooglecloudpubsub
exporter.The text was updated successfully, but these errors were encountered: