Your data. Anywhere you go.

New Relic for iOS or Android


Download on the App Store    Android App on Google play


New Relic Insights App for iOS


Download on the App Store


Learn more

Close icon

Feature Idea: Distributed tracing using TCP

feature-idea
.netagent

#1

We would love to add distributed tracing to services which does not communicate with http.
In our special case TCP would be the choice.


New Relic Edit

  • I want this too
  • I have more info to share (reply below)
  • I have a solution for this

0 voters

We take feature ideas seriously and our product managers review every one when plotting their roadmaps. However, there is no guarantee this feature will be implemented. This post ensures the idea is put on the table and discussed though. So please vote and share your extra details with our team.


#2

Hey @Marvin.Henneberg - Thanks for posting the feature idea here - I just got that filed for you :smiley:


#3

Thanks @RyanVeitch! :star_struck:


#4

Can you explain more about your service, are you using WCF?

It is currently possible to manually add support for Distributed Tracing using our DT API.

https://docs.newrelic.com/docs/understand-dependencies/distributed-tracing/enable-configure/enable-distributed-tracing#agent-apis


#5

Yes the Service is using WCF and its a third party service so we don’t know the source code nor can we make any changes.


#6

And does the WCF service use the netTcpBinding?