npmpackage.info

Gathering detailed insights and metrics for @opentelemetry/semantic-conventions

Other packages similar to @opentelemetry/semantic-conventions

@traceloop/ai-semantic-conventions

0.13.4-otel-1.28

OpenTelemetry ai-specific semantic conventions

@traceloop/instrumentation-pinecone

0.13.4-otel-1.28

OpenTelemetry instrumentation for pinecone vector DB

@traceai/fi-semantic-conventions

0.1.9

Semantic conventions for OpenTelemetry instrumentation

@traceloop/instrumentation-cohere

0.13.4-otel-1.28

Cohere Instrumentation

Gathering detailed insights and metrics for @opentelemetry/semantic-conventions

@opentelemetry/semantic-conventions - 1.34.0 | npmpackage.info

@opentelemetry/semantic-conventions

OpenTelemetry JavaScript Client

1.34.0

3,020

Apache-2.0

TypeScript

12.41 kB

1,851,845,998 6.4

Installations

npm install @opentelemetry/semantic-conventions

Developer Guide

BETA

Typescript

Yes

Module System

CommonJS, ESM

Min. Node Version

>=14

Node Version

18.20.8

NPM Version

lerna/6.6.2/node@v18.20.8+x64 (linux)

Score

99.6

Supply Chain

100

Quality

89.2

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

36

Total

3,275

Closed

619

Merged

2,620

Issues

Open

228

Total

2,104

Closed

1,876

Releases

149

experimental/v0.202.0

Updated on Jun 02, 2025

semconv/v1.34.0

Updated on May 21, 2025

semconv/v1.33.1

Updated on May 20, 2025

experimental/v0.201.1

Updated on May 19, 2025

experimental/v0.201.0

Updated on May 15, 2025

v2.0.1

Updated on May 15, 2025

View All 149 releases

Languages

TypeScript

JavaScript

Jinja

Shell

TypeScript (96.66%)

JavaScript (3.06%)

Jinja (0.19%)

Shell (0.08%)

Developer

open-telemetry

Download Statistics

Total Downloads

1,851,845,998

Last Day

1,538,444

Last Week

32,832,597

Last Month

140,448,214

Last Year

1,132,373,356

GitHub Statistics

Apache-2.0 License

3,020 Stars

2,702 Commits

899 Forks

53 Watchers

15 Branches

337 Contributors

Updated on Jun 30, 2025

Bundle Size

51.97 kB

Minified

12.41 kB

Minified + Gzipped

Bundlephobia

Maintainers

View All 337 Contributors

Package Meta Information

Latest Version

1.34.0

Package Id

@opentelemetry/semantic-conventions@1.34.0

Unpacked Size

7.33 MB

Size

1.09 MB

File Count

111

NPM Version

lerna/6.6.2/node@v18.20.8+x64 (linux)

Node Version

18.20.8

Published on

May 21, 2025

Total Downloads

Cumulative downloads

Total Downloads

1,851,845,998

Last Day

1,538,444

Compared to previous day

Last Week

-6.4%

32,832,597

Compared to previous week

Last Month

4.4%

140,448,214

Compared to previous month

Last Year

149.9%

1,132,373,356

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

@size-limit/file @size-limit/time @size-limit/webpack @types/mocha @types/node @types/sinon cross-var lerna mocha nock nyc sinon size-limit ts-node typescript

OpenTelemetry Semantic Conventions

Semantic Convention constants for use with the OpenTelemetry SDK/APIs. This document defines standard attributes for traces.

Installation

1npm install --save @opentelemetry/semantic-conventions

Import Structure

This package has 2 separate entry-points:

The main entry-point, @opentelemetry/semantic-conventions, includes only stable semantic conventions. This entry-point follows semantic versioning 2.0: it will not include breaking changes except with a change in the major version number.
The "incubating" entry-point, @opentelemetry/semantic-conventions/incubating, contains unstable semantic conventions (sometimes called "experimental") and, for convenience, a re-export of the stable semantic conventions. This entry-point is NOT subject to the restrictions of semantic versioning and MAY contain breaking changes in minor releases. See below for suggested usage of this entry-point.

Exported constants follow this naming scheme:

ATTR_${attributeName} for attributes
METRIC_${metricName} for metric names
${attributeName}_VALUE_{$enumValue} for enumerations

The ATTR, METRIC, and VALUE static strings were used to facilitate readability and filtering in auto-complete lists in IDEs.

