Actions
Bug #20960
closedLower the log level of the "Skipping adding class [...] as its name is equal or longer than 1024" message
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
Description
It is not really a problem (just a message that could be useful to troubleshoot a problem) and happens quite a lot with Rudder due to the way the reporting is handled (in case full class prefix length exceeds 1024 and we fall back on the old class prefix).
Let's set it to verbose level so that it is not visible in normal usage.
Actions