Make CloudConfigurationManager.GetSetting("setting") less verbose
Each calls to CloudConfigurationManager.GetSetting("setting") generate garbage in the trace outputs. Its not necessary and very annoying when analysing output traces.
The simple statement CloudConfigurationManager.GetSetting("setting") generates this:
Getting "setting" from ServiceRuntime: FAIL.
Getting "setting" from ConfigurationManager: PASS (0).
Eivind Tjore commented
This is a easy to fix issue that irritates a lot of people in addition to being a security risk...
So 2 years reviewing it seems a bit overkill :(
Joshua Drake commented
Can we make it cache to, the way the ConfigurationManager does?
We are also getting this with version 3.1.0.
It's still logging the full looked up value.
Even better would be to allow diagnostics to be set up to filter out specific assemblies all together.
I'm using version 3.1 and I'm still getting these trace messages in my log. How is this fixed exactly? Do I need to configure something?
Fixed in version 3.0.0. Please update Microsoft Azure Configuration Manager nuget package.
This is going to cause us to fail a (eventual) security audit, with no doubt.
Please allow us to TURN OFF the tracing!!
Jimmy Chandra commented
This thing pretty much make it looking at azure log useless. I used to be able to figure out problems at least by looking at the log. Now... it's all spam. Thanks MS. Fix it please. Either remove the tracing on release build or let us control the trace level. Tried removing listener, adding moving it to Info, etc. Nothing works. Grr.
Andrew Koltz commented
Agreed. Independent configuration is the right answer here. I want to be able to focus on my application's logs, not be distracted by the platform's.
Besides the obvious annoyance-factor this might also have security implications. The PASS-entry writes the actual value of the setting (e.g. a SQL or blob connection string) to the trace log which possibly exposes the data in an unwanted fashion (i.e. via log access or by hooking in a trace listener).
Could not agree more. At least allow us to independently configure the tracing level of the CloudConfigurationManager trace messages so we can turn these off without disabling tracing globally.