Does rabbitmq operator have/support logging capability?

[Anjitha M]

Hi all,

I have a requirement where my RabbitMQ operator/cluster needs the following features:

1. Enable logging for RabbitMQ operator (e.g. logging sent to rabbitmq-server-error.log). The log level needs to be configurable ( the log level (INFO, TRACE, DEBUG, ERROR)).

2. Log rotate needs to be enabled so the operator doesn't fail over time due to disk space exhaustion.

3. Before log rotation logs need to be sent to AIOPs Logging (e.g. Elastic Search / Kibana logging provided by AIOPs) before log is lost to log rotation.

I was wondering if this is supported by the operator, or if not - any suggestion on how this can be incorporated? 

Thanks,

Anjitha 

[Michal Kuratczyk]

Hi,

1. RabbitMQ Operator logs by default - nothing to enable there. If you want to customize the log level, you can add --zap-log-level=LEVEL as an `operator` container command argument (full example here: https://github.com/rabbitmq/cluster-operator/pull/554). RabbitMQ Operator doesn't currently produce any logs below info but it uses libraries/components that do, so you will indeed get more or less logs based on the LEVEL set.

2&3. That's not the right approach to logging on Kubernetes. You don't need log rotation and you don't need to worry about running out of disk - logs are emitted to stdout/stderr and you should store them externally.  RabbitMQ Operator and RabbitMQ Clusters deployed to Kubernetes are no different than other Kubernetes workloads in this regard: https://kubernetes.io/docs/concepts/cluster-administration/logging/

Best,

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/8453a655-e927-423e-820c-e7291a90201fn%40googlegroups.com.

--

Michał