Joel Unzain

@ifraixedes, I think I see your point. However, from a user of the library's perspective at least a panic with a corresponding error message should be there such that the...

@peterbourgon, the Prometheus go-client does not run into this specific situation (building `... string -> prometheus.Labels`) as far I see in their source code (https://github.com/prometheus/client_golang). I did, however, notice that...

Yeah, an efficient reset would be nice here for uses cases where we want to initialize the query object given a map and then just query for specific values given...

Remaining task: ``` Add a metric to see how often we are modifying the wrp in that function. We may want to move the modification of the wrp into talaria...

Just looked at the `modified_wrp_count` metric values from production and the majority of WRPs have the transaction UUIDs missing and a few have both that and the WRP.contentType as empty....

This depends on wrp message obj being validated.

We expect to see these errors until https://github.com/xmidt-org/wrp-go/issues/25 is fixed and ported into caduceus.

@kcajmagic has a script to delete releases. Perhaps, we should modify the script to remove those with the prefix in this^ title.

So if we want to log tracing information for requests made to devices, a better place to pass a `LoggerFunc` (similar to https://github.com/xmidt-org/argus/blob/main/chrysom/client.go#L169) might be the `wrpHandler` https://github.com/xmidt-org/talaria/blob/main/WRPHandler.go#L29 FYI: All...

On a slight tangent, @utsavbatra5. When adding the server-side OpenTelemetry integration to talaria, would you be interested in trying out the approach described here https://github.com/xmidt-org/tr1d1um/issues/202? If you need more information,...