Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unify service.instance.id? #324

Open
Seikilos opened this issue Feb 23, 2024 · 0 comments
Open

Unify service.instance.id? #324

Seikilos opened this issue Feb 23, 2024 · 0 comments

Comments

@Seikilos
Copy link

Seikilos commented Feb 23, 2024

I noticed that there are two ways, how 3rd party libraries (the same is true for OTELs Node SDK) emit instance.id and other fields.

For instance does the otel logger create a property called "service.instance.id"

image

But OTELs spans create an event for this field:

image

Unfortunately this is a different column in hyperdx.
The first one is service.instance.id, the second one is process.tag.service.instance.id

Annoyingly the same is true for the service name field. I have always to filter for service.name:"THE_SERVICE" OR service:"THE_SERVICE" even though Hyperdx shows both fields in the Service column when there is no filter applied.

While I know this is an implementers issue, I would recommend thinking about fixing this on hyperdx side to massively improve usability. Frankly this fragmented approach in node really makes tracing nearly impossible since I keep forgetting that filtering for one service may return incomplete results because some parts of the same service do things differently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant