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
rhankey's avatar
rhankey
Contributor III
3 months ago

It will be interesting to hear if there is a config parameter by AppServer, App, or User somewhere to turn this "feature" on/off, or if there is way to toggle it on/off when logging specific output.

In the meantime, the workaround I have been using to overcome this new "feature" is by formatting numeric values as I'm writing them to the log.  Eg:

api.LogMessage("DecValue="+DecValue.ToString("N2")+", IntValue="+IntValue.ToString("0"))

 

  • WernerN's avatar
    WernerN
    Contributor II
    5 days ago

    It is a bit frustrating that all of us have to come up with work around solutions that actually increase the debugging effort for a 'solution' that should not even be there in the first place.

    • RobbSalzmann's avatar
      RobbSalzmann
      Valued Contributor II
      5 days ago

      It may help to know that OneStream is actively tightening security of its platform to meet the very stringent requirements of FedRAMP certification.  While the log redaction situation creates a little extra work for developers, there are a couple of things that I think offset this:

      • FedRAMP means OneStream can be sold into the massive government municipal market - opening up opportunities, big projects for many of us.
      • V9.1 introduces the Business Rules Profiler.  Using this tool will negate the need for a majority of the BRApi.ErrorLog.LogMessage calls currently used for debugging.

       

      Jack's workaround above is brilliant in it's simplicity and can be implemented with a simple find and replace.