Heroku tracks unique id request

Question

I have a rather interesting log fragment:

173 <190>1 2014-08-10T16:27:04.714496+00:00 d.b94e55d3-c99e-4547-865d-708591bea1ee app web.2 - - Started POST "/mandrill_inbound" for 54.184.37.188 at 2014-08-10 16:27:04 +0000
128 <45>1 2014-08-10T16:27:04.928835+00:00 d.b94e55d3-c99e-4547-865d-708591bea1ee heroku web.2 - - Process running mem=665M(130.0%)
129 <45>1 2014-08-10T16:27:04.929061+00:00 d.b94e55d3-c99e-4547-865d-708591bea1ee heroku web.2 - - Error R14 (Memory quota exceeded)

Summary of this Process running mem=665M(130.0%)

And the related bit:

2014-08-10T16:27:04.745084+00:00 d.b94e55d3-c99e-4547-865d-708591bea1ee heroku router - - at=info method=POST path="/mandrill_inbound" host=www.myproject.com request_id=cfde9bb3-2cd8-4045-b3f1-235c0d4c91c3 fwd="54.184.37.188" dyno=web.2 connect=2ms service=202ms status=200 bytes=408

Now I can use this request identifier request_id=cfde9bb3-2cd8-4045-b3f1-235c0d4c91c3to find out which parameters were sent to this post request.

Or is there another way to figure this out?

If there is no way to reproduce what happened here, what will be the most sensible strategy? Because this memory problem does not go away on its own.

Answer 1

Unfortunately, you cannot do much in retrospect.

, , Heroku, .

Heroku, Librato, . Librato , Librato Heroku. , , Librato, , .

oink gem, / , , , oink .