Support converting http timers to OTel traces #560
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds support in Forwarder Agent for converting timers tagged with trace and span ids to OpenTelemetry traces. Feature is optional and currently not active by default.
temporary_emit_otel_traces
property controls whether the Forwarder Agent converts timers to traces. An alternative implementation approach would have been to allow the ingress config for each consumer to declare that it wanted this feature enabled. The property was added to the Windows job for consistency although we don't expect it to be receiving http timers.service.name
attribute to be defined at the resource level. However it's not currently possible to configure the span metrics connector in otel-collector-release.Depends on this gorouter change: cloudfoundry/gorouter#407
Type of change
Testing performed?
Checklist:
main
branch, or relevant version branchIf you have any questions, or want to get attention for a PR or issue please reach out on the #logging-and-metrics channel in the cloudfoundry slack