Usage

Stable SemConv

1npm install --save @opentelemetry/semantic-conventions

1import {
2  ATTR_NETWORK_PEER_ADDRESS,
3  ATTR_NETWORK_PEER_PORT,
4  ATTR_NETWORK_PROTOCOL_NAME,
5  ATTR_NETWORK_PROTOCOL_VERSION,
6  NETWORK_TRANSPORT_VALUE_TCP,
7} from '@opentelemetry/semantic-conventions';
8
9const span = tracer.startSpan(spanName, spanOptions)
10  .setAttributes({
11    [ATTR_NETWORK_PEER_ADDRESS]: 'localhost',
12    [ATTR_NETWORK_PEER_PORT]: 8080,
13    [ATTR_NETWORK_PROTOCOL_NAME]: 'http',
14    [ATTR_NETWORK_PROTOCOL_VERSION]: '1.1',
15    [ATTR_NETWORK_TRANSPORT]: NETWORK_TRANSPORT_VALUE_TCP,
16  });

Unstable SemConv

Because the "incubating" entry-point may include breaking changes in minor versions, it is recommended that instrumentation libraries not import @opentelemetry/semantic-conventions/incubating in runtime code, but instead copy relevant definitions into their own code base. (This is the same recommendation as for other languages.)

For example, create a "src/semconv.ts" (or "lib/semconv.js" if implementing in JavaScript) file that copies from experimental_attributes.ts or experimental_metrics.ts:

1// src/semconv.ts
2export const ATTR_DB_NAMESPACE = 'db.namespace';
3export const ATTR_DB_OPERATION_NAME = 'db.operation.name';

1// src/instrumentation.ts
2import {
3  ATTR_SERVER_PORT,
4  ATTR_SERVER_ADDRESS,
5} from '@opentelemetry/semantic-conventions';
6import {
7  ATTR_DB_NAMESPACE,
8  ATTR_DB_OPERATION_NAME,
9} from './semconv';
10
11span.setAttributes({
12  [ATTR_DB_NAMESPACE]: ...,
13  [ATTR_DB_OPERATION_NAME]: ...,
14  [ATTR_SERVER_PORT]: ...,
15  [ATTR_SERVER_ADDRESS]: ...,
16})

Occasionally, one should review changes to @opentelemetry/semantic-conventions to see if any used unstable conventions have changed or been stabilized. However, an update to a newer minor version of the package will never be breaking.

Why not pin the version?

A considered alternative for using unstable exports is to pin the version. I.e., depend on an exact version, rather than on a version range.

1npm install --save-exact @opentelemetry/semantic-conventions  # Don't do this.

Then, import directly from @opentelemetry/semantic-conventions/incubating. This is not recommended.

In some languages having multiple versions of a package in a single application is not possible. This is possible in JavaScript. The primary argument against pinning this package is that it can easily lead to many copies being installed in an application's node_modules/..., which can cause significant disk usage. In a disk-constrained environment, such as AWS Lambda Layers, that can be a blocker.

Deprecations

There are two main types of deprecations in this package:

"semconv deprecations": The process of defining the OpenTelemetry Semantic Conventions sometimes involves deprecating a particular field name as conventions are stabilized. For example, the stabilization of HTTP conventions included deprecating the http.url span attribute in favor of url.full. When using this JS package, that appears as a deprecation of the ATTR_HTTP_URL export in favour of ATTR_URL_FULL.
"JS package deprecations": Independently, this JavaScript package has twice changed how it exports the Semantic Conventions constants, e.g. ATTR_HTTP_URL instead of SEMATTRS_HTTP_URL. The two older forms are still included in 1.x versions of this package for backwards compatibility. The rest of this section shows how to migrate to the latest form.

Migrating from `SEMATTRS_`, `SEMRESATTRS_`, ...

Deprecated as of @opentelemetry/semantic-conventions@1.26.0.

Before v1.26.0, constants for each semconv attribute were exported, prefixed with SEMRESATTRS_ (if defined as a Resource Attribute) or SEMATTRS_. As well, constants were exported for each value in an enumeration, of the form ${attributeName}VALUES_${enumValue}. For example:

Deprecated usage:

1import {
2  SEMRESATTRS_SERVICE_NAME,
3  SEMATTRS_HTTP_ROUTE,
4  SEMATTRS_DB_SYSTEM,
5  DBSYSTEMVALUES_POSTGRESQL
6} from '@opentelemetry/semantic-conventions';
7
8// 'service.name' resource attribute
9console.log(SEMRESATTRS_SERVICE_NAME); // migrate to 'ATTR_SERVICE_NAME'
10
11// 'http.route' attribute
12console.log(SEMATTRS_HTTP_ROUTE); // migrate to 'ATTR_HTTP_ROUTE'
13
14// 'db.system' attribute
15console.log(SEMATTRS_DB_SYSTEM); // migrate to 'ATTR_DB_SYSTEM' (in incubating [*])
16
17// 'postgresql' enum value for 'db.system' attribute
18console.log(DBSYSTEMVALUES_POSTGRESQL); // migrate to 'DB_SYSTEM_VALUE_POSTGRESQL' (in incubating [*])

See Migrated usage below.

Migrating from `SemanticAttributes.`, `SemanticResourceAttributes.`, ...

Deprecated as of @opentelemetry/semantic-conventions@1.0.0.

Before v1.0.0, constants were exported in namespace objects SemanticResourceAttributes and SemanticAttributes, and a namespace object for enumerated values for some fields (e.g. DbSystemValues for values of the 'db.system' enum). For example:

Deprecated usage:

1import {
2  SemanticAttributes,
3  SemanticResourceAttributes,
4  DbSystemValues,
5} from '@opentelemetry/semantic-conventions';
6
7// 'service.name' resource attribute
8console.log(SemanticResourceAttributes.SERVICE_NAME); // migrate to 'ATTR_SERVICE_NAME'
9
10// 'http.route' attribute
11console.log(SemanticAttributes.HTTP_ROUTE); // migrate to 'ATTR_HTTP_ROUTE'
12
13// 'db.system' attribute
14console.log(SemanticAttributes.DB_SYSTEM); // migrate to 'ATTR_DB_SYSTEM' (in incubating [*])
15
16// 'postgresql' enum value for 'db.system' attribute
17console.log(DbSystemValues.POSTGRESQL); // migrate to 'DB_SYSTEM_VALUE_POSTGRESQL' (in incubating [*])

See Migrated usage below.

Migrated usage

If using any unstable conventions, copy the relevant definitions into your code base (e.g. to "src/semconv.ts", see above):

1// src/semconv.ts
2export const ATTR_DB_SYSTEM = 'db.system' as const;
3export const DB_SYSTEM_VALUE_POSTGRESQL = "postgresql" as const;

then:

1import {
2  ATTR_SERVICE_NAME,
3  ATTR_HTTP_ROUTE,
4  METRIC_HTTP_CLIENT_REQUEST_DURATION
5} from '@opentelemetry/semantic-conventions'; // stable semconv
6import {
7  ATTR_DB_SYSTEM,
8  DB_SYSTEM_VALUE_POSTGRESQL
9} from './semconv'; // unstable semconv
10
11console.log(ATTR_SERVICE_NAME); // 'service.name'
12console.log(ATTR_HTTP_ROUTE);   // 'http.route'
13
14// Bonus: the older exports did not include metric names from semconv.
15// 'http.client.request.duration' metric name
16console.log(METRIC_HTTP_CLIENT_REQUEST_DURATION);
17
18console.log(ATTR_DB_SYSTEM);    // 'db.system'
19// 'postgresql' enum value for 'db.system' attribute
20console.log(DB_SYSTEM_VALUE_POSTGRESQL);

Useful links

For more information on OpenTelemetry, visit: https://opentelemetry.io/
For more about OpenTelemetry JavaScript: https://github.com/open-telemetry/opentelemetry-js
For help or feedback on this project, join us in GitHub Discussions

License

Apache 2.0 - See LICENSE for more information.

No vulnerabilities found.

10

Dependency-Update-Tool

Determines if the project uses a dependency update tool.

10

Maintained

Determines if the project is "actively maintained".

10

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

10

Security-Policy

Determines if the project has published a security policy.

10

SAST

Determines if the project uses static code analysis.

10

CI-Tests

Determines if the project runs tests before pull requests are merged.

10

Contributors

Determines if the project has a set of contributors from multiple organizations (e.g., companies).

3

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

Reason

dependency not pinned by hash detected -- score normalized to 3

Details

Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/benchmark.yml:20: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/benchmark.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/benchmark.yml:22: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/benchmark.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/benchmark.yml:43: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/benchmark.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/changelog.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/changelog.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/close-stale.yml:10: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/close-stale.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql-analysis.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/codeql-analysis.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql-analysis.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/codeql-analysis.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql-analysis.yml:24: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/codeql-analysis.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql-analysis.yml:27: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/codeql-analysis.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/create-or-update-release-pr.yml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/create-or-update-release-pr.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/create-or-update-release-pr.yml:43: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/create-or-update-release-pr.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/docs.yaml:12: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/docs.yaml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/docs.yaml:14: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/docs.yaml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/docs.yaml:32: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/docs.yaml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/e2e.yml:22: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/e2e.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/e2e.yml:24: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/e2e.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/lint.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/lint.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/lint.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/lint.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/peer-api.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/peer-api.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish-to-npm.yml:14: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/publish-to-npm.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish-to-npm.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/publish-to-npm.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/sbom.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/sbom.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/sbom.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/sbom.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/sbom.yml:56: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/sbom.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/sbom.yml:68: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/sbom.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/sbom.yml:72: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/sbom.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/survey-on-merged-pr.yml:20: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/survey-on-merged-pr.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/unit-test.yml:80: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/unit-test.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/unit-test.yml:82: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/unit-test.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/unit-test.yml:107: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/unit-test.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/unit-test.yml:109: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/unit-test.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/unit-test.yml:125: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/unit-test.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/unit-test.yml:136: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/unit-test.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/unit-test.yml:137: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/unit-test.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/unit-test.yml:153: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/unit-test.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/unit-test.yml:27: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/unit-test.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/unit-test.yml:29: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/unit-test.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/unit-test.yml:69: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/unit-test.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/w3c-integration-test.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/w3c-integration-test.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/w3c-integration-test.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/open-telemetry/opentelemetry-js/w3c-integration-test.yml/main?enable=pin
Warn: pipCommand not pinned by hash: integration-tests/tracecontext-integration-test.sh:13
Warn: pipCommand not pinned by hash: integration-tests/tracecontext-integration-test.sh:14
Warn: npmCommand not pinned by hash: .github/workflows/benchmark.yml:30
Warn: npmCommand not pinned by hash: .github/workflows/create-or-update-release-pr.yml:49
Warn: npmCommand not pinned by hash: .github/workflows/e2e.yml:35
Warn: npmCommand not pinned by hash: .github/workflows/e2e.yml:41
Warn: npmCommand not pinned by hash: .github/workflows/peer-api.yml:21
Warn: npmCommand not pinned by hash: .github/workflows/peer-api.yml:24
Warn: npmCommand not pinned by hash: .github/workflows/sbom.yml:22
Warn: npmCommand not pinned by hash: .github/workflows/unit-test.yml:40
Warn: npmCommand not pinned by hash: .github/workflows/unit-test.yml:46
Info: 4 out of 39 GitHub-owned GitHubAction dependencies pinned
Info: 2 out of 7 third-party GitHubAction dependencies pinned
Info: 0 out of 2 pipCommand dependencies pinned
Info: 11 out of 20 npmCommand dependencies pinned

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Signed-Releases

Determines if the project cryptographically signs release artifacts.

0

Fuzzing

Determines if the project uses fuzzing.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

6.4

/10

Last Scanned on 2025-06-30T07:48:53Z

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More

Other packages similar to @opentelemetry/semantic-conventions

Other packages similar to @opentelemetry/semantic-conventions

@opentelemetry/semantic-conventions

Installations

Developer Guide

Yes

CommonJS, ESM

>=14

18.20.8

lerna/6.6.2/node@v18.20.8+x64 (linux)

Score

Pull Requests

36

3,275

619

2,620

Issues

228

2,104

1,876

Releases

Languages

Developer

Download Statistics

GitHub Statistics

Bundle Size

51.97 kB

12.41 kB

Maintainers

Package Meta Information

Total Downloads

1,851,845,998

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

OpenTelemetry Semantic Conventions

Installation

Import Structure

Usage

Stable SemConv

Unstable SemConv

Why not pin the version?

Deprecations

Migrating from SEMATTRS_*, SEMRESATTRS_*, ...

Migrating from SemanticAttributes.*, SemanticResourceAttributes.*, ...

Migrated usage

Useful links

License

10

10

10

10

10

10

10

10

10

10

3

0

0

0

0

0

6.4

/10

Migrating from `SEMATTRS_`, `SEMRESATTRS_`, ...

Migrating from `SemanticAttributes.`, `SemanticResourceAttributes.`, ...