Implement some of the stable database semantic conventions#11575
Implement some of the stable database semantic conventions#11575trask merged 95 commits intoopen-telemetry:mainfrom
Conversation
|
I will add 'error.type' and the opt-in |
|
status update, still need to:
|
22f2903 to
038fbec
Compare
| } | ||
|
|
||
| @SuppressWarnings("unchecked") | ||
| public static <T> AttributeKey<T> getAttributeKey(AttributeKey<T> oldKey) { |
There was a problem hiding this comment.
I don't remember which way we did this for the http but mapping from new to old might be preferable here as it reduces the need to suppress deprecation warnings when old attributes are used (after we update the semconv jars). For http this might not have been an issue because most of the http tests are in a base class so we needed to suppress the warnings only here.
There was a problem hiding this comment.
we wouldn't be able to map db.collection.name since multiple attributes were consolidated into this one attribute
map.put(DB_SQL_TABLE, DB_COLLECTION_NAME);
map.put(DB_CASSANDRA_TABLE, DB_COLLECTION_NAME);
map.put(DB_MONGODB_COLLECTION, DB_COLLECTION_NAME);
map.put(DB_COSMOSDB_CONTAINER, DB_COLLECTION_NAME);
There was a problem hiding this comment.
I think we can find ways to resolve the multiple mapping issue. This is just an idea, we can tackle this later if it seems to be worth the effort.
…metry#11575) Co-authored-by: Trask Stalnaker <[email protected]>
…metry#11575) Co-authored-by: Trask Stalnaker <[email protected]>
Protyping parts of open-telemetry/semantic-conventions#1090