log.exchange.formatter = json
has no effect
#12810
-
Describe the bugTrying to export logs to the system exchange as structured JSON logs with Reproduction steps
Expected behaviorLog messages in the queue are JSON-formatted according to the default field map. Additional contextThe affected instances are running RabbitMQ 3.13.4, Erlang 26.2.5 in a cluster of 3 or 5 nodes. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
@Kritnich RabbitMQ 3.13.x is out of community support. JSON formatting does have an effect. I have revisited it thoroughly a few months ago when the relevant section of the docs was last updated. The formatter may or may not be used when the log target is an exchange and not a file or the standard streams. The docs do not promise that it is a supported combination. Just because two features exist does not mean that they are supposed to be combined. |
Beta Was this translation helpful? Give feedback.
-
If someone wants to contribute a change that would apply JSON formatting to the messages published to This is a combination of two relatively rarely used features. Both work as documented independently. |
Beta Was this translation helpful? Give feedback.
If someone wants to contribute a change that would apply JSON formatting to the messages published to
amq.rabbitmq.log
, they are welcome to do it for4.x
. There won't be any more3.13.x
open source releases that are not high severity security patches.This is a combination of two relatively rarely used features. Both work as documented independently.
If someone needs them both, that person can look into contributing it. The core team focuses primarily on issues that affect the majority of users.