|
Dynatrace OneAgent SDK for C/C++
1.7.1.1
|
Trace calls to remote services (RMI, etc.). More...
Functions | |
| onesdk_tracer_handle_t | onesdk_outgoingremotecalltracer_create (onesdk_string_t service_method, onesdk_string_t service_name, onesdk_string_t service_endpoint, onesdk_int32_t channel_type, onesdk_string_t channel_endpoint) |
| Creates a tracer for tracing outgoing remote calls. More... | |
| void | onesdk_outgoingremotecalltracer_set_protocol_name (onesdk_tracer_handle_t tracer_handle, onesdk_string_t protocol_name) |
| Sets the name of the remoting protocol. More... | |
| onesdk_tracer_handle_t | onesdk_incomingremotecalltracer_create (onesdk_string_t service_method, onesdk_string_t service_name, onesdk_string_t service_endpoint) |
| Creates a tracer for tracing incoming remote calls. More... | |
| void | onesdk_incomingremotecalltracer_set_protocol_name (onesdk_tracer_handle_t tracer_handle, onesdk_string_t protocol_name) |
| Sets the name of the remoting protocol. More... | |
Trace calls to remote services (RMI, etc.).
When tracing remote calls, we use the following parameters
service_method service_name service_endpoint And for outgoing remote calls also
channel_type channel_endpoint service_method should be the name of the service method/operation, service_name the name of the service class/type and service_endpoint a string identifying the "instance" of that service class/type.
The channel_ parameters are described in Channel Types and Endpoints.
Further there is the optional protocol_name property that you can set to specify the used "wire protocol".
For further information, see the high level SDK documentation at https://github.com/Dynatrace/OneAgent-SDK/#remoting
org.example.services.Repository.org.example.services.Repository), but the one that you're using (calling) is located at http://art-department.example.org:12345/services/assets/repo.storeFile.service_method = storeFileservice_name = org.example.services.Repositoryservice_endpoint = http://art-department.example.org:12345/services/assets/repochannel_type = ONESDK_CHANNEL_TYPE_TCP_IPchannel_endpoint = art-department.example.org:12345MasterControlProgram.MasterControlProgram is accessed by a some custom laser communication system. service_name argument. You have to specify something though, since it's an required argument (and empty string doesn't count). One easy convention for such cases would be to simply always use the string instance. Another one would be to use the service name. Let's go with the first. service_method = derez fileservice_name = MasterControlProgramservice_endpoint = instancechannel_type = ONESDK_CHANNEL_TYPE_OTHERchannel_endpoint = onesdk_nullstr()
|
inline |
Creates a tracer for tracing incoming remote calls.
| service_method | The name of the service method. |
| service_name | The name of the service. |
| service_endpoint | The service endpoint. |
For more information see Remote Call Tracers.
|
inline |
Sets the name of the remoting protocol.
| tracer_handle | A valid incoming remote call tracer handle. |
| protocol_name | [optional] The name of the remoting protocol used to access the service. |
For more information see Remote Call Tracers.
protocol_name = onesdk_nullstr() will reset/clear any value that was set previously.
|
inline |
Creates a tracer for tracing outgoing remote calls.
| service_method | The name of the service method. |
| service_name | The name of the service. |
| service_endpoint | The service endpoint. |
| channel_type | The type of the channel used to communicate with the service. |
| channel_endpoint | [optional] The endpoint of the channel used to communicate with the service. |
For more information see Remote Call Tracers and Channel Types and Endpoints.
|
inline |
Sets the name of the remoting protocol.
| tracer_handle | A valid outgoing remote call tracer handle. |
| protocol_name | [optional] The name of the remoting protocol used to access the service. |
For more information see Remote Call Tracers.
protocol_name = onesdk_nullstr() will reset/clear any value that was set previously.
1.8.13