-
Notifications
You must be signed in to change notification settings - Fork 598
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cleanup instrumentation info-level logging #2434
Comments
kford-newrelic
added
3
Story Point Estimate
and removed
estimate
Issue needing estimation
labels
Feb 16, 2024
kford-newrelic
added
the
apr-jun qtr
Represents proposed work item for the Apr-Jun quarter
label
Apr 12, 2024
kford-newrelic
removed
the
apr-jun qtr
Represents proposed work item for the Apr-Jun quarter
label
Jun 3, 2024
kford-newrelic
modified the milestones:
Proposed - Ruby Agent - FY25Q3,
Ruby Agent - FY25Q3 - Agent Enhancements & Tech Debt
Sep 25, 2024
github-project-automation
bot
moved this from In Sprint
to Code Complete/Done
in Ruby Engineering Board
Oct 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When the agent instruments a customer's app, it records a log message about what is being instrumented, for example:
Installing Fiber instrumentation
. We often hard-code this log in instrumentation files. However, the methodlog_and_instrument
, which is called whenever preprend or chain is used, also logs instrumentation and records a supportability metric. This results in cases where instrumentation notices are logged twice, or potentially not at all, and supportability metrics are not recorded.We should review each instrumentation file to:
default_source.rb
can be used to quickly determine if prepend or chain is avaliable or not.dupe: #2516
The text was updated successfully, but these errors were encountered: