CreateInstrumentationConfigurationRequest
¶
Source code in docs_src/capo_application_signals/types/create_instrumentation_configuration_request.py
attribute_filters
instance-attribute
¶
attribute_filters: NotRequired[DynamicInstrumentationAttributeFilters]
Client-side filters that target specific instances. Each object in the array is AND-matched on its keys, and multiple objects are OR-matched to decide where to apply the instrumentation.
capture_configuration
instance-attribute
¶
capture_configuration: CaptureConfiguration
Specifies what to capture when the instrumentation point is hit. Specify CodeCapture for code-level capture settings.
description
instance-attribute
¶
description: NotRequired[str]
An optional short description (up to 50 characters) that explains the purpose of this instrumentation.
environment
instance-attribute
¶
environment: str
The environment that the service is running in, such as eks:cluster-prod/namespace or ec2:production.
expires_at
instance-attribute
¶
expires_at: NotRequired[datetime]
For BREAKPOINT: optional, defaults to 24 hours, must be between 5 min and 24 hours. For PROBE: not supported. PROBE configurations are permanent and persist until explicitly deleted.
instrumentation_type
instance-attribute
¶
instrumentation_type: InstrumentationType
Type of instrumentation: BREAKPOINT (temporary) or PROBE (permanent)
location
instance-attribute
¶
location: Location
The location where instrumentation should be applied. Specify a CodeLocation for code-level instrumentation.
service
instance-attribute
¶
service: str
The name of the service to instrument. This should match the service.name resource attribute reported by the application.
signal_type
instance-attribute
¶
signal_type: DynamicInstrumentationSignalType
The telemetry signal type to emit for this instrumentation. The supported value is SNAPSHOT.