You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been trying to set this up and, of course, while still trying to figure out the proper configuration set I've not added my auth credentials and the Loki server's been rejecting my logs. But the library was not reporting those errors even if I've set the onConnectionError option. After some debugging and looking through the code it appears that only actual connection errors will get reported there and successful requests resulting in failure responses will not. Are there any plans to expose this kind of errors? I understand that configuration errors should get caught early in development and never appear in production but still there is a chance that the remote side may change for some reason and start to reject my calls, so my code will need some way of detecting such conditions.
Cheers
The text was updated successfully, but these errors were encountered:
Hey,
I've been trying to set this up and, of course, while still trying to figure out the proper configuration set I've not added my auth credentials and the Loki server's been rejecting my logs. But the library was not reporting those errors even if I've set the
onConnectionError
option. After some debugging and looking through the code it appears that only actual connection errors will get reported there and successful requests resulting in failure responses will not. Are there any plans to expose this kind of errors? I understand that configuration errors should get caught early in development and never appear in production but still there is a chance that the remote side may change for some reason and start to reject my calls, so my code will need some way of detecting such conditions.Cheers
The text was updated successfully, but these errors were encountered: