-atlassian.logging.cloud.enabled

[Bert van Dijk _TMC_nl_]

Hi,

In Kubernetes, it is possible to set the JVM parameter:

-atlassian.logging.cloud.enabled=true

This should enable you to have a central logging point, but I cannot find any information about it. Does anyone know what this parameter does?

Thanks,

Bert

[Yevhen · Accepted solution]

@Bert van Dijk _TMC_nl_ with this property Jira will push logs to localhost:9880 (the default FluentD port). So if you define a FluentD sidecar for Jira pod, Jira will send logs to that FluentD, and FluentD can then send them to whatever backend you define.

[Bert van Dijk _TMC_nl_]

Hi Bert!

Thanks for reaching out.

I've checked internally, and found that this property is obsolete. It should be removed from the java arguments in our Helm charts in the near future.

In the past, when this was set to true, Confluence would push logs directly to a fluentd sidecar which can then send logs to the configured logging backend. This would be a separate container that runs alongside the main Confluence container but in the same pod. The purpose of the Fluentd sidecar is to collect and forward logs from Confluence to a centralized logging system.

The way fluentd works with Confluence DC has now changed enough that it is no longer relevant.

Kind regards,