Meaning encoding the REST OTLP packets as protobuf fields ain't happening

@Srikanth Chekuri are there any possible solutions on this can be done?

@Mac Wynkoop the encoding of the data and sending it is taken care by exporter. Are you using any OTLP http exporter or are you trying to write your own exporter?

It's an extremely basic OTLP exporter that yes, I implemented in the Google Apps Script. I was trying to initially just send the data over in normal JSON formatting, not realizing it had to be protobuf-encoded JSON data. So I'm currently just having it console.log(spanpayload) to the Google Stackdriver logging system. It kind of shows the same data, just not really OTLP-compliant.

I was trying to initially just send the data over in normal JSON formatting, not realizing it had to be protobuf-encoded JSON data

Just want to make sure I understand it, by

protobuf-encoded

JSON data, you mean the JSON payload that is OTLP compliant right? Have you looked at https://www.npmjs.com/package/@opentelemetry/exporter-trace-otlp-http?

Hey @Srikanth Chekuri I am picking this effort back up, to get an OTLP exporter in my Google Apps Script. Currently trying to transpile the npm package in with Webpack.