We need to decide on a pattern for system-specific client/server metrics.
The pattern for client/server is {domain}.client.metric_name and {domain}.server.metric_name (e.g. http.client.request.duration and http.server.request.duration).
For db/messaging/rpc/genai/etc, we'll need to take into account system-specific metrics and have a consistent place for the system identifier.
E.g.
db.cosmosdb.client.* and db.cosmosdb.server.*
vsdb.client.cosmosdb.* and db.server.cosmosdb.*
Option 1 (*.{system}.client.*) is aligned better with attribute naming pattern ({domain}.{system}.attribute_name).
Option 2 (*.client.{system}.*) is aligned better with metric naming pattern ({domain}.client.{system}.metric_name).
There is no obvious advantage of one options versus the other, but keeping things consistent is important. Let's pick one option and document it as a guidance.
We need to decide on a pattern for system-specific client/server metrics.
The pattern for client/server is
{domain}.client.metric_nameand{domain}.server.metric_name(e.g.http.client.request.durationandhttp.server.request.duration).For db/messaging/rpc/genai/etc, we'll need to take into account system-specific metrics and have a consistent place for the system identifier.
E.g.
db.cosmosdb.client.*anddb.cosmosdb.server.*vs
db.client.cosmosdb.*anddb.server.cosmosdb.*Option 1 (
*.{system}.client.*) is aligned better with attribute naming pattern ({domain}.{system}.attribute_name).Option 2 (
*.client.{system}.*) is aligned better with metric naming pattern ({domain}.client.{system}.metric_name).There is no obvious advantage of one options versus the other, but keeping things consistent is important. Let's pick one option and document it as a guidance.