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've hesitated to add array-based attributes (e.g. db.collection.names) in the past due to concern that they aren't well supported today in metrics backends.
Another recent example is db.cosmosdb.regions_contacted.
Capturing these as attributes on metrics gives users the chance to aggregate across metrics where db.collection.names contains X, or db.cosmosdb.regions_contacted contains Y, which seems to be useful.
Another benefit of including these attributes on metrics is that they can be meaningful characteristics to split time series on.
The text was updated successfully, but these errors were encountered:
We've hesitated to add array-based attributes (e.g.
db.collection.names
) in the past due to concern that they aren't well supported today in metrics backends.Another recent example is
db.cosmosdb.regions_contacted
.Capturing these as attributes on metrics gives users the chance to aggregate across metrics where
db.collection.names
containsX
, ordb.cosmosdb.regions_contacted
containsY
, which seems to be useful.Another benefit of including these attributes on metrics is that they can be meaningful characteristics to split time series on.
The text was updated successfully, but these errors were encountered: