{"action":"created","issue":{"url":"https://api.github.com/repos/elastic/apm-agent-ruby/issues/155","repository_url":"https://api.github.com/repos/elastic/apm-agent-ruby","labels_url":"https://api.github.com/repos/elastic/apm-agent-ruby/issues/155/labels{/name}","comments_url":"https://api.github.com/repos/elastic/apm-agent-ruby/issues/155/comments","events_url":"https://api.github.com/repos/elastic/apm-agent-ruby/issues/155/events","html_url":"https://github.com/elastic/apm-agent-ruby/issues/155","id":332568385,"node_id":"MDU6SXNzdWUzMzI1NjgzODU=","number":155,"title":"Feature request - logging of slow requests","user":{"login":"cheald","id":9830,"node_id":"MDQ6VXNlcjk4MzA=","avatar_url":"https://avatars3.githubusercontent.com/u/9830?v=4","gravatar_id":"","url":"https://api.github.com/users/cheald","html_url":"https://github.com/cheald","followers_url":"https://api.github.com/users/cheald/followers","following_url":"https://api.github.com/users/cheald/following{/other_user}","gists_url":"https://api.github.com/users/cheald/gists{/gist_id}","starred_url":"https://api.github.com/users/cheald/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cheald/subscriptions","organizations_url":"https://api.github.com/users/cheald/orgs","repos_url":"https://api.github.com/users/cheald/repos","events_url":"https://api.github.com/users/cheald/events{/privacy}","received_events_url":"https://api.github.com/users/cheald/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-06-14T21:19:10Z","updated_at":"2018-06-15T07:00:46Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"I've been using elastic-apm for several weeks now, and it's great at giving me high-level metrics, but it's not very useful for troubleshooting pathological cases.\r\n\r\nI'd like elastic-apm to have a configurable runtime threshold, and \"sample\" any request which runs for longer than that threshold. I realize that this is not how the project is currently designed, architecturally, but samples are *way* more important for the slow, infrequent cases than the common fast case. When I have slow actions, I want to be able to figure out why they were slow.\r\n\r\nIs there anything like that on the horizon?"},"comment":{"url":"https://api.github.com/repos/elastic/apm-agent-ruby/issues/comments/397532077","html_url":"https://github.com/elastic/apm-agent-ruby/issues/155#issuecomment-397532077","issue_url":"https://api.github.com/repos/elastic/apm-agent-ruby/issues/155","id":397532077,"node_id":"MDEyOklzc3VlQ29tbWVudDM5NzUzMjA3Nw==","user":{"login":"mikker","id":2819,"node_id":"MDQ6VXNlcjI4MTk=","avatar_url":"https://avatars3.githubusercontent.com/u/2819?v=4","gravatar_id":"","url":"https://api.github.com/users/mikker","html_url":"https://github.com/mikker","followers_url":"https://api.github.com/users/mikker/followers","following_url":"https://api.github.com/users/mikker/following{/other_user}","gists_url":"https://api.github.com/users/mikker/gists{/gist_id}","starred_url":"https://api.github.com/users/mikker/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mikker/subscriptions","organizations_url":"https://api.github.com/users/mikker/orgs","repos_url":"https://api.github.com/users/mikker/repos","events_url":"https://api.github.com/users/mikker/events{/privacy}","received_events_url":"https://api.github.com/users/mikker/received_events","type":"User","site_admin":false},"created_at":"2018-06-15T07:00:46Z","updated_at":"2018-06-15T07:00:46Z","author_association":"MEMBER","body":"Hi @cheald. Glad to hear that you are finding APM useful!\r\n\r\nWe already do a few things to help with what you are describing: First, there's the _Impact_ of the request. This is the default sorting value of requests (or _transactions_) and it should help with finding the endpoints that are most popular _and_ the slowest. If you just want slowest, you can sort by avg. resp. time.\r\n\r\nSecond, if what you want is to sample _only_ the requests taking longer than _x_ ms then you are right, we don't have that. There `span_frames_min_duration` but that works on the individual span and not the transaction as a whole. _Sample_ in this context meaning _include stack trace and source code_.\r\n\r\nI haven't thought about adding a (kind of) `transaction_min_duration` if this is what you are after?\r\n\r\nI might be misunderstanding you – if so, please do tell 😄 "}}
{"actor":{"display_login":"mikker"}}