Project

General

Profile

Actions

Bug #4542

closed

Missing property 'rudder.debug.nodeconfiguration.path' in configuration file

Added by Nicolas CHARLES about 10 years ago. Updated almost 10 years ago.

Status:
Released
Priority:
1
Category:
System integration
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

A new parameter appeared in the configuration file of Rudder.
Here is the content to add with the a migration script between 2.9 and 2.10

#
# Debug Node Configuration parameters
# 
# Node Configurations are all the parameters (global parameters, 
# applied rules/directives with their parameters, node information, etc)
# contextualized for the node. They are the resources used to actually
# generate promises for THAT node. 
#
# By default, these information are only used internally by Rudder and
# are not available to the user. But they may be needed in some cases, 
# for debugging. 
#
# This option allows to define the directory where the node configurations
# (in JSON format) will go. 
# 
# To enable the writing of node configurations, enable the logger 
# named "rudder.debug.nodeconfiguration" in logback.xml
#
rudder.debug.nodeconfiguration.path=/var/log/rudder/nodeConfigurations


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #4242: Promise generation takes too long when getting more and more nodesReleasedFrançois ARMAND2014-03-11Actions
Actions

Also available in: Atom PDF