Emily S

Hi @dgoradia Thank you for the additional information. I now understand what you are looking for. The Ruby agent doesn't allow users to process the field values themselves that are...

Hi again @dgoradia, would you mind telling me why rails puts the post body in the header? I'm curious what the reason is for that?

This issue is a due to a limitation of using `IO.pipe` and forking processes. It's not clear what the best course of action is at this point. The agent uses...

Hi @jclusso this isn't really a bug that can be fixed. It's more a limitation of the Ruby language and I'm not sure there's anything we can do about it....

@jclusso There's no way to selectively disable this log message while enabling the other log messages, unfortunately. The message does indicate some data was not correctly compressed and sent to...

Hi @Ex-Ark! Sorry to hear that you’ve having trouble connecting to the APM server from your Rails app. We have a few questions about your setup: You are running the...

Hi @Ex-Ark The code that I believe is causing that error are the lines in [this file](https://github.com/elastic/apm-agent-ruby/blob/master/lib/elastic_apm/metrics/cpu_mem_set.rb) trying to access `/proc/*` files in a Linux system. [Here](https://github.com/elastic/apm-agent-ruby/blob/master/lib/elastic_apm/metrics/cpu_mem_set.rb#L145) is an example....

Hi @Ex-Ark only the system metrics will be disabled, not the other ones (that you're seeing)

Since you're already putting `puts` in the agent code, can you see if one of the `IO.readlines` in [this file](https://github.com/elastic/apm-agent-ruby/blob/master/lib/elastic_apm/metrics/cpu_mem_set.rb) is reached and throws an error?

hmm, I can't find a place where we are using an offset and that error might be raised but thank you for pointing us to that ruby bug! If there's...