We are currently trialling an experimental feature in our most client libraries that sends exception reports to Ably to help us identify and resolve issues quickly.


When this feature is enabled (this is the default for these newer client libs), it will capture exceptions that are generated as a result of Ably client library code failing, and will:

  • Collate some context about the exception
  • Gather stack traces attempting to remove stack traces that don't apply to the Ably client library
  • Send the stack trace, context and exception to our private error reporting service at errors.ably.io


If you want to find out more about this exception reporting service in some of our bleeding edge client libraries, pleased get in touch