Customize /traces response

[pamposh123]

Zipkin traces api returns the ip and port in payload. We would like to suppress this info as it is recognized as security vulnerability.

Is there a way to suppress this info? We are ok with not having remoteEndPoint or localEndPoint nodes as well.

[jcchavezs]

Thanks for coming by. You can use a collector to redact such information. tir. 17. mai 2022, 19:49 skrev arun ***@***.***>:

…

Zipkin traces api returns the ip and port in payload. We would like to suppress this info as it is recognized as security vulnerability. [image: image] <https://user-images.githubusercontent.com/15619237/168877337-cdd6a036-b6e9-410e-833d-cc0e0edd8302.png> Is there a way to suppress this info? We are ok with not having remoteEndPoint or localEndPoint nodes as well. — Reply to this email directly, view it on GitHub <#3448>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAXOYAUXL5OXDTP3YDPQFILVKPL3FANCNFSM5WFW7P5Q> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[pamposh123]

Thanks Carlos, do you have a example/document how collector can be used for this issue? I was looking at https://zipkin.io/pages/architecture.html but couldn't find details around collector usage to redact info.

[jcchavezs]

You can use something like https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/transformprocessor with an open telemetry collector but to be honest i looks like too much burden. You can also create your own processor where you redact those tags: receiver zipkin -> custom processor -> exporter zipkin.

[pamposh123]

Thanks Carlos, where I find Zipkin documentation for creating custom processor. Any example/tutorial etc. will be very helpful.