Any communication way between a service OneAgent injected and a service with OneAgent SDK?

[hiroshi_kitahar]

Hi there,

I have a question about the linkage between OneAgent and OneAgent SDK.

Is there any way to monitor transactions which start from IIS with OneAgent injected and following services with OneAgent SDK?

Transactions of our prospect start from a package software based on IIS server and then travel services coded in C.

They can monitor the package software based on IIS by injecting OneAgent but they can't modify the source code.

They can monitor partial transaction flow in services written in C by using OneAgent SDK

but they are looking for a way to monitor transactions end-to-end ( from IIS package to following services in C)

* Please refer to the attached file.

In this case, is there any way to monitor end-to-end transactions?

Best regards,

Hiroshi Kitahara

[skrystosik]

If you will monitor C part of your application, transactions should connect. This is because, there is passed ID between components that can be used by dynatrace to connect transactions.

Sebastian

[hiroshi_kitahar]

Hi @sebastian k.

Thank you for your comment.

I understood transactions should connect.

If you have any idea how to connect transactions between "OneAgent-side" and "OneAgent SDK-side", would you please share your thought with me?

Best regards,

Hiroshi Kitahara

[skrystosik]

It should be enaugh for you to follow documentation of instrumentation. Connection should be established automatically on Dynatrace side. Look here:

https://github.com/Dynatrace/OneAgent-SDK-for-C#initializing-the-dynatrace-oneagent-sdk

you have byte_tag for example that will be responsible for tracking transaction in complex. It depends of kind of operation that is performed on C part of your app.

Sebastian

[Julius_Loman]

Not necessarily as it might not be HTTP communication. Depending on the protocol used, you might need to use OneAgent SDK also on the client side. If it's HTTP, transaction tracking headers will probably be there. If it's not http or a common protocol (such as various messaging systems) you might need to add the correlation metadata.