You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using APM Automatic Instrumentation (ADO.NET) for database related tracing and also using DD_TRACE_SERVICE_MAPPING to map database service names accross multiple services like this:
application_db (service1_db, service2_db, ...)
service1
service2
...
Which is quite nice, as it groups all the queries shared accross different services.
But here comes the catch: No matter which database (host) gets instrumented - they all get grouped into one service.
This is not really caused by the mapping itself: service1 talks to databaseHost1 and databaseHost2
We would like to split services by network.destination.ip to actually see each database host as a own service.
Is there any existing solution for this that we are missing?
Or any plans in the future to enable this?
Thank you.
The text was updated successfully, but these errors were encountered:
We are using APM Automatic Instrumentation (ADO.NET) for database related tracing and also using
DD_TRACE_SERVICE_MAPPING
to map database service names accross multiple services like this:Which is quite nice, as it groups all the queries shared accross different services.
But here comes the catch: No matter which database (host) gets instrumented - they all get grouped into one service.
This is not really caused by the mapping itself: service1 talks to databaseHost1 and databaseHost2
We would like to split services by
network.destination.ip
to actually see each database host as a own service.Is there any existing solution for this that we are missing?
Or any plans in the future to enable this?
Thank you.
The text was updated successfully, but these errors were encountered: