jerny-lantern

> I see that `active_support` service has appeared on the "after" trace, and that definitely seems wrong. But this indicates to me you're using Redis via ActiveSupport's cache API? >...

Update to clarify this issue. The graphql ruby gem library need to be updated to a new version to support `ddtrace` 1.1.0. After doing this graphql requests were properly assigned...

Hey @delner thank you for the response! I definitely want to follow the best practices and if `service_name` is going away I will follow y`alls guidance. One issue with removing...

Actually I think this may be because there are updates to the `graphql` gem datadog instrumentation gem that need to be applied for `ddtrace` `1.x`. We are running an older...

@delner thanks again for your follow up. This makes sense and I see in the issue #4038 linked above they added the `component` tag : https://github.com/rmosolgo/graphql-ruby/pull/4038/files#diff-dced85d92543d6c338f0cccc6ee1070f7094d702c09cdbd5990e784dc9fdcab8R21 It's technically not breaking...

by UI behavior do you mean changes in the UI that are able to automatically pick up the `component` fields? Because its no longer a `service` then I guess It...

Cool. Any eta on when the UI side for a service will make these changes for better support around the `component` field? Have many customers even migrated to this preferred...

> I don't have an ETA on the UI side yet, but I don't intend to remove the `service_name` option until we do. 👍 > I think we might be...

> > Anything I can set on my side in the meantime? > > In the interim, you could try using our Processing Pipeline feature to modify the GraphQL spans...