Add a failfast/troubleshooting option

[curtcox]

Description

My biggest issue with Logfire so far is lack of diagnostic information when logs aren't successfully being sent to the server. Having a default mode that doesn't depend on successful logging in order to run makes sense. However, there should also be a mode that dumps as much relevant diagnostic information as possible to the user and exits if successful logging can't be verified. I'm making this request because so far most of my time with Logfire has been spent trying to figure out why nothing was being sent to the logs.

This request is not about missing better requirement definition and resolution. It would be nice to have a more comprehensive set of requirements so that they could be installed up front. However, missing requirements tend to have the nice property of existing with a stack trace that can be diagnosed and fixed.

[alexmojaki]

logfire.configure(send_to_logfire=True, token='<hardcoded token>'); logfire.info('test log'); logfire.force_flush() should work if you can connect to the server and have a token.

This request is not about missing better requirement definition and resolution. It would be nice to have a more comprehensive set of requirements so that they could be installed up front.

I'm confused, is this a separate issue? Did you have some problem about missing dependencies?

[curtcox]

Yes, that is a different issue. That's what I mean by "this request is not about".

I did have problems with missing dependencies, but the error messages and stack traces were enough to search on in order to find solutions. I mentioned that specific instance because it illustrates the effectiveness of the fast-fail-abort-with-enough-info-to-solve-the-problem option that I'm requesting. Sorry for the confusion.