Some trace nodes express timestamps in seconds instead of milliseconds

[kaylareopelle]

Description

The Distributed Tracing team discovered some transaction trace node timestamps are expressed in seconds though their top-level timestamp is expressed in millisconds. We're not aware of which trace nodes may be impacted. The example shared by the DT team seems related to Datastore/statement/* nodes. All trace nodes should express their timestamps in milliseconds.

Fortunately, the backend can accommodate mismatched timestamp types and send the correct timestamps to the UI. Customers should have the accurate millisecond timestamps displayed despite what the agent sends.

Initial report (internal)

Expected Behavior

Timestamps with milliseconds are sent for transaction trace nodes.

Troubleshooting or NR Diag results

TBD

Steps to Reproduce

TBD

For Maintainers Only or Hero Triaging this bug

Suggested Priority (P1,P2,P3,P4,P5): P3
Suggested T-Shirt size (S, M, L, XL, Unknown): M

[workato-integration]

https://new-relic.atlassian.net/browse/NR-171744