# NcScale is shutting down – any alternatives for logging WeWeb and Xano?

**URL:** <https://community.weweb.io/t/ncscale-is-shutting-down-any-alternatives-for-logging-weweb-and-xano/17018>\
**Category:** Ask us anything\
**Tags:** xano\
**Created:** [March 5, 2025, 5:42pm UTC](https://community.weweb.io/t/ncscale-is-shutting-down-any-alternatives-for-logging-weweb-and-xano/17018 "2025-03-05T17:42:53Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Alchuu](https://avatars.discourse-cdn.com/v4/letter/a/ee7513/32.png) [@Alchuu](https://community.weweb.io/u/Alchuu)\
**Post date:** [April 11, 2025, 9:24am UTC](https://community.weweb.io/t/ncscale-is-shutting-down-any-alternatives-for-logging-weweb-and-xano/17018/2 "2025-04-11T09:24:25Z")

</div>

Hey Andrii,

I’ve been using Sentry for logging errors in both WeWeb and Xano, and it’s been working pretty smoothly.

I created a global workflow that runs on app load (before fetching collections) and placed the following code in a JS block to capture and send all errors to Sentry, including Xano errors. It doesn’t require any custom API endpoints and is relatively easy to configure.

```auto
wwLib.getFrontWindow().axios.interceptors.response.use(
  response => response, 
  error => {
    // Capture all errors in Sentry
    Sentry.captureException(error);

    // Propagate the error to the rest of your error handling logic
    return Promise.reject(error);
  }
);

```

Hope that helps!

---

_[View the full topic](https://community.weweb.io/t/ncscale-is-shutting-down-any-alternatives-for-logging-weweb-and-xano/17018)._