-
Story
-
Resolution: Done
-
Critical
-
AMQ 7.6.0.GA
If an application generates a lot of WARN log messages, for example if message re-delivery is exceeded during a performance test, the logs can consume the entire PV. For an operator deployment, there is currently no way to configure the logging either (to set up, for example, rolling logs).
- incorporates
-
ENTMQBR-6406 Allow to set loglevel at ActiveMQArtemis CR level
- Closed
- is cloned by
-
ENTMQBR-4624 Doc: AMQ 7 operator deployment - logs can consume entire disk
- Closed
-
ENTMQBR-5945 [doc] AMQ 7 operator deployment - logs can consume entire disk
- Closed
- is duplicated by
-
ENTMQBR-5469 [OpenShift] Artemis log is created inside the AMQ Broker Data folder
- Closed
- is incorporated by
-
ENTMQBR-7157 logging - fix defaults in the image to just use stdout - no disk
- Closed
- is related to
-
ENTMQBR-3588 Allow configurable logging for AMQ 7 Operator Deployments
- Closed
-
ENTMQBR-7616 Exception java.security.PrivilegedActionException raised when the broker starts
- Closed
-
ENTMQBR-7877 [LTS] Exception java.security.PrivilegedActionException raised when the broker starts
- Closed