WithDefaultFunctionLocationtrace option. This allows the caller to indicate a fall-back function to use for CLM in case no other location was found first.
- Added caching versions of the code-level metrics functions
FunctionLocation, and trace options
WithFunctionLocation. These improve performance by caching the result of computing the source code location, and reuse that cached result on all subsequent calls.
- Added a
WithCodeLevelMetricstrace option to force the collection of CLM data even if it would have been excluded as being out of the configured scope. (Note that CLM data are never collected if CLM is turned off globally or if the
WithoutCodeLevelMetricsoption was specified for the same transaction.)
- Added an exported
CodeLevelMetricsScopeLabelToValuefunction to convert a list of strings describing CLM scopes in the same manner as the
NEW_RELIC_CODE_LEVEL_METRICS_SCOPEenvironment variable (but as individual string parameters), returning the
CodeLevelMetricsScopevalue which corresponds to that set of scopes.
- Added a new
CodeLevelMetricsScopeLabelListToValuefunction which takes a comma-separated list of scope names exactly as the
NEW_RELIC_CODE_LEVEL_METRICS_SCOPEenvironment variable does, and returns the
CodeLevelMetricsvalue corresponding to that set of scopes.
- Added text marshaling and unmarshaling for the
CodeLevelMetricsScopevalue, allowing the
CodeLevelMetricsfield of the configuration
structto be converted to or from JSON or other text-based encoding representations.
WithPathPrefixtrace option now takes any number of
stringparameters, allowing multiple path prefixes to be recognized rather than just one.
FunctionLocationfunction now accepts any number of function values instead of just a single one. The first such parameter which indicates a valid function, and for which CLM data are successfully obtained, is the one which will be reported.
- The configuration
PathPrefixis now deprecated with the introduction of a new
PathPrefixesfield. This allows for multiple path prefixes to be given to the agent instead of only a single one.
NEW_RELIC_CODE_LEVEL_METRICS_SCOPEenvironment variable now accepts a comma-separated list of pathnames.
- Improved the implementation of CLM internals to improve speed, robustness, and thread safety.
- Corrected the implementation of the
WrapHandleFuncfunctions so that they consistently report the function being invoked by the
httpframework, and improved them to use the new caching functions and ensured they are thread-safe.
This release fixes issue #557.
As of release 3.18.0, the API was extended by allowing custom options to be added to calls to the
Application.StartTransaction method and the
WrapHandleFunc functions. They are implemented as variadic functions such that the new option parameters are optional (i.e., zero or more options may be added to the end of the function calls) to be backward-compatible with pre-3.18.0 usage of those functions. This prevents the changes from breaking existing code for typical usage of the agent. However, it does mean those functions' call signatures have changed:
WrapHandle(*Application, string, http.Handler)->
WrapHandle(*Application, string, http.Handler, ...TraceOption)
WrapHandleFunc(*Application, string, func(http.ResponseWriter, *http.Request))->
WrapHandleFunc(*Application, string, func(http.ResponseWriter, *http.Request), ...TraceOption)
If, for example, you created your own custom interface type which includes the
StartTransaction method or something that depends on these functions' exact call semantics, that code will need to be updated accordingly before using version 3.18.0 (or later) of the Go Agent.
New Relic recommends that you upgrade the agent regularly to ensure that you’re getting the latest features and performance benefits. Additionally, older releases will no longer be supported when they reach end-of-life.
See the Go Agent EOL Policy for details about supported versions of the Go Agent and third-party components.