@opentelemetry/semantic-conventions - npm Package Compare versions

Comparing version 0.23.1-alpha.23 to 0.23.1-alpha.24

build/esm/resource/index.d.ts

@@ -1,2 +0,2 @@
-export * from './ResourceAttributes';
+export * from './SemanticResourceAttributes';
 //# sourceMappingURL=index.d.ts.map

build/esm/resource/index.js

@@ -16,3 +16,3 @@ /*
  */
-export * from './ResourceAttributes';
+export * from './SemanticResourceAttributes';
 //# sourceMappingURL=index.js.map

build/esm/trace/SemanticAttributes.d.ts

 export declare const SemanticAttributes: {
     /**
+    * The full invoked ARN as provided on the `Context` passed to the function (`Lambda-Runtime-Invoked-Function-Arn` header on the `/runtime/invocation/next` applicable).
+    *
+    * Note: This may be different from `faas.id` if an alias is involved.
+    */
+    AWS_LAMBDA_INVOKED_ARN: string;
+    /**
     * An identifier for the database management system (DBMS) product being used. See below for a list of well-known identifiers.
@@ -484,7 +490,11 @@ */
     /**
-    * The full name of the service being called, including its package name, if applicable.
+    * The full (logical) name of the service being called, including its package name, if applicable.
+    *
+    * Note: This is the logical name of the service from the RPC interface perspective, which can be different from the name of any implementing class. The `code.namespace` attribute may be used to store the latter (despite the attribute name, it may include a class name; e.g., class with method actually executing the call on the server side, RPC client stub class on the client side).
     */
     RPC_SERVICE: string;
     /**
-    * The name of the method being called, must be equal to the $method part in the span name.
+    * The name of the (logical) method being called, must be equal to the $method part in the span name.
+    *
+    * Note: This is the logical name of the method from the RPC interface perspective, which can be different from the name of any implementing method/function. The `code.function` attribute may be used to store the latter (e.g., method actually executing the call on the server side, RPC client stub method on the client side).
     */
@@ -501,6 +511,2 @@ RPC_METHOD: string;
     /**
-    * `method` property from request. Unlike `rpc.method`, this may not relate to the actual method being called. Useful for client-side traces since client does not know what will be called on the server.
-    */
-    RPC_JSONRPC_METHOD: string;
-    /**
     * `id` property of request or response. Since protocol allows id to be int, string, `null` or missing (for notifications), value is expected to be cast to string for simplicity. Use empty string in case of `null` value. Omit entirely if this is a notification.
@@ -507,0 +513,0 @@ */

build/esm/trace/SemanticAttributes.js

@@ -19,2 +19,8 @@ /*
     /**
+    * The full invoked ARN as provided on the `Context` passed to the function (`Lambda-Runtime-Invoked-Function-Arn` header on the `/runtime/invocation/next` applicable).
+    *
+    * Note: This may be different from `faas.id` if an alias is involved.
+    */
+    AWS_LAMBDA_INVOKED_ARN: 'aws.lambda.invoked_arn',
+    /**
     * An identifier for the database management system (DBMS) product being used. See below for a list of well-known identifiers.
@@ -501,7 +507,11 @@ */
     /**
-    * The full name of the service being called, including its package name, if applicable.
+    * The full (logical) name of the service being called, including its package name, if applicable.
+    *
+    * Note: This is the logical name of the service from the RPC interface perspective, which can be different from the name of any implementing class. The `code.namespace` attribute may be used to store the latter (despite the attribute name, it may include a class name; e.g., class with method actually executing the call on the server side, RPC client stub class on the client side).
     */
     RPC_SERVICE: 'rpc.service',
     /**
-    * The name of the method being called, must be equal to the $method part in the span name.
+    * The name of the (logical) method being called, must be equal to the $method part in the span name.
+    *
+    * Note: This is the logical name of the method from the RPC interface perspective, which can be different from the name of any implementing method/function. The `code.function` attribute may be used to store the latter (e.g., method actually executing the call on the server side, RPC client stub method on the client side).
     */
@@ -518,6 +528,2 @@ RPC_METHOD: 'rpc.method',
     /**
-    * `method` property from request. Unlike `rpc.method`, this may not relate to the actual method being called. Useful for client-side traces since client does not know what will be called on the server.
-    */
-    RPC_JSONRPC_METHOD: 'rpc.jsonrpc.method',
-    /**
     * `id` property of request or response. Since protocol allows id to be int, string, `null` or missing (for notifications), value is expected to be cast to string for simplicity. Use empty string in case of `null` value. Omit entirely if this is a notification.
@@ -524,0 +530,0 @@ */

build/src/resource/index.d.ts

@@ -1,2 +0,2 @@
-export * from './ResourceAttributes';
+export * from './SemanticResourceAttributes';
 //# sourceMappingURL=index.d.ts.map

build/src/resource/index.js

@@ -28,3 +28,3 @@ "use strict";
  */
-__exportStar(require("./ResourceAttributes"), exports);
+__exportStar(require("./SemanticResourceAttributes"), exports);
 //# sourceMappingURL=index.js.map

build/src/trace/SemanticAttributes.d.ts

 export declare const SemanticAttributes: {
     /**
+    * The full invoked ARN as provided on the `Context` passed to the function (`Lambda-Runtime-Invoked-Function-Arn` header on the `/runtime/invocation/next` applicable).
+    *
+    * Note: This may be different from `faas.id` if an alias is involved.
+    */
+    AWS_LAMBDA_INVOKED_ARN: string;
+    /**
     * An identifier for the database management system (DBMS) product being used. See below for a list of well-known identifiers.
@@ -484,7 +490,11 @@ */
     /**
-    * The full name of the service being called, including its package name, if applicable.
+    * The full (logical) name of the service being called, including its package name, if applicable.
+    *
+    * Note: This is the logical name of the service from the RPC interface perspective, which can be different from the name of any implementing class. The `code.namespace` attribute may be used to store the latter (despite the attribute name, it may include a class name; e.g., class with method actually executing the call on the server side, RPC client stub class on the client side).
     */
     RPC_SERVICE: string;
     /**
-    * The name of the method being called, must be equal to the $method part in the span name.
+    * The name of the (logical) method being called, must be equal to the $method part in the span name.
+    *
+    * Note: This is the logical name of the method from the RPC interface perspective, which can be different from the name of any implementing method/function. The `code.function` attribute may be used to store the latter (e.g., method actually executing the call on the server side, RPC client stub method on the client side).
     */
@@ -501,6 +511,2 @@ RPC_METHOD: string;
     /**
-    * `method` property from request. Unlike `rpc.method`, this may not relate to the actual method being called. Useful for client-side traces since client does not know what will be called on the server.
-    */
-    RPC_JSONRPC_METHOD: string;
-    /**
     * `id` property of request or response. Since protocol allows id to be int, string, `null` or missing (for notifications), value is expected to be cast to string for simplicity. Use empty string in case of `null` value. Omit entirely if this is a notification.
@@ -507,0 +513,0 @@ */

build/src/trace/SemanticAttributes.js

@@ -22,2 +22,8 @@ "use strict";
     /**
+    * The full invoked ARN as provided on the `Context` passed to the function (`Lambda-Runtime-Invoked-Function-Arn` header on the `/runtime/invocation/next` applicable).
+    *
+    * Note: This may be different from `faas.id` if an alias is involved.
+    */
+    AWS_LAMBDA_INVOKED_ARN: 'aws.lambda.invoked_arn',
+    /**
     * An identifier for the database management system (DBMS) product being used. See below for a list of well-known identifiers.
@@ -504,7 +510,11 @@ */
     /**
-    * The full name of the service being called, including its package name, if applicable.
+    * The full (logical) name of the service being called, including its package name, if applicable.
+    *
+    * Note: This is the logical name of the service from the RPC interface perspective, which can be different from the name of any implementing class. The `code.namespace` attribute may be used to store the latter (despite the attribute name, it may include a class name; e.g., class with method actually executing the call on the server side, RPC client stub class on the client side).
     */
     RPC_SERVICE: 'rpc.service',
     /**
-    * The name of the method being called, must be equal to the $method part in the span name.
+    * The name of the (logical) method being called, must be equal to the $method part in the span name.
+    *
+    * Note: This is the logical name of the method from the RPC interface perspective, which can be different from the name of any implementing method/function. The `code.function` attribute may be used to store the latter (e.g., method actually executing the call on the server side, RPC client stub method on the client side).
     */
@@ -521,6 +531,2 @@ RPC_METHOD: 'rpc.method',
     /**
-    * `method` property from request. Unlike `rpc.method`, this may not relate to the actual method being called. Useful for client-side traces since client does not know what will be called on the server.
-    */
-    RPC_JSONRPC_METHOD: 'rpc.jsonrpc.method',
-    /**
     * `id` property of request or response. Since protocol allows id to be int, string, `null` or missing (for notifications), value is expected to be cast to string for simplicity. Use empty string in case of `null` value. Omit entirely if this is a notification.
@@ -527,0 +533,0 @@ */

package.json

 {
   "name": "@opentelemetry/semantic-conventions",
-  "version": "0.23.1-alpha.23+884d20ab",
+  "version": "0.23.1-alpha.24+3bc34528",
   "description": "OpenTelemetry semantic conventions",
@@ -58,3 +58,3 @@ "main": "build/src/index.js",
   },
-  "gitHead": "884d20ab417bf0283ec84a72b9a0fae8ebcb82a1"
+  "gitHead": "3bc3452814e30274d7eea1f3c9da968b88b1a197"
 }

New alerts

Manifest confusion

Supply chain risk

This package has inconsistent metadata. This could be malicious or caused by an error when publishing the package.

Found 1 instance in 1 package

Fixed alerts

Manifest confusion

Supply chain risk

This package has inconsistent metadata. This could be malicious or caused by an error when publishing the package.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

263274

increased by4.16%

Lines of code

5260

increased by2.49%

No dependency changes