-
Notifications
You must be signed in to change notification settings - Fork 821
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[opentelemetry-exporter]: provide an option for max attribute value (currently it's hardcoded to 128 bytes) #934
Comments
The exporter is changing to use the OTLP format in #901. I think we should address this after that merges? |
I think this has already been addressed in #901. This limitations/restrictions were there due to old OpenCensus protos, now in latest OpenTelemetry proto they got ride of |
@obecny could you please confirm the same? |
@mayurkale22 It looks like it got rid it is not used anymore |
I was going to close but this issue should be closed by #901 |
We're just waiting for reviews and to be confident in it before we release as it is a large change. Should be soon |
Co-authored-by: Rauno Viskus <[email protected]>
Currently opentelemetry-exporter has a limit of 128 bytes for span's attribute value:
opentelemetry-js/packages/opentelemetry-exporter-collector/src/transform.ts
Line 23 in 4627892
We have a use case where we need it to be bigger (we use our own exporter on the backend that sends all the data to Kinesis for further processing, so bigger values are not an issue for us).
I suggest to provide an optional config property called
maxAttributeSize
inside of this interface:opentelemetry-js/packages/opentelemetry-exporter-collector/src/CollectorExporter.ts
Line 29 in 4627892
and then pass it down to the function is responsible for truncating:
opentelemetry-js/packages/opentelemetry-exporter-collector/src/transform.ts
Line 29 in 4627892
If you like the approach, I can prepare a PR today or tomorrow.
If you have any other ideas how to overcome this limitation - let's discuss them.
The text was updated successfully, but these errors were encountered: