Skip to content
This repository was archived by the owner on Jan 21, 2026. It is now read-only.
This repository was archived by the owner on Jan 21, 2026. It is now read-only.

What to do with/about phantom child spans? #881

@AdriVanHoudt

Description

@AdriVanHoudt

I'm seeing a lot of these and while these 3 reference /messages I don't think they are directly related though

0|api      | @google-cloud/trace-agent ERROR TraceApi#createChildSpan: [[email protected]:lib/Connection.js] Creating phantom child span [mysql-query] because root span [/messages] was already closed.
0|api      | @google-cloud/trace-agent ERROR TraceApi#createChildSpan: [[email protected]:http] Creating phantom child span [metadata.google.internal] because root span [/messages] was already closed.
0|api      | @google-cloud/trace-agent ERROR TraceApi#createChildSpan: [[email protected]:src/client.js] Creating phantom child span [grpc:/google.logging.v2.LoggingServiceV2/WriteLogEntries] because root span [/messages] was already closed.

This might be related to #382 and thus also to #794
but wanted to be sure.
That endpoint does make use of tails atm.
The logging thing happens through @google-cloud/[email protected] but I can probably update that if that helps with anything :D
If there isn't anything I can do for now until the referenced issues are solved, would there be a way to turn these messages of since they are massively spammy atm

Metadata

Metadata

Assignees

Labels

api: cloudtraceIssues related to the googleapis/cloud-trace-nodejs API.triage meI really want to be triaged.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions