From 139f514ba5d00ff2472e9ded831e1e1322b9e97e Mon Sep 17 00:00:00 2001 From: Luca Forstner Date: Tue, 6 Feb 2024 10:22:11 +0100 Subject: [PATCH] rfc(decision): Propagation Context Evolution --- README.md | 1 + text/0127-propagation-context-evolution.md | 35 ++++++++++++++++++++++ 2 files changed, 36 insertions(+) create mode 100644 text/0127-propagation-context-evolution.md diff --git a/README.md b/README.md index ca83237b..a8b90ef2 100644 --- a/README.md +++ b/README.md @@ -61,3 +61,4 @@ This repository contains RFCs and DACIs. Lost? - [0118-mobile-transactions-and-spans](text/0118-mobile-transactions-and-spans.md): Transactions and Spans for Mobile Platforms - [0123-metrics-correlation](text/0123-metrics-correlation.md): This RFC addresses the high level metrics to span correlation system - [0126-sdk-spans-aggregator](text/0126-sdk-spans-aggregator.md): SDK Span Buffer +- [0127-propagation-context-evolution](text/0127-propagation-context-evolution.md): Propagation Context Evolution diff --git a/text/0127-propagation-context-evolution.md b/text/0127-propagation-context-evolution.md new file mode 100644 index 00000000..1b5cac78 --- /dev/null +++ b/text/0127-propagation-context-evolution.md @@ -0,0 +1,35 @@ +- Start Date: 2024-02-06 +- RFC Type: decision +- RFC PR: https://github.com/getsentry/rfcs/pull/127 +- RFC Status: draft + +# Summary + +One paragraph explanation of the feature or document purpose. + +# Motivation + +Why are we doing this? What use cases does it support? What is the expected outcome? + +# Background + +The reason this decision or document is required. This section might not always exist. + +# Supporting Data + +[Metrics to help support your decision (if applicable).] + +# Options Considered + +If an RFC does not know yet what the options are, it can propose multiple options. The +preferred model is to propose one option and to provide alternatives. + +# Drawbacks + +Why should we not do this? What are the drawbacks of this RFC or a particular option if +multiple options are presented. + +# Unresolved questions + +- What parts of the design do you expect to resolve through this RFC? +- What issues are out of scope for this RFC but are known?