Process group for OpenTelemetry service

[matcap]

Hi, here is my current situation: I have a .NET 8 service on my machine that sends OpenTelemetry traces to the local OneAgent endpoint (localhost:14499).

On Dynatrace though, I see two separate services, one of type Unified Service (the one derived from OpenTelemetry) that has no process group, and another one of type Web request service that has a process group assigned.

How can I make sure that I only see one service with the correct process group?

Thanks in advance

[marco_irmer]

It sounds like your .NET 8 service might be instrumented both natively by the OneAgent (creating the Web request service) and also via OpenTelemetry (creating the Unified Service). If this is the case, and only OpenTelemetry is desirable, then I believe you would need to change the OneAgent settings on your host so that it won't monitor those processes.

[matcap]

Exactly, I'm sorry but I forgot to mention that I already disabled Deep Monitoring for my service in OneAgent settings

[marco_irmer]

I would say the next step may me to confirm that deep monitoring has been successfully deactivated, including recycling the process(es) if not already done. You may also wish to examine some of the traces/spans coming in under the Web request service to confirm whether they in fact originate from OneAgent and not OpenTelemetry. If they are coming from OneAgent, then perhaps support might need to be involved to help with fully deactivating the OneAgent-based service monitoring.

[matcap]

Yes, I can confirm that deep monitoring is disabled. The traces are coming from OpenTelemetry (see image) and are sent through the OneAgent localhost:14499 endpoint, and this is exactly what I want.
The only missing thing is the associated process group.

[Julius_Loman · Accepted solution]

This is achieved with OpenTelemetry resource attributes. You need to add the process group ID as resource attributes to your services. As traces are ingested using OTEL, Dynatrace cannot know which process those traces originate from. 

if you can modify the app code and Otel initialization, the best way is to use the metadata for that, see this. But you need the OneAgent module to load.
If this is not possible for any reason, and you can set resource attributes by configuration only, then you can get the process group ID from Dynatrace UI, for example,and set it manually in the app configuration.

[matcap]

Thanks, this solution is working as I expected