Closed xwgao closed 1 year ago
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers
. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
This issue has been closed as inactive because it has been stale for 120 days with no activity.
Component(s)
processor/metricstransform
What happened?
Description
I enabled auto-instrumentation for my microservices in Node.js. And I used spanmetrics connector and metricstransform processor in my otel collector to generate metrics (duration and error) for microservices in my application. And I also configured my otel collector to export traces and metrics to Instana server via OTLP protocol. If I added the below transformation in metricstransform processor as below, I would not see the traces for endpoint
/api/v2/document-query/query
on Instana dashboard. After removing this transformation, I can see the traces for endpoint/api/v2/document-query/query
on Instana dashboard.Steps to Reproduce
See the details in ##Description
Expected Result
I can see the traces for endpoint
/api/v2/document-query/query
on Instana dashboard even if I added the following transformation in metricstransform processor as below.Actual Result
I can not see the traces for endpoint
/api/v2/document-query/query
on Instana dashboard if I added the following transformation in metricstransform processor as below.Collector version
v0.75.0
Environment information
Environment
OpenShift Container Platform 4.10
OpenTelemetry Collector configuration