[Bug]: Trace ids are no longer cascaded on next spans after Tracer::extract(Format::TEXT_MAP)
& using context on startxSpan
#2726
Labels
馃悰 bug
Something isn't working
Bug report
馃憢
We use some custom tooling to facilitate better insights through AMQP processes where the resource types are the type of messages, rather than e.g.
basic_deliver
After the upgrade the given trace ids are no longer cascaded onto next spans after
$spanContext = Tracer::extract(Format::TEXT_MAP, [...])
and use them onTrager::startActiveSpan('operation', ["references" => Reference::create(Reference::CHILD_OF, $spanContext)
; We already triedstartRootSpan
as an alternative too.The given span context is created with
::inject(TEXT_MAP)
However the resources are still being registered in the service catalog, but there are no traces at all anymore.
We don't seem to understand what changed, and which changes we should make to resolve those issues again.
If we were to publish a message without tracing context to be used, it does create the traces correctly again.
And when debugging a bit more it seems that there is a new trace id created and the given one is being ignored
Implementation details
Trace Debug
Would you be able to give us any pointers on what can adjust?
This same code structure did work for us pre-1.x.
Thank you!
PHP version
8.1.x
Tracer or profiler version
1.1.0
Installed extensions
ddtrace
is on version 1.1.0[PHP Modules]
apcu
bcmath
bz2
calendar
Core
ctype
curl
datadog-profiling
date
ddappsec
ddtrace
dom
exif
fileinfo
filter
ftp
gd
gettext
gmp
hash
iconv
igbinary
imagick
imap
intl
json
libxml
mbstring
mcrypt
memcached
mysqli
mysqlnd
OAuth
openssl
pcntl
pcre
PDO
pdo_mysql
PDO_ODBC
pdo_pgsql
pdo_sqlite
pgsql
Phar
posix
readline
redis
Reflection
session
shmop
SimpleXML
soap
sockets
sodium
SPL
sqlite3
standard
sysvmsg
sysvsem
sysvshm
tidy
tokenizer
uuid
xml
xmlreader
xmlwriter
xsl
Zend OPcache
zip
zlib
[Zend Modules]
Zend OPcache
datadog-profiling
ddappsec
ddtrace
Output of
phpinfo()
Our configuration
Upgrading from
0.99
The text was updated successfully, but these errors were encountered: