http-incoming-metris has been linked with tracing. Now needs to support http-outgoing.
As part of the prior work, the name and tags has been standardised for httpclient in #548.
Left tricky parts:
the normalized url of http-outgoing-metrics VS the raw URL in the tracing
[X] done by 585
indexing the httpclient OR full search the tags in tracing logs? how can we ensure the performance?
[ ] define kind as LowCardinality
[ ] define component as LowCardinality
[ ] define tags as map and apply indexes
For http-incoming-metrics, that link SHOULD include spans with kind=SERVER only
http-incoming-metris has been linked with tracing. Now needs to support http-outgoing. As part of the prior work, the name and tags has been standardised for httpclient in #548.
Left tricky parts:
the normalized url of http-outgoing-metrics VS the raw URL in the tracing
indexing the httpclient OR full search the tags in tracing logs? how can we ensure the performance?
For http-incoming-metrics, that link SHOULD include spans with kind=SERVER only
For metrics, add
tracedmetric