ajp-lsq

Switch tracing service name to be ServingRevision rather than ServingPod in queue-proxy

16

## Describe the feature Currently, queue-proxy uses the pod name as the service name in the traces it sends out. Link to line where this happens here: https://github.com/knative/serving/blob/33dbc31dd93d4ec1aed2d026d3763fb81a1cc807/cmd/queue/main.go#L357 This is...

## Problem statement I have a set of operations under a tag called "client". When I go to generate my server code in an output folder called `gen/server`, the file...

Support env replacement in config-tracing

3

**Problem** I'm trying to run the opentelemetry-collector as an agent i.e. daemonset. For this to be maximally useful, I have to point each pod to the zipkin port 9411 on...

Cannot use iamRole on S3 source

2

When trying to create an AWSS3Source using the `auth.iamRole` parameter, the `triggermesh-controller` pod returns the following error: ```json {"severity":"INFO","timestamp":"2022-07-21T15:54:27.180662781Z","logger":"triggermesh-controller.event-broadcaster","caller":"record/event.go:285","message":"Event(v1.ObjectReference{Kind:\"AWSS3Source\", Namespace :\"triggermesh\", Name:\"etl-bankruptcy-test\", UID:\"50f49e1d-9a6f-4a3f-abaa-917288a29197\", APIVersion:\"sources.triggermesh.io/v1alpha1\", ResourceVersion:\"413496913\", FieldPath:\"\"}): type: 'Warning' reason: 'FailedSubscribe'...