Currently, WildFly natively supports two of three OpenTelemetry signals: traces (via the opentelemetry subsystem) and metrics (via the micrometer subsystem). It would be helpful if WildFly also natively supported OTLP logs. Additionally, it would be good if this feature had unified attribute configuration with the other signals - see WFLY-18290.

It is possible to sort of get this working now, at least if you're using the OpenTelemetry Collector. You can configure the Collector to have a TCP receiver, then configure WildFly to talk to that receiver using a socket-handler and a json-formatter. But then you still need to configure the Collector to massage what WildFly sends into the correct format, which is a bit clunky and probably bad for performance.