Forum Discussion

WernerN's avatar
WernerN
Contributor II
3 months ago

Version 9.0 Redacting information in Error Log

Dear Community Members, Has anyone experienced information in the log being redacted. I found this in the latest documenation. However, i see no pattern of what is considered sensitive.  I...
Parsing
System
JackLacava's avatar
JackLacava
Icon for OneStream Employee rankOneStream Employee
3 months ago

I hear you, I agree that we went a bit overboard with this feature. It gets triggered in "interesting" cases, like when a string has 8 consecutive zeros... It can be maddening.

Future releases will likely dial it down a bit.

EricPotts's avatar
EricPotts
New Contributor II
14 days ago

I need this turned off now. No one asked for this "Feature". This waste so much of time and limits customer adoption.

  • JackLacava's avatar
    JackLacava
    Icon for OneStream Employee rankOneStream Employee
    8 days ago

    A workaround i've found recently is, whenever i see a [REDACTED] triggered, i make sure to concatenate that value with some arbitrary other bit (e.g. "s_" + myVariable) and then place it in the details of the error, not the subject (e.g. BRApi.ErrorLog.LogMessage(si, "check details", "s_" + myVariable) ). That seems to keep the censoring algorithm at bay. 

    • WernerN's avatar
      WernerN
      Contributor II
      8 days ago

      Awesome, thanks for the tip Jack! Will try it immediately.