Bug #23969: Waning log spam when disabled rudder_compute_changes setting - Rudder - Issue Tracker

Actions

Copy link

Bug #23969

closed

Waning log spam when disabled rudder_compute_changes setting

Added by Elaad FURREEDAN 12 months ago. Updated 11 months ago.

Status:

Released

Priority:

N/A

Assignee:

François ARMAND

Category:

Server components

Target version:

7.3.11

Pull Request:

https://github.com/Normation/rudder/p...

Severity:

Minor - inconvenience | misleading | easy workaround

UX impact:

I hate Rudder for that

User visibility:

Effort required:

Very Small

Priority:

Name check:

To do

Fix check:

Checked

Regression:

Description

When we disabled the setting rudder_compute_changes through API:

curl -k -H "X-API-Token: <Your Api token>"  -X POST 'https://<you Rudder Host>/rudder/api/latest/settings/rudder_compute_changes' -d "value=false"

We have a warning log spamming :

[2023-12-01 09:28:07+0100] WARN  report.changes - Not updating changes by rule - disabled by configuration setting 'rudder_compute_changes' (set by REST API)
[2023-12-01 09:28:12+0100] WARN  report.changes - Not updating changes by rule - disabled by configuration setting 'rudder_compute_changes' (set by REST API)
[2023-12-01 09:28:17+0100] WARN  report.changes - Not updating changes by rule - disabled by configuration setting 'rudder_compute_changes' (set by REST API)
[2023-12-01 09:28:22+0100] WARN  report.changes - Not updating changes by rule - disabled by configuration setting 'rudder_compute_changes' (set by REST API)
[2023-12-01 09:28:27+0100] WARN  report.changes - Not updating changes by rule - disabled by configuration setting 'rudder_compute_changes' (set by REST API)
.
.
.

/var/log/rudder/webapp # cat 20231201.stderrout.log|grep -i "Not updating changes by rule"|wc -l
12134