- Fixed newrelic transaction timing #75
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
jarpi
commented
Feb 29, 2016
jarpi
commented
- While working with custom transactions, we've noticed of a bad transaction time in the reports - There's a method in new relic api that can fake total duration time of the transaction
| } | ||
|
|
||
| function getFunctionContainer (obj, props) { | ||
| var currentProps = props.map(function (item) { |
There was a problem hiding this comment.
Check lodash and ramda docs http://ramdajs.com/0.19.1/docs
rafinskipg
added a commit
that referenced
this pull request
Mar 1, 2016
- Fixed newrelic transaction timing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.