# Elastic Ruby on Rails APM: Queue is full issue

**URL:** <https://discuss.elastic.co/t/elastic-ruby-on-rails-apm-queue-is-full-issue/246793>\
**Category:** APM\
**Tags:** ruby\
**Created:** [August 28, 2020, 4:16pm UTC](https://discuss.elastic.co/t/elastic-ruby-on-rails-apm-queue-is-full-issue/246793 "2020-08-28T16:16:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rahulnama](https://avatars.discourse-cdn.com/v4/letter/r/8c91f0/32.png) [@rahulnama](https://discuss.elastic.co/u/rahulnama)\
**Post date:** [August 28, 2020, 4:16pm UTC](https://discuss.elastic.co/t/elastic-ruby-on-rails-apm-queue-is-full-issue/246793/1 "2020-08-28T16:16:43Z")

</div>

Hi Team

I'm using APM version: 7.8.0 for ruby on rails app. I integrated this with prod and dev.

However, for some reason I'm not able to see recent requests for prod site.

Here are the logs in my app. I see queue is full

 ![Screen Shot 2020-08-28 at 11.09.48 AM](https://us1.discourse-cdn.com/elastic/original/3X/f/b/fba0a5e5048f98142f5f4923880a7d29472e91ec.png)

Any suggestions on Why this is happening ? bcos my APM server is working fine and I'm able to get data from Dev.

Here are the logs of APM server:

```
|2020-08-28T16:13:07.117Z|INFO|[request]|middleware/log_middleware.go:97|request ok|{"request_id": "9557d79b-09c4-409a-bbab-0f288f193049", "method": "GET", "URL": "/config/v1/agents?service.name=Ilearn", "content_length": 0, "remote_address": "10.85.77.124", "user-agent": "elastic-apm-ruby/3.10.1 http.rb/4.4.1 ruby/2.4.1", "response_code": 200}|
|---|---|---|---|---|---|
|2020-08-28T16:13:07.847Z|INFO|[request]|middleware/log_middleware.go:97|request ok|{"request_id": "d77adb92-c9b2-4cd2-ae57-dea86d206a5a", "method": "GET", "URL": "/config/v1/agents?service.name=IlearnDev", "content_length": 0, "remote_address": "10.85.77.118", "user-agent": "elastic-apm-ruby/3.10.1 http.rb/4.4.1 ruby/2.4.1", "response_code": 200}|
|2020-08-28T16:13:13.253Z|INFO|[request]|middleware/log_middleware.go:97|request accepted|{"request_id": "2b7a1c36-430e-44fc-98cf-76df7304a0e7", "method": "POST", "URL": "/intake/v2/events", "content_length": 558, "remote_address": "10.213.180.192", "user-agent": "elastic-apm-ruby/3.10.1 http.rb/4.4.1 ruby/2.4.1", "response_code": 202}|
|2020-08-28T16:13:20.814Z|INFO|[request]|middleware/log_middleware.go:97|request ok|{"request_id": "61dddcac-6157-4afb-bc92-6f592f262d2b", "method": "GET", "URL": "/config/v1/agents?service.name=IlearnDev", "content_length": 0, "remote_address": "10.213.180.192", "user-agent": "elastic-apm-ruby/3.10.1 http.rb/4.4.1 ruby/2.4.1", "response_code": 200}|
|2020-08-28T16:13:20.935Z|INFO|[request]|middleware/log_middleware.go:97|request accepted|{"request_id": "4e4e7706-7a07-4980-aab3-fc238ca2d3e6", "method": "POST", "URL": "/intake/v2/events", "content_length": 608, "remote_address": "10.85.77.118", "user-agent": "elastic-apm-ruby/3.10.1 http.rb/4.4.1 ruby/2.4.1", "response_code": 202}|

```

I'm trying to understand what made the queue full ? bcos queue can send data to apm server and apm server is not busy.

Please suggest

Thanks  
Rahul

---

<div class="post-metadata">

**Author:** ![rahulnama](https://avatars.discourse-cdn.com/v4/letter/r/8c91f0/32.png) [@rahulnama](https://discuss.elastic.co/u/rahulnama)\
**Post date:** [August 31, 2020, 4:18pm UTC](https://discuss.elastic.co/t/elastic-ruby-on-rails-apm-queue-is-full-issue/246793/2 "2020-08-31T16:18:16Z")

</div>

Hi Team

Any suggestions would be helpful.

Thank you

---

<div class="post-metadata">

**Author:** ![ylasri](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ylasri/32/86120_2.png) [@ylasri](https://discuss.elastic.co/u/ylasri)\
**Post date:** [August 31, 2020, 5:02pm UTC](https://discuss.elastic.co/t/elastic-ruby-on-rails-apm-queue-is-full-issue/246793/3 "2020-08-31T17:02:44Z")

</div>

Hope this [link](https://www.elastic.co/guide/en/apm/server/current/tune-apm-server.html) can can help  
APM Server uses an internal queue to buffer incoming events. A larger queue can retain more data if Elasticsearch is unavailable for longer periods, and it alleviates problems that might result from sudden spikes of traffic. You can adjust the queue size by overriding [`queue.mem.events`](https://www.elastic.co/guide/en/apm/server/current/configuration-process.html#mem.events). Increasing [`queue.mem.events`](https://www.elastic.co/guide/en/apm/server/current/configuration-process.html#mem.events) can significantly affect APM Server memory usage.

Also this [link](https://www.elastic.co/guide/en/apm/server/master/common-problems.html#queue-full) can help

---

<div class="post-metadata">

**Author:** ![rahulnama](https://avatars.discourse-cdn.com/v4/letter/r/8c91f0/32.png) [@rahulnama](https://discuss.elastic.co/u/rahulnama)\
**Post date:** [August 31, 2020, 8:49pm UTC](https://discuss.elastic.co/t/elastic-ruby-on-rails-apm-queue-is-full-issue/246793/4 "2020-08-31T20:49:49Z")

</div>

Sure @ylasri

I will have a look.

Thank you : )

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 21, 2020, 4:49pm UTC](https://discuss.elastic.co/t/elastic-ruby-on-rails-apm-queue-is-full-issue/246793/5 "2020-09-21T16:49:49Z")

</div>

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.