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
{{ message }}
This repository has been archived by the owner on Jul 13, 2023. It is now read-only.
call /v1/err (or /v1/err/error) to invoke a fake "error" for testing purposes.
call /v1/err/critical to invoke a fake critical exception.
Responds with a status of 418 and creates an appropriate log entry.
Closes#478
call /v1/err (or /v1/err/error) to invoke a fake "error" for testing purposes.
call /v1/err/critical to invoke a fake critical exception.
Responds with a status of 418 and creates an appropriate log entry.
Closes#478
call /v1/err (or /v1/err/error) to invoke a fake "error" for testing purposes.
call /v1/err/critical to invoke a fake critical exception.
Responds with a status of 418 and creates an appropriate log entry.
Closes#478
call /v1/err (or /v1/err/error) to invoke a fake "error" for testing purposes.
call /v1/err/critical to invoke a fake critical exception.
Responds with a status of 418 and creates an appropriate log entry.
Closes#478
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
With the low number of errors and info messages being generated, there is concern that logging may break and we'd be unaware of any problem.
Create an endpoint that generates a demo error to validate logging.
The text was updated successfully, but these errors were encountered: