Closed ZNeumann closed 2 months ago
Test Suite | Status | Result |
---|---|---|
Multiverse | :white_check_mark: | 7/7 passing |
SOAK | :x: | 55/56 passing |
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 78.13%. Comparing base (
b4609db
) to head (87d5da8
). Report is 1 commits behind head on dev.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Does OTLP collector expect lowercase only letters in the trace id (similar to w3c traceparent header spec)?
All trace_ids that we create within the agent are lowercase, so this should not be important.
Could we use get_linking_metadata()
in some integration tests to verify the trace.id
is 16 or 32 characters based on the setting of the INI value?
Could we use
get_linking_metadata()
in some integration tests to verify thetrace.id
is 16 or 32 characters based on the setting of the INI value?
added in 5afcf9f
Could tests for
nr_distributed_trace_set_trace_id
be added toaxiom/tests/test_distributed_trace.c
? There exist tests fornr_txn_create_w3c_traceparent_header
inaxiom/tests/test_txn.c
which ensuresnr_distributed_trace_create_w3c_traceparent_header
padding works. But there don't exists explicit tests fornr_distributed_trace_set_trace_id
padding covering 3 cases:
- input is null
- input is < 32
- input is >= 32
Adressed in 87b7a85
https://github.com/newrelic/newrelic-php-agent/pull/929#discussion_r1657754748
This probably needs its own test(s).
W3C compliant headers will have a 32 char trace id. We generate these 32 character ids when we create a header by appending 0's in front of our 16 char trace id.
This PR takes that same concept, but optionally does so for when we store the trace id, not just when we are sending a header.