• Type: Suggestion
• Resolution: Unresolved
• Fix Version/s: None
• Component/s: Data Center - Core
• Labels:

  • affects-server
  • clustering
  • data-center
  • data-center-specific
  • enterprise-cluster
  • logging
  • logging&auditing

[CONFSERVER-40921] Changes made in Logging and Profiling only apply to the current node when running Confluence Data Center with multiple nodes

Collapse comment: Nikita Dvorkin added a comment - 04/Feb/2022 5:35 PM

Nikita Dvorkin added a comment - 04/Feb/2022 5:35 PM

Dear Confluence developers,

Haven't you tired yourself activating logging on each node for some package before testing some feature? It would be great to see this implemented.

Expand comment: Nikita Dvorkin added a comment - 04/Feb/2022 5:35 PM

Nikita Dvorkin added a comment - 04/Feb/2022 5:35 PM Dear Confluence developers, Haven't you tired yourself activating logging on each node for some package before testing some feature? It would be great to see this implemented.

Collapse comment: Matt Doar added a comment - 01/Oct/2021 5:37 PM

Matt Doar added a comment - 01/Oct/2021 5:37 PM

Odd. When you add a message to the log from one node does the message appear in the log on other nodes? Or is the problem just with this one log package not getting propagated?

Expand comment: Matt Doar added a comment - 01/Oct/2021 5:37 PM

Matt Doar added a comment - 01/Oct/2021 5:37 PM Odd. When you add a message to the log from one node does the message appear in the log on other nodes? Or is the problem just with this one log package not getting propagated?