Skip to content
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

Add tracing capability for Workload #99

Closed
4 tasks
Tracked by #47
thisthat opened this issue Oct 4, 2022 · 0 comments · Fixed by #125
Closed
4 tasks
Tracked by #47

Add tracing capability for Workload #99

thisthat opened this issue Oct 4, 2022 · 0 comments · Fixed by #125
Assignees

Comments

@thisthat
Copy link
Member

thisthat commented Oct 4, 2022

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:

Image

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)

DoD

  • The Workload Controller generates Spans

Resources

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants