David Ashpole comments

Results 617 comments of


                                            David Ashpole

Add tracing instrumentation documentation

/assign @shivanshu1333

Add resourcequota cpu and memory metrics

I see a mixture of updowncounters and gauges. Seems like they should all use the same instrument, given they are all usage and limit, but with different units. I see...

otelhttp: Allow setting start time using context

@open-telemetry/opamp-go-approvers this needs one more review if anyone has time

labels_allow_list and annotations_allow_list wildcards clobber resource specific configuration

/assign @rexagod /triage accepted

Document the bridge that allows for client_golang instrumented code to push with OpenTelemetry OTLP

@bwplotka were you thinking of an example, or just documentation? If documentation, where do you think this belongs?

Metrics Anomaly Detector

@rexagod Is this planned for 1.30? If it is, we need to add the 1.30 milestone, and the `lead-opted-in` label

Metrics Anomaly Detector

@rexagod do you think you will get to this in the 1.33 timeframe?