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
If I understand correctly, when configured with OpenTelemetry, HotChocolate currently creates a ResolveFieldValue activity/span for all async field resolvers, but not for sync field resolvers, presumably to reduce noise and data ingestion costs for the common case of sync resolvers.
I have many fields that are async (ValueTask) only because they perform some async locking. These generally complete synchronously in under 1ms. I would like to exclude these from being exported, just as if they were sync fields.
The solution you'd like
I have tried for several hours now to find a way of not exporting these, using processors and whatnot, but I haven't gotten anywhere. It would be great if HotChocolate provided some way of filtering trace telemetry from the source.
The text was updated successfully, but these errors were encountered:
Product
Hot Chocolate
Is your feature request related to a problem?
If I understand correctly, when configured with OpenTelemetry, HotChocolate currently creates a
ResolveFieldValue
activity/span for all async field resolvers, but not for sync field resolvers, presumably to reduce noise and data ingestion costs for the common case of sync resolvers.I have many fields that are async (ValueTask) only because they perform some async locking. These generally complete synchronously in under 1ms. I would like to exclude these from being exported, just as if they were sync fields.
The solution you'd like
I have tried for several hours now to find a way of not exporting these, using processors and whatnot, but I haven't gotten anywhere. It would be great if HotChocolate provided some way of filtering trace telemetry from the source.
The text was updated successfully, but these errors were encountered: