Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Configuration errors are ignored
See original GitHub issueMy config file references a sink that is not included in my project - I would have expected that the call to ReadFrom.Configuration throws some sort of error - but it is silently ignored and the sink is just not added.
I would prefer an error - can I change this behavior somehow?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:4
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Custom error setting being ignored for locations denied in ...
In a ASP.Net 4 and MVC2 application we have an odd configuration error. The web.config looks something like this: <configuration> <location path ...
Read more >Ignored Error Types
The Ignored Error Types screen displays the list of errors that should be ignored if a mobile transaction fails on synchronizing. When a...
Read more >Error Message: The configuration has not yet loaded. If this ...
IssueError Message The configuration has not yet loaded. If this message persists, it may indicate a configuration problem.
Read more >Manage errors in APM: Collect, ignore, or mark as expected
Go to the Server-side configuration menu for the application that has errors that you want to ignore. Under Error collection, look for Ignore...
Read more >How to ignore configuration errors
How to ignore configuration errors. Two common errors turning up in the log files are "(EE) ioctl EVIOCGNAME failed: Inappropriate ioctl for ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Bumping this up, because I think this is very counter intuitive. While logging events should not fail, the configuration of the logger itself is a fundamental part of any application and failure to load the configured sinks really ought to be fatal.
It took me a bit to realize I forgot to include the Sinks.Console and Sinks.File packages when the logging was not working.
The whole point of logging is to avoid silent failures, so this is rather ironic.
Could be closed? Configuration errors are not ignored entirely. They are swallowed by default by design and
SelfLogis a way to debug all issues with config.