fluent-plugin-opentelemetry 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: c8f0a6c1b314b0737a832920decef09f6066acd10d578271b65edc4bc535b540
+  data.tar.gz: b5b1fd56d7c410ac7decfc50b67459277cb14d1a20b762bfdc414edaeaf1f4ef
+SHA512:
+  metadata.gz: fe86042e9aa128f24f0479332aee03e753ef82e6e04fe34b6d49cc1226753f2ca26a775d5b938cce67cf02b710f5230c8106f278cb5afc19dc69faefc439a3c5
+  data.tar.gz: 65c174366007116fd6b7fa2422914224414f5ec7c976732550d448fd219edd25c7b413e1a077ad243ab341d2e2fbd688369e1c525ba417c8418c32d5d17532b2

data/.rubocop.yml

@@ -0,0 +1,75 @@
+AllCops:
+  Exclude:
+    - 'lib/opentelemetry/**/*'
+    - 'vendor/bundle/**/*'
+  NewCops: enable
+  SuggestExtensions: false
+  TargetRubyVersion: 3.2
+
+Layout/LineLength:
+  Enabled: false
+
+Lint/UnusedMethodArgument:
+  Enabled: false
+
+Metrics:
+  Enabled: false
+
+Naming/BlockForwarding:
+  Enabled: false
+
+Naming/MethodParameterName:
+  Enabled: false
+
+Naming/VariableNumber:
+  Enabled: false
+
+Style/ArgumentsForwarding:
+  Enabled: false
+
+Style/ClassAndModuleChildren:
+  Enabled: false
+
+Style/ClassVars:
+  Exclude:
+    - 'test/**/*.rb'
+
+Style/Copyright:
+  Enabled: false
+
+Style/Documentation:
+  Enabled: false
+
+Style/FetchEnvVar:
+  Enabled: false
+
+Style/GuardClause:
+  Enabled: false
+
+Style/IfUnlessModifier:
+  Enabled: false
+
+Style/MixinUsage:
+  Exclude:
+    - 'test/helper.rb'
+
+Style/NumericLiterals:
+  Enabled: false
+
+Style/PercentLiteralDelimiters:
+  Enabled: false
+
+Style/RequireOrder:
+  Enabled: true
+
+Style/StringConcatenation:
+  Enabled: false
+
+Style/StringHashKeys:
+  Enabled: false
+
+Style/StringLiterals:
+  EnforcedStyle: double_quotes
+
+Style/TrivialAccessors:
+  Enabled: false

data/CHANGELOG.md

@@ -0,0 +1,5 @@
+## [Unreleased]
+
+## [0.1.0] - 2025-03-31
+
+- Initial release

data/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

data/README.md

@@ -0,0 +1,154 @@
+# fluent-plugin-opentelemetry
+
+[Fluentd](https://fluentd.org/) input/output plugin to forward [OpenTelemetry Protocol](https://github.com/open-telemetry/opentelemetry-proto) data.
+
+## Installation
+
+### RubyGems
+
+```sh
+gem install fluent-plugin-opentelemetry
+```
+
+### Bundler
+
+```ruby
+gem "fluent-plugin-opentelemetry"
+```
+
+And then execute:
+
+```sh
+$ bundle
+```
+
+## Configuration
+
+### Input plugin
+
+To receive data, this plugin requires `<http>` or `<grpc>` section, or both.
+
+#### Root section
+
+| parameter | type   | description          | default  |
+|-----------|--------|----------------------|----------|
+| tag       | string | The tag of the event | required |
+
+#### `<http>` section
+
+This requires to receive data via HTTP/HTTPS.
+
+| parameter | type    | description            | default   |
+|-----------|---------|------------------------|-----------|
+| bind      | string  | The address to bind to | `0.0.0.0` |
+| port      | integer | The port to listen to  | `4318`    |
+
+#### `<grpc>` section
+
+This requires to receive data via gRPC.
+
+> [!WARNING]
+> Now, gRPC feature status is experimental.
+
+| parameter | type    | description            | default   |
+|-----------|---------|------------------------|-----------|
+| bind      | string  | The address to bind to | `0.0.0.0` |
+| port      | integer | The port to listen to  | `4318`    |
+
+* `<transport>` section
+
+Refer [Config: Transport Section](https://docs.fluentd.org/configuration/transport-section)
+
+#### Example
+
+```
+<source>
+  @type opentelemetry
+  tag opentelemetry
+
+  <http>
+    bind 0.0.0.0
+    port 4318
+  </http>
+
+  <grpc>
+    bind 0.0.0.0
+    port 4317
+  </grpc>
+</source>
+```
+
+### Output plugin
+
+To send data, this plugin requires `<http>` or `<grpc>` section.
+
+#### `<http>` section
+
+This requires to send data via HTTP/HTTPS.
+
+| parameter                       | type    | description                                                    | default                 |
+|---------------------------------|---------|----------------------------------------------------------------|-------------------------|
+| endpoint                        | string  | The endpoint for HTTP/HTTPS request                            | `http://127.0.0.1:4318` |
+| proxy                           | string  | The proxy for HTTP/HTTPS request                               | `nil`                   |
+| error_response_as_unrecoverable | bool    | Raise UnrecoverableError when the response code is not SUCCESS | `true`                  |
+| retryable_response_codes        | array   | The list of retryable response codes                           | `[429, 502, 503, 504]`  |
+| read_timeout                    | integer | The read timeout in seconds                                    | `60`                    |
+| write_timeout                   | integer | The write timeout in seconds                                   | `60`                    |
+| connect_timeout                 | integer | The connect timeout in seconds                                 | `60`                    |
+
+| parameter | type   | description                               | available values | default |
+|-----------|--------|-------------------------------------------|------------------|---------|
+| compress  | enum   | The option to compress HTTP request body  | `text` / `gzip`  | `text`  |
+
+#### `<grpc>` section
+
+This requires to send data via gRPC.
+
+> [!WARNING]
+> Now, gRPC feature status is experimental.
+
+| parameter                       | type    | description                                                    | default          |
+|---------------------------------|---------|----------------------------------------------------------------|------------------|
+| endpoint                        | string  | The endpoint for HTTP/HTTPS request                            | `127.0.0.1:4317` |
+
+#### `<transport>` section
+
+| parameter              | type    | description                                    | default |
+|------------------------|---------|------------------------------------------------|---------|
+| cert_path              | string  | Specifies the path of Certificate file         | `nil`   |
+| private_key_path       | string  | Specifies the path of Private Key file         | `nil`   |
+| private_key_passphrase | string  | Specifies the public CA private key passphrase | `nil`   |
+
+| parameter   | type | description                                                 | available values               | default |
+|-------------|------|-------------------------------------------------------------|--------------------------------|---------|
+| min_version | enum | Specifies the lower bound of the supported SSL/TLS protocol | `TLS1_1` / `TLS1_2` / `TLS1_3` | `nil`   |
+| max_version | enum | The endpoint for HTTP/HTTPS request                         | `TLS1_1` / `TLS1_2` / `TLS1_3` | `nil`   |
+
+Refer [Config: Transport Section](https://docs.fluentd.org/configuration/transport-section)
+
+#### `<buffer>` section
+
+| parameter  | type   | description                                               | default |
+|------------|--------|-----------------------------------------------------------|---------|
+| chunk_keys | array  | Overwrites the default `chunk_keys` value in this plugin. | `tag`   |
+
+Refer [Config: Buffer Section](https://docs.fluentd.org/configuration/buffer-section)
+
+#### Example
+
+```
+<match opentelemetry.**>
+  @type opentelemetry
+
+  <http>
+    endpoint "https://127.0.0.1:4318"
+  </http>
+</match>
+```
+
+## Copyright
+
+* Copyright(c) 2025- Shizuo Fujita
+* License
+  * Apache License, Version 2.0
+

data/Rakefile

@@ -0,0 +1,35 @@
+# frozen_string_literal: true
+
+require "bundler/gem_tasks"
+require "rake/testtask"
+require "tmpdir"
+
+Rake::TestTask.new(:test) do |t|
+  t.libs << "test"
+  t.libs << "lib"
+  t.test_files = FileList["test/**/test_*.rb"]
+
+  # Disable displaying 'warning: literal string will be frozen in the future'
+  ENV["RUBYOPT"] = "--disable=frozen_string_literal"
+end
+
+task default: :test
+
+desc "Regenerate 'lib/opentelemetry'"
+task :"regenerate:opentelemetry" do
+  lib_path = File.expand_path("lib/opentelemetry")
+
+  rm_rf lib_path
+  cd Dir.tmpdir do
+    sh "git clone https://github.com/open-telemetry/opentelemetry-proto.git --depth 1"
+    cd "opentelemetry-proto" do
+      files = Dir.glob("opentelemetry/**/*.proto")
+
+      mkdir_p "gen"
+      sh "grpc_tools_ruby_protoc --grpc_out=./gen --ruby_out=./gen --proto_path=. #{files.join(' ')}"
+      mv "./gen/opentelemetry", lib_path
+    end
+  ensure
+    rm_rf "opentelemetry-proto"
+  end
+end

data/TODO.md

@@ -0,0 +1,108 @@
+This checklist indicates the implementation status of MUST / SHOULD in the protocol specification.
+Ref. https://github.com/open-telemetry/opentelemetry-proto/blob/main/docs/specification.md
+
+# Protocol Details
+## OTLP/gRPC
+- [ ] [MUST] All server components MUST support the following transport compression options:
+  - [ ] [MUST] No compression, denoted by none.
+  - [ ] [MUST] Gzip compression, denoted by gzip.
+
+### OTLP/gRPC Concurrent Requests
+- [ ] [SHOULD] The implementations that need to achieve high throughput SHOULD support concurrent Unary calls to achieve higher throughput.
+- [ ] [SHOULD] The client SHOULD send new requests without waiting for the response to the earlier sent requests, essentially creating a pipeline of requests that are currently in flight that are not acknowledged.
+- [ ] [SHOULD] The number of concurrent requests SHOULD be configurable.
+- [ ] [SHOULD] The client implementation SHOULD expose an option to turn on and off the waiting during a shutdown.
+
+### OTLP/gRPC Response
+- Full Success
+  - [x] [MUST] On success, the server response MUST be a Export<signal>ServiceResponse message.
+  - [x] [MUST] The server MUST leave the partial_success field unset in case of a successful response.
+  - [ ] [SHOULD] If the server receives an empty request the server SHOULD respond with success.
+- Partial Success (NOTE: Currentry, it does not support partially accepting)
+  - [ ] [MUST] The server response MUST be the same Export<signal>ServiceResponse message as in the Full Success case.
+  - [ ] [MUST] The server MUST initialize the partial_success field, and it MUST set the respective rejected_spans, rejected_data_points, rejected_log_records or rejected_profiles field with the number of spans/data points/log records/profiles it rejected.
+  - [ ] [MUST] Servers MAY also use the partial_success field to convey warnings/suggestions to clients even when the server fully accepts the request. The rejected_<signal> field MUST have a value of 0, and the error_message field MUST be non-empty.
+  - [ ] [MUST] The client MUST NOT retry the request when it receives a partial success response where the partial_success is populated.
+  - [ ] [SHOULD] The server SHOULD populate the error_message field with a human-readable error message in English.
+- Failures
+  - [ ] [MUST] Not-retryable errors indicate that telemetry data processing failed, and the client MUST NOT retry sending the same telemetry data. The client MUST drop the telemetry data.
+  - [ ] [MUST] The server MUST indicate retryable errors using code Unavailable.
+  - [ ] [SHOULD] Retryable errors indicate that telemetry data processing failed, and the client SHOULD record the error and may retry exporting the same data.
+  - [ ] [SHOULD] The client SHOULD maintain a counter of such dropped data.
+  - [ ] [SHOULD] The client SHOULD interpret gRPC status codes as retryable or not-retryable according to the following table.
+  - [ ] [SHOULD] When retrying, the client SHOULD implement an exponential backoff strategy.
+  - [ ] [SHOULD] The client SHOULD interpret RESOURCE_EXHAUSTED code as retryable only if the server signals that the recovery from resource exhaustion is possible.
+
+### OTLP/gRPC Throttling
+- [ ] [MUST] The client MUST then throttle itself to avoid overwhelming the server.
+- [ ] [MUST] To signal backpressure when using gRPC transport, the server MUST return an error with code Unavailable.
+- [ ] [SHOULD] If the server is unable to keep up with the pace of data it receives from the client then it SHOULD signal that fact to the client.
+- [ ] [SHOULD] When the client receives this signal, it SHOULD follow the recommendations outlined in documentation for RetryInfo.
+- [ ] [SHOULD] The server SHOULD choose a retry_delay value that is big enough to give the server time to recover yet is not too big to cause the client to drop data while being throttled.
+
+
+## OTLP/HTTP
+- [x] [MUST] All server components MUST support the following transport compression options:
+  - [x] [MUST] No compression, denoted by none.
+  - [x] [MUST] Gzip compression, denoted by gzip.
+- [ ] [SHOULD] Implementations that use HTTP/2 transport SHOULD fallback to HTTP/1.1 transport if HTTP/2 connection cannot be established.
+
+### Binary Protobuf Encoding
+- [x] [MUST] The client and the server MUST set "Content-Type: application/x-protobuf" request and response headers when sending binary Protobuf encoded payload.
+
+### JSON Protobuf Encoding
+- [x] [MUST] The client and the server MUST set "Content-Type: application/json" request and response headers when sending JSON Protobuf encoded payload.
+- [x] [MUST] Values of enum fields MUST be encoded as integer values.
+- [x] [MUST] OTLP/JSON receivers MUST ignore message fields with unknown names and MUST unmarshal the message as if the unknown field was not present in the payload.
+
+### OTLP/HTTP Request
+- [x] [MUST] The client MAY gzip the content and in that case MUST include "Content-Encoding: gzip" request header.
+
+### OTLP/HTTP Response
+- [x] [MUST] The response body MUST be the appropriate serialized Protobuf message.
+- [x] [MUST] The server MUST set "Content-Type: application/x-protobuf" header if the response body is binary-encoded Protobuf payload.
+- [x] [MUST] The server MUST set "Content-Type: application/json" if the response is JSON-encoded Protobuf payload.
+- [x] [MUST] The server MUST use the same "Content-Type" in the response as it received in the request.
+- Full Success
+  - [x] [MUST] On success, the server MUST respond with HTTP 200 OK
+  - [x] [MUST] The response body MUST be a Protobuf-encoded Export<signal>ServiceResponse message.
+  - [x] [MUST] The server MUST leave the partial_success field unset in case of a successful response.
+  - [x] [SHOULD] If the server receives an empty request the server SHOULD respond with success.
+- Partial Success (NOTE: Currentry, it does not support partially accepting)
+  - [ ] [MUST] If the request is only partially accepted, the server MUST respond with HTTP 200 OK.
+  - [ ] [MUST] The response body MUST be the same Export<signal>ServiceResponse message as in the Full Success case.
+  - [ ] [MUST] The server MUST initialize the partial_success field, and it MUST set the respective rejected_spans, rejected_data_points, rejected_log_records or rejected_profiles field with the number of spans/data points/log records it rejected.
+  - [ ] [MUST] Servers MAY also use the partial_success field to convey warnings/suggestions to clients even when it fully accepts the request. In such cases, the rejected_<signal> field MUST have a value of 0, and the error_message field MUST be non-empty.
+  - [ ] [MUST] The client MUST NOT retry the request when it receives a partial success response where the partial_success is populated.
+  - [ ] [SHOULD] The server SHOULD populate the error_message field with a human-readable error message in English.
+- Failures
+  - [x] [MUST] If the processing of the request fails, the server MUST respond with appropriate HTTP 4xx or HTTP 5xx status code.
+  - [ ] [MUST] The response body for all HTTP 4xx and HTTP 5xx responses MUST be a Protobuf-encoded Status message that describes the problem.
+  - [ ] [SHOULD] The Status.message field SHOULD contain a developer-facing error message as defined in Status message schema.
+  - [ ] [SHOULD] The server SHOULD use HTTP response status codes to indicate retryable and not-retryable errors for a particular erroneous situation.
+  - [x] [SHOULD] The client SHOULD honour HTTP response status codes as retryable or not-retryable.
+- Retryable Response Codes
+  - [x] [MUST] All other 4xx or 5xx response status codes MUST NOT be retried.
+  - [x] [SHOULD] The requests that receive a response status code listed in following table SHOULD be retried.
+- Bad Data
+  - [x] [MUST] If the processing of the request fails because the request contains data that cannot be decoded or is otherwise invalid and such failure is permanent, then the server MUST respond with HTTP 400 Bad Request.
+  - [x] [MUST] The client MUST NOT retry the request when it receives HTTP 400 Bad Request response.
+  - [ ] [SHOULD] The Status.details field in the response SHOULD contain a BadRequest that describes the bad data.
+- OTLP/HTTP Throttling
+  - [ ] [SHOULD] If the server receives more requests than the client is allowed or the server is overloaded, the server SHOULD respond with HTTP 429 Too Many Requests or HTTP 503 Service Unavailable.
+  - [ ] [SHOULD] The client SHOULD honour the waiting interval specified in the "Retry-After" header if it is present.
+  - [ ] [SHOULD] The "Retry-After" header is not present in the response, then the client SHOULD implement an exponential backoff strategy between retries.
+- All Other Responses
+  - [x] [SHOULD] If the server disconnects without returning a response, the client SHOULD retry and send the same request.
+  - [x] [SHOULD] The client SHOULD implement an exponential backoff strategy between retries to avoid overwhelming the server.
+
+### OTLP/HTTP Connection
+- [ ] [SHOULD] If the client cannot connect to the server, the client SHOULD retry the connection using an exponential backoff strategy between retries.
+- [ ] [SHOULD] The client SHOULD keep the connection alive between requests.
+- [ ] [SHOULD] Server implementations SHOULD accept OTLP/HTTP with binary-encoded Protobuf payload and OTLP/HTTP with JSON-encoded Protobuf payload requests on the same port and multiplex the requests to the corresponding payload decoder based on the "Content-Type" request header.
+
+### OTLP/HTTP Concurrent Requests
+- [ ] [SHOULD] To achieve higher total throughput, the client MAY send requests using several parallel HTTP connections. In that case, the maximum number of parallel connections SHOULD be configurable.
+
+# Future Versions and Interoperability
+- [ ] [MUST] When possible, the interoperability MUST be ensured between all versions of OTLP that are not declared obsolete.