This Instrumentation Rule is currently only available with the Odigos Enterprise plan.
Contact us for more information.
Contact us for more information.
Considerations
Configuration Options
column
column
column
boolean : Indicates whether to record the code.column attribute for the column number in the code.filepath best representing the operation.- This field is optional, and defaults to
false
filePath
filePath
filePath
boolean : Indicates whether to record the code.filepath attribute for the source code file name that identifies the code unit.- This field is optional, and defaults to
false
function
function
function
boolean : Indicates whether to record the code.function attribute for the method or function name, or equivalent.- This field is optional, and defaults to
false
lineNumber
lineNumber
lineNumber
boolean : Indicates whether to record the code.lineno attribute for the line number in the code.filepath best representing the operation.- This field is optional, and defaults to
false
namespace
namespace
namespace
boolean : Indicates whether to record the code.namespace attribute for the “namespace” within which code.function is defined. Usually the qualified class or module name, such that code.namespace + some separator + code.function form a unique identifier for the code unit.- This field is optional, and defaults to
false
stackTrace
stackTrace
stackTrace `boolean
- This field is optional, and defaults to
false
Any unspecified options will be set to the default value of
false (not recorded).Basic Example
The following example demonstrates how to enable code attributes for all supported workloads and instrumentation libraries in the cluster.1
Create a YAML file with the following content:
code-attributes.yaml
2
Apply the action to the cluster: