Skip to content

Commit

Permalink
Enforce similar structure for oteps as for specs (open-telemetry#104)
Browse files Browse the repository at this point in the history
Signed-off-by: Bogdan Drutu <[email protected]>
  • Loading branch information
bogdandrutu authored May 4, 2020
1 parent 2819ca9 commit 2feafdd
Show file tree
Hide file tree
Showing 16 changed files with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion oteps/0007-no-out-of-band-reporting.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ Here is a list of decisions and trade-offs related to supporting out-of-band rep
* Example in the create metric we need to allow users to specify the resource, see
[here][create-metric]. The developer that writes the instrumentation has no knowledge about where
the monitored resource is deployed so there is no way to configure the right resource.
2. [RFC](./0002-remove-spandata.md) removes support to report SpanData.
2. [RFC](./trace/0002-remove-spandata.md) removes support to report SpanData.
* This will require that the trace API has to support all the possible fields to be configured
via the API, for example need to allow users to set a pre-generated `SpanId` that can be avoided
if we do not support out-of-band reporting.
Expand Down
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.

0 comments on commit 2feafdd

Please sign in to comment.