You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description of the problem including expected versus actual behavior:
We have a simple Koa-based Node app. It’s instrumented with Jaeger and we use the OpenTelemetry collector to send traces to the Elastic stack so that we can view trace data in Kibana. Since upgrading to 7.16.3, trace data is missing for some apps.
Actual behaviour is that no traces are visible in Kibana.
Reverting the elasticapm server to < v7.16.2 resolves this issue.
The trace pipeline mentioned above should result in the creation of two records, one in the transaction index and one in the span index. When using ElasticAPM 7.16.3, the record in the transaction index is missing. The transaction record is present with using 7.16.2 and below.
Steps to reproduce:
Please include a minimal but complete recreation of the problem,
including server configuration, agent(s) used, etc. The easier you make it
for us to reproduce it, the more likely that somebody will take the time to
look at it.
Instrument a simple Koa application with jaeger-client3.19
Run docker-compose up
Invoke a GET request on the Koa app to emit a trace.
InstrumentationLibrarySpans #0
InstrumentationLibrarySpans SchemaURL:
InstrumentationLibrary
Span #0
Trace ID : 0000000000000000fb9436dec94f751c
Parent ID : fb9436dec94f751c
ID : 5d270d86cf25bed5
Name : fetch auth token
Kind : SPAN_KIND_UNSPECIFIED
Start time : 2022-02-21 15:44:52.111 +0000 UTC
End time : 2022-02-21 15:44:52.116 +0000 UTC
Status code : STATUS_CODE_UNSET
Status message :
Span #1
Trace ID : 0000000000000000fb9436dec94f751c
Parent ID :
ID : fb9436dec94f751c
Name : health_route
Kind : SPAN_KIND_UNSPECIFIED
Start time : 2022-02-21 15:44:52.107 +0000 UTC
End time : 2022-02-21 15:44:52.12 +0000 UTC
Status code : STATUS_CODE_UNSET
Status message :
Attributes:
-> sampler.type: STRING(const)
-> sampler.param: BOOL(true)
-> path: STRING(/healthz)
I cannot see any commits between 7.16.2 and 7.16.3 that would explain this. Can you see any errors in the APM Server log or Elasticsearch log that might shed additional light?
Otherwise, if you're able to provide a standalone instrumented program so we can try to reproduce the issue, that would help speed things along.
@paulgrav if you are still experiencing this issue, please let us know and provide any additional info you can so we can try to reproduce. Closing in the meantime.
APM Server version (
apm-server version
): 7.16.3Description of the problem including expected versus actual behavior:
We have a simple Koa-based Node app. It’s instrumented with Jaeger and we use the OpenTelemetry collector to send traces to the Elastic stack so that we can view trace data in Kibana. Since upgrading to 7.16.3, trace data is missing for some apps.
Koa App > Jaeger Tracer (v3.19) thrift_binary > otel collector contrib (v0.45) otlp > elasticapm (v7.16.3) > es (v7.16.3)
I expect traces to be visible in Kibana.
Actual behaviour is that no traces are visible in Kibana.
Reverting the elasticapm server to < v7.16.2 resolves this issue.
The trace pipeline mentioned above should result in the creation of two records, one in the transaction index and one in the span index. When using ElasticAPM 7.16.3, the record in the transaction index is missing. The transaction record is present with using 7.16.2 and below.
Steps to reproduce:
Please include a minimal but complete recreation of the problem,
including server configuration, agent(s) used, etc. The easier you make it
for us to reproduce it, the more likely that somebody will take the time to
look at it.
jaeger-client
3.19
docker-compose up
Provide logs (if relevant):
docker-compose.yaml
otel.yaml
apm.yaml
logging output from otel:
span record created:
The text was updated successfully, but these errors were encountered: