From cdd7ad020e165fe680703b6d3319b908b682fb7a Mon Sep 17 00:00:00 2001 From: Andrew Dolgov Date: Fri, 20 Oct 2023 17:12:29 +0300 Subject: jaeger-client -> opentelemetry --- .../Trace/V1/ExportTraceServiceResponse.php | 119 +++++++++++++++++++++ 1 file changed, 119 insertions(+) create mode 100644 vendor/open-telemetry/gen-otlp-protobuf/Opentelemetry/Proto/Collector/Trace/V1/ExportTraceServiceResponse.php (limited to 'vendor/open-telemetry/gen-otlp-protobuf/Opentelemetry/Proto/Collector/Trace/V1/ExportTraceServiceResponse.php') diff --git a/vendor/open-telemetry/gen-otlp-protobuf/Opentelemetry/Proto/Collector/Trace/V1/ExportTraceServiceResponse.php b/vendor/open-telemetry/gen-otlp-protobuf/Opentelemetry/Proto/Collector/Trace/V1/ExportTraceServiceResponse.php new file mode 100644 index 000000000..27b03030a --- /dev/null +++ b/vendor/open-telemetry/gen-otlp-protobuf/Opentelemetry/Proto/Collector/Trace/V1/ExportTraceServiceResponse.php @@ -0,0 +1,119 @@ +opentelemetry.proto.collector.trace.v1.ExportTraceServiceResponse + */ +class ExportTraceServiceResponse extends \Google\Protobuf\Internal\Message +{ + /** + * The details of a partially successful export request. + * If the request is only partially accepted + * (i.e. when the server accepts only parts of the data and rejects the rest) + * the server MUST initialize the `partial_success` field and MUST + * set the `rejected_` with the number of items it rejected. + * Servers MAY also make use of the `partial_success` field to convey + * warnings/suggestions to senders even when the request was fully accepted. + * In such cases, the `rejected_` MUST have a value of `0` and + * the `error_message` MUST be non-empty. + * A `partial_success` message with an empty value (rejected_ = 0 and + * `error_message` = "") is equivalent to it not being set/present. Senders + * SHOULD interpret it the same way as in the full success case. + * + * Generated from protobuf field .opentelemetry.proto.collector.trace.v1.ExportTracePartialSuccess partial_success = 1; + */ + protected $partial_success = null; + + /** + * Constructor. + * + * @param array $data { + * Optional. Data for populating the Message object. + * + * @type \Opentelemetry\Proto\Collector\Trace\V1\ExportTracePartialSuccess $partial_success + * The details of a partially successful export request. + * If the request is only partially accepted + * (i.e. when the server accepts only parts of the data and rejects the rest) + * the server MUST initialize the `partial_success` field and MUST + * set the `rejected_` with the number of items it rejected. + * Servers MAY also make use of the `partial_success` field to convey + * warnings/suggestions to senders even when the request was fully accepted. + * In such cases, the `rejected_` MUST have a value of `0` and + * the `error_message` MUST be non-empty. + * A `partial_success` message with an empty value (rejected_ = 0 and + * `error_message` = "") is equivalent to it not being set/present. Senders + * SHOULD interpret it the same way as in the full success case. + * } + */ + public function __construct($data = NULL) { + \GPBMetadata\Opentelemetry\Proto\Collector\Trace\V1\TraceService::initOnce(); + parent::__construct($data); + } + + /** + * The details of a partially successful export request. + * If the request is only partially accepted + * (i.e. when the server accepts only parts of the data and rejects the rest) + * the server MUST initialize the `partial_success` field and MUST + * set the `rejected_` with the number of items it rejected. + * Servers MAY also make use of the `partial_success` field to convey + * warnings/suggestions to senders even when the request was fully accepted. + * In such cases, the `rejected_` MUST have a value of `0` and + * the `error_message` MUST be non-empty. + * A `partial_success` message with an empty value (rejected_ = 0 and + * `error_message` = "") is equivalent to it not being set/present. Senders + * SHOULD interpret it the same way as in the full success case. + * + * Generated from protobuf field .opentelemetry.proto.collector.trace.v1.ExportTracePartialSuccess partial_success = 1; + * @return \Opentelemetry\Proto\Collector\Trace\V1\ExportTracePartialSuccess|null + */ + public function getPartialSuccess() + { + return $this->partial_success; + } + + public function hasPartialSuccess() + { + return isset($this->partial_success); + } + + public function clearPartialSuccess() + { + unset($this->partial_success); + } + + /** + * The details of a partially successful export request. + * If the request is only partially accepted + * (i.e. when the server accepts only parts of the data and rejects the rest) + * the server MUST initialize the `partial_success` field and MUST + * set the `rejected_` with the number of items it rejected. + * Servers MAY also make use of the `partial_success` field to convey + * warnings/suggestions to senders even when the request was fully accepted. + * In such cases, the `rejected_` MUST have a value of `0` and + * the `error_message` MUST be non-empty. + * A `partial_success` message with an empty value (rejected_ = 0 and + * `error_message` = "") is equivalent to it not being set/present. Senders + * SHOULD interpret it the same way as in the full success case. + * + * Generated from protobuf field .opentelemetry.proto.collector.trace.v1.ExportTracePartialSuccess partial_success = 1; + * @param \Opentelemetry\Proto\Collector\Trace\V1\ExportTracePartialSuccess $var + * @return $this + */ + public function setPartialSuccess($var) + { + GPBUtil::checkMessage($var, \Opentelemetry\Proto\Collector\Trace\V1\ExportTracePartialSuccess::class); + $this->partial_success = $var; + + return $this; + } + +} + -- cgit v1.2.3