We recently deployed auto instrumentation of the python requests library to one of our services, and noticed that this caused our cardinality within Influx to explode. We traced the issue down to the metric http.client.duration_exemplar, and the two tags trace_id and span_id. Since the trace id and span id are unique values, I think that treating them as tags is violating the recommended schema design, and they should be set as fields instead.
We recently deployed auto instrumentation of the python
requestslibrary to one of our services, and noticed that this caused our cardinality within Influx to explode. We traced the issue down to the metrichttp.client.duration_exemplar, and the two tagstrace_idandspan_id. Since the trace id and span id are unique values, I think that treating them as tags is violating the recommended schema design, and they should be set as fields instead.