Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[opentelemetry input plugin] grpc: received message larger than max #15230

Closed
rainbowwiki opened this issue Apr 25, 2024 · 10 comments · Fixed by #15231
Closed

[opentelemetry input plugin] grpc: received message larger than max #15230

rainbowwiki opened this issue Apr 25, 2024 · 10 comments · Fixed by #15231
Labels
feature request Requests for new plugin and for new features to existing plugins

Comments

@rainbowwiki
Copy link

Use Case

client send opentelemetry to telegraf

Expected behavior

telegraf can receive the opentelemetry metrics

Actual behavior

Thu, 25 Apr 2024 12:48:54 GMT - severe: [telemetry.OpenTelemetry_Exporter.f5telemetry_default::My_Consumer] error: Service request
Thu, 25 Apr 2024 12:48:54 GMT - severe: [telemetry.OpenTelemetry_Exporter.f5telemetry_default::My_Consumer] Error on attempt to send metrics:
Traceback:
Error: 8 RESOURCE_EXHAUSTED: grpc: received message larger than max (7560819 vs. 4194304)

Additional info

How can I adjust the max size for opentelemetry plugin?

@rainbowwiki rainbowwiki added the feature request Requests for new plugin and for new features to existing plugins label Apr 25, 2024
@powersj
Copy link
Contributor

powersj commented Apr 25, 2024

Hi,

Those logs do not look like Telegraf logs, but instead the logs from your exporter service?

Can you please share your telegraf logs and config please.

@powersj powersj added the waiting for response waiting for response from contributor label Apr 25, 2024
@rainbowwiki
Copy link
Author

the telegraf side no log for this issue,
I go through the opentelemetry input plugin, no config for increase the max size

@telegraf-tiger telegraf-tiger bot removed the waiting for response waiting for response from contributor label Apr 25, 2024
@powersj
Copy link
Contributor

powersj commented Apr 25, 2024

Please share your logs and config, you can omit any IP addresses or secrets.

@powersj powersj added the waiting for response waiting for response from contributor label Apr 25, 2024
@rainbowwiki
Copy link
Author

rainbowwiki commented Apr 25, 2024


[global_tags]


[agent]
  interval = "10s"
  round_interval = true

  metric_batch_size = 20480

  metric_buffer_limit = 2000000

  collection_jitter = "0s"

  flush_interval = "20s"
  flush_jitter = "0s"

  precision = ""

  debug = true
  quiet = false

  logtarget = "file"

  logfile = "/var/log/telegraf/telegraf.log"

  logfile_rotation_interval = "0d"

  logfile_rotation_max_size = "10MB"

  logfile_rotation_max_archives = 5

  hostname = ""
  omit_hostname = false


[[outputs.file]]
   files = ["stdout", "/tmp/metrics.out"]
   rotation_interval = "10m"
   rotation_max_archives = 10
   rotation_max_size = "100MB"
   data_format = "json"



[[outputs.health]]


[[outputs.kafka]]
  brokers = ["xxxxx"]
  topic = "zeus-source-f5"
  data_format = "json"
  json_timestamp_units = "1ms"
  
  
# Receive OpenTelemetry traces, metrics, and logs over gRPC
[[inputs.opentelemetry]]
  ## Override the default (0.0.0.0:4317) destination OpenTelemetry gRPC service
  ## address:port
  service_address = "0.0.0.0:4317"

  ## Override the default (5s) new connection timeout
  timeout = "30s"

  ## Override the default (prometheus-v1) metrics schema.
  ## Supports: "prometheus-v1", "prometheus-v2"
  ## For more information about the alternatives, read the Prometheus input
  ## plugin notes.
  metrics_schema = "prometheus-v1"

  ## Optional TLS Config.
  ## For advanced options: https://github.com/influxdata/telegraf/blob/v1.18.3/docs/TLS.md
  ##
  ## Set one or more allowed client CA certificate file names to
  ## enable mutually authenticated TLS connections.
  # tls_allowed_cacerts = ["/etc/telegraf/clientca.pem"]
  ## Add service certificate and key.
  # tls_cert = "/etc/telegraf/cert.pem"
  # tls_key = "/etc/telegraf/key.pem"

@telegraf-tiger telegraf-tiger bot removed the waiting for response waiting for response from contributor label Apr 25, 2024
@rainbowwiki
Copy link
Author

this is my config, telegraf side no log

@powersj
Copy link
Contributor

powersj commented Apr 25, 2024

Thanks for the config

telegraf side no log

Your config has logs sent here:

logtarget = "file"
logfile = "/var/log/telegraf/telegraf.log"

I have also put up #15231 which introduces a new option called max_msg_size. In 30mins after this message, artifacts should be attached to that PR that you can download and try. Please let me know if setting that value to something like "8MB" or higher helps out.

@powersj powersj added the waiting for response waiting for response from contributor label Apr 25, 2024
@rainbowwiki
Copy link
Author

thanks for your support! will test and give you feedback~

@telegraf-tiger telegraf-tiger bot removed the waiting for response waiting for response from contributor label Apr 25, 2024
@powersj powersj added the waiting for response waiting for response from contributor label Apr 25, 2024
@powersj
Copy link
Contributor

powersj commented Apr 29, 2024

@rainbowwiki have you had a chance to give the PR a try? Thanks!

@telegraf-tiger telegraf-tiger bot removed the waiting for response waiting for response from contributor label Apr 29, 2024
@powersj powersj added the waiting for response waiting for response from contributor label Apr 29, 2024
@rainbowwiki
Copy link
Author

@powersj Hi man, sorry for the message delay, we tryed and work now, thanks!

@telegraf-tiger telegraf-tiger bot removed the waiting for response waiting for response from contributor label May 10, 2024
@powersj
Copy link
Contributor

powersj commented May 10, 2024

Thanks for confirming!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Requests for new plugin and for new features to existing plugins
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants