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

traceCustomService - not implemented #21

Open
boomsta opened this issue Feb 15, 2021 · 4 comments
Open

traceCustomService - not implemented #21

boomsta opened this issue Feb 15, 2021 · 4 comments

Comments

@boomsta
Copy link

boomsta commented Feb 15, 2021

Hi,

Seems like the traceCustomService was not implemented in the .NET SDK.
(I was able to find and use it on the JAVA SDK)

Daniel

@z1c0
Copy link
Contributor

z1c0 commented Feb 15, 2021

Hi Daniel,

that's correct but also it's by design.
Custom services are supported out-of-the-box by Dynatrace (see Define Custom Services), hence adding this feature explicitly to OneAgent SDKs was never a priority.

-Wolfgang

@boomsta
Copy link
Author

boomsta commented Feb 15, 2021

Hi Wolfgang,

Thanks for your response.
Ofcourse I'm familiar with the Custom Service mechanism in Dynatrace. But my to my understanding of this SDK tracer was to allow manipulation of how services are created, where the OOB mechanism is unable to- such as in the case of unsupported technologies, monolithic code etc.

For myself, I've found it useful in the JAVA SDK

Daniel

@z1c0
Copy link
Contributor

z1c0 commented Feb 15, 2021

Hi Daniel,

thanks for the feedback. I'll forward it to our OneAgent SDK PM @dtPaTh.
I'll keep this issue open for now to keep you posted on the status of this feature.

-Wolfgang

@boomsta
Copy link
Author

boomsta commented Feb 15, 2021

Thanks Wolfgang!

Much appreciated,
Daniel

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

2 participants