Replies: 1 comment
-
Hi! Turning on Log4Net's and collecting internal debugging would be the first thing to try: https://logging.apache.org/log4net/release/faq.html#internalDebug I'd also suggest turning off/skipping the async appender configuration until you have the plain direct appender working. If that's still no help, checking Seq's ingestion log (Settings > Diagnostics) is the next place to look, followed by using an HTTP debugging proxy like Fiddler to check whether the application is trying to send data to Seq and where that might be failing. Hope this helps, |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is my project, how do I configure log4net
I have been using log4net in my project for a long time and it is very user-friendly. My company has used log4net in multiple projects, and today I wanted to use the powerful logging function of seq. However, I found that the logs cannot be written and there are no task prompts. The logs can be written to the console;
I use C #. net8 serilog seq, which can completely write logs to seq, but my company's project is too complicated and I don't want to convert log4net to serilog. Please help me, thank you!
Beta Was this translation helpful? Give feedback.
All reactions