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
Instrument the WorkLoad controller with the OTel SDK to export traces.
Technical Details
Use OTel Go to manually instrument the code to export the following spans as a single trace:
The Trace Context should be propagated into the CRDs via a common metadata field TraceContext. The context will be propagated using this immutable map.
The Workload controller shall use keptn/operator/workload as the component name.
The Workload controller shall extract the parent Span from TraceContext.
Each Span should be created with the following OTel Attribute:
KeptnApp as keptn.deployment.app_name
KeptnWorkload as keptn.deployment.workload
KeptnVersion as keptn.deployment.version
Acceptance Criteria
Workload creates a Consumer Span when it starts to handle a Workload CRD
Workload creates a Producer Span when it creates a WorkloadInstance
Attributes with Keptn information should always be added whenever possible (e.g. AppName, status of the task)
Goal
Instrument the WorkLoad controller with the OTel SDK to export traces.
Technical Details
Use OTel Go to manually instrument the code to export the following spans as a single trace:
The Trace Context should be propagated into the CRDs via a common metadata field
TraceContext
. The context will be propagated using this immutable map.The Workload controller shall use
keptn/operator/workload
as the component name.The Workload controller shall extract the parent Span from
TraceContext
.Each Span should be created with the following OTel Attribute:
keptn.deployment.app_name
keptn.deployment.workload
keptn.deployment.version
Acceptance Criteria
DoD
Resources
The text was updated successfully, but these errors were encountered: