From 0806e465e0601869e4ce10a247172bf52854df0b Mon Sep 17 00:00:00 2001 From: Billy Vong Date: Thu, 5 Feb 2026 10:19:36 -0500 Subject: [PATCH] fix: typo in RFC summary for Sentry semantic conventions Corrected a typo in the summary regarding the current time of semantic conventions. --- text/0116-sentry-semantic-conventions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/text/0116-sentry-semantic-conventions.md b/text/0116-sentry-semantic-conventions.md index 09d06d89..7c162557 100644 --- a/text/0116-sentry-semantic-conventions.md +++ b/text/0116-sentry-semantic-conventions.md @@ -6,7 +6,7 @@ # Summary -The purpose of this RFC is to formalize the a set of semantic conventions in Sentry, aligning with [OpenTelemetry's semantic conventions](https://opentelemetry.io/docs/concepts/semantic-conventions/). At the curren time, these semantic conventions are meant to apply to spans, breadcrumbs, and metrics, but not to errors/transactions/replays/crons. This may change in the future. +The purpose of this RFC is to formalize the a set of semantic conventions in Sentry, aligning with [OpenTelemetry's semantic conventions](https://opentelemetry.io/docs/concepts/semantic-conventions/). At the current time, these semantic conventions are meant to apply to spans, breadcrumbs, and metrics, but not to errors/transactions/replays/crons. This may change in the future. These will be a standardized naming scheme for operations and data that will be shared across the SDKs, ingest, and the product. We will implement the semantic conventions via a versioned JSON schema that is published as packages for Python, JavaScript, and Rust. This allows us to have a single source of truth for the semantic conventions, and also allows us to generate code for all parts of the stack (ingest, frontend, backend, data pipelines) that need to be aware of this.