You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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"
But OTELs spans create an event for this field:
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.
The text was updated successfully, but these errors were encountered:
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"
But OTELs spans create an event for this field:
Unfortunately this is a different column in hyperdx.
The first one is
service.instance.id
, the second one isprocess.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 theService
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.
The text was updated successfully, but these errors were encountered: