tracing bridge selection in micrometer

Question

Background:

Our system contains 40+ micro-services (spring-boot 3.2.x), they are all deployed on a Kubernetes cluster, logs are printed in the pods, and we use ELK stack (LogStash, ElasticSearch, Kibana) to search, analyze, and visualize logs.

by default the log details don't contains the trace_id & span_id, which causes difficulties to search a particular request, especially in production environment.

so my requirement is only to add trace_id & span_id into the log.

Confuses:

after some researching, I found the micrometer tracking maybe good for me.

but I got stuck on the selection for the tracking bridge, since micrometer support brave and otel, I tried both bridge in my local, both meet my requirement.

I don't know the internal mechanism for the bridge, I am just worried that include the bridge is a little bit heavy for my scenario? since I don't need other functionalities apart from logging.

any micrometer expert can help on this?

Thanks in advance.