Exception handling
In most applications some errors will get raised that aren't related to possible bugs in your code, they just happen when your app gets into contact with the real world. Bots might drop by and try to automatically post forms, outdated links might direct visitors to content that doesn't exist anymore and so on.
To avoid these errors from being raised as problems in AppSignal it's possible to add exception handling to your code or even let AppSignal completely ignore certain errors.
Table of Contents
Ignore errors
The AppSignal configuration makes it possible to ignore errors. By providing a list of specific errors AppSignal will not send alerts when these errors are raised.
Appsignal.Transaction.set_error/3
If you want to rescue exceptions in your application to prevent crashes, but
still want to track the occurrence you can use
Appsignal.Transaction.set_error/3 to add the exception
to the current AppSignal transaction.
1
2
3
4
5
6
7
try do
raise("Oh no!")
rescue
e ->
stack = System.stacktrace
Appsignal.Transaction.set_error("ExceptionName", "error message", stack)
end
The exception will be tracked by AppSignal like any other error, and it allows you to provide custom error handling and fallbacks.
Note: This function only works when there is an AppSignal transaction active. Otherwise the error will be ignored.
Please see
Appsignal.send_error/6 for sending errors
without an AppSignal transaction.
Appsignal.send_error/6
AppSignal provides a mechanism to track errors that occur in code that's not in a web or background job context, such as Mix tasks. This is useful for instrumentation that doesn't automatically create AppSignal transactions to profile.
You can use the Appsignal.send_error/6 function to
directly send an exception to AppSignal from any place in your code without
starting an AppSignal transaction first.
1
2
3
4
5
6
7
try do
raise "Oops!"
rescue
e ->
stack = System.stacktrace
Appsignal.send_error(e, "error message", stack)
end