Description
Similar to #621, we need to improve the granularity of backend dependencies that are NoSQL-based or messaging-based.
This, in particular, means that service.target.type, service.target.name need to be set properly and also the old field destination.service.resource needs to be updated accordingly.
The detailed changes are described in these spec changes:
Summary of changes
DBs
- For Cassandra, define
db.instance to the Keyspace name (if available)
- For MongoDB, define
db.instance to the Database name (if available)
- For Elasticsearch, define
db.instance as the Cluster name (if available, with heuristic).
- For Redis do not set the
db.instance / service.target.name fields
- For Memcached do not set the
db.instance / service.target.name fields
- For any other NoSQL database / store follow the spec
Messaging
- For azurequeue : use
queue name
- For azureservicebus : use
queue name or topic name
- Other: use already captured
queue name
Agent Issues
Description
Similar to #621, we need to improve the granularity of backend dependencies that are NoSQL-based or messaging-based.
This, in particular, means that
service.target.type,service.target.nameneed to be set properly and also the old fielddestination.service.resourceneeds to be updated accordingly.The detailed changes are described in these spec changes:
Summary of changes
DBs
db.instanceto the Keyspace name (if available)db.instanceto the Database name (if available)db.instanceas the Cluster name (if available, with heuristic).db.instance/service.target.namefieldsdb.instance/service.target.namefieldsMessaging
queue namequeue nameortopic namequeue nameAgent Issues