You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We added a metric that registers whenever the concurrent-ruby instrumentation is invoked to differentiate between times the library is loaded by Rails and times the library is independently used by the customer.
Let's add more "invoked"-type metrics that record the first time some instrumentation is invoked so we can get a better sense of the instrumentation our customers use.
Acceptance Criteria
Libraries using prepend/chain_instrument methods reviewed for compatibility with record_metric_once
"invoked"-type metrics are added to the libraries that seem like good candidates
Angler's metric_names.txt is updated to include the new metrics
Design Consideration/Limitations
We may want to consider dropping the Supportability/Instrumentation/#{LibraryName}/#{Prepend || MethodChaining} metrics in favor of these metrics so that we know when instrumentation is used rather than installed.
Dependencies
Angler updates to allow us to observe the new data
Estimates
S
The text was updated successfully, but these errors were encountered:
When we discussed this issue during an estimation session, we decided adding "invoked" metrics would be the most appropriate for instrumented gems that are dependencies of other popular gems.
For these gems, the current installation metrics aren't enough to give us a clear picture of how many users leverage these libraries.
Following a pattern established by the concurrent-ruby instrumentation,
establish a way for all instrumentation to differentiate between the
simple presence of an instrumented gem and its invocation.
resolves#1923
Description
We added a metric that registers whenever the concurrent-ruby instrumentation is invoked to differentiate between times the library is loaded by Rails and times the library is independently used by the customer.
Let's add more "invoked"-type metrics that record the first time some instrumentation is invoked so we can get a better sense of the instrumentation our customers use.
Acceptance Criteria
record_metric_once
Design Consideration/Limitations
We may want to consider dropping the Supportability/Instrumentation/#{LibraryName}/#{Prepend || MethodChaining} metrics in favor of these metrics so that we know when instrumentation is used rather than installed.
Dependencies
Angler updates to allow us to observe the new data
Estimates
S
The text was updated successfully, but these errors were encountered: