Skip to content
This repository has been archived by the owner on Dec 6, 2024. It is now read-only.

Enforce similar structure for oteps as for specs #104

Merged
merged 1 commit into from
May 4, 2020
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion text/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.