4 ms·
Agreed, logging in config retrieval code should log all this stuff, requests, where they are filled from, that sort of thing. The problems with this approach w
by cesaref 3y ago
Agreed, logging in config retrieval code should log all this stuff, requests, where they are filled from, that sort of thing.
The problems with this approach when it's enabled is that log aggregators (e.g splunk) can end up including stuff like passwords which shouldn't be visible to the group able to view those logs, so some care is needed.
- TeMPOraL 3y agoLogging keys only should be sufficient for this.
- usrusr 3y agoI'd rather have some config reserialization capability with provenance (perhaps as an opt-in). A good config reserialization can make itself useful in so many situations, if it has the right features. Like pointing out key-value pairs that don't have any effect, or simply writing out some documentation. Logging has its merits, like discoverability when you stare at it without suspecting configuration to be the culprit, but I believe that there can and should be more.