# Error monitoring & managing application reliability

**URL:** <https://community.weweb.io/t/error-monitoring-managing-application-reliability/3583>\
**Category:** Ask us anything\
**Created:** [July 18, 2023, 9:56pm UTC](https://community.weweb.io/t/error-monitoring-managing-application-reliability/3583 "2023-07-18T21:56:07Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![caffeinatedwes](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/caffeinatedwes/32/625_2.png) [@caffeinatedwes](https://community.weweb.io/u/caffeinatedwes)\
**Post date:** [July 18, 2023, 9:56pm UTC](https://community.weweb.io/t/error-monitoring-managing-application-reliability/3583/1 "2023-07-18T21:56:08Z")

</div>

Hi all,

We have a client application that’s getting more complex and whose application is becoming a core part of their business’ continuity. As such, we’re looking to mature in how we manage our application reliability.

I’m curious if anyone else here has thought about this and what type of solutions they use. For context, here’s where we are now—

- **Up-time monitoring** : We’re using [BetterUptime](https://betterstack.com/uptime) to ensure our WeWeb projects are consistently live. This has proven invaluable, particularly during WeWeb’s [downtime earlier this year](https://community.weweb.io/t/urgent-performance-issues-huge-latency-and-live-website-going-down-this-weekend/1972), enabling us to proactively communicate with clients and work with the WeWeb team.
- **Error and Performance Monitoring** : We’re in the process of identifying suitable solutions. Our back-ends are built on Xano, and we’re setting up an error and performance monitoring system using their metadata API’s [request history endpoint](https://docs.xano.com/metadata-api/request-history). For the front-end, we’re considering tools like [LogRocket](https://logrocket.com/) or [Sentry](https://sentry.io/welcome/). While there are numerous other tools, most seem tailored for larger, code-centric applications.

Any input or thoughts would be appreciated! From the look of it, I’ve only seen [one other post about this topic before](https://community.weweb.io/t/has-anyone-implemented-sentry-for-error-monitoring/1856), which didn’t have a response. CC @felixtanhm

---

<div class="post-metadata">

**Author:** ![mark](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/mark/32/4163_2.png) [@mark](https://community.weweb.io/u/mark)\
**Post date:** [July 18, 2023, 11:29pm UTC](https://community.weweb.io/t/error-monitoring-managing-application-reliability/3583/2 "2023-07-18T23:29:43Z")

</div>

NCScale looks promising. They have Weweb on their roadmap to integrate.

---

<div class="post-metadata">

**Author:** ![caffeinatedwes](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/caffeinatedwes/32/625_2.png) [@caffeinatedwes](https://community.weweb.io/u/caffeinatedwes)\
**Post date:** [July 19, 2023, 12:27am UTC](https://community.weweb.io/t/error-monitoring-managing-application-reliability/3583/3 "2023-07-19T00:27:22Z")

</div>

Thanks for mentioning them — I’ll follow along their progress.

---

<div class="post-metadata">

**Author:** ![dorilama](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/dorilama/32/10403_2.png) [@dorilama](https://community.weweb.io/u/dorilama)\
**Post date:** [July 19, 2023, 6:52am UTC](https://community.weweb.io/t/error-monitoring-managing-application-reliability/3583/4 "2023-07-19T06:52:47Z")

</div>

A new player in the space is [highlight.io](https://www.highlight.io/). It’s on my list of things to try.  
It has session replay, error monitoring and logging. It’s open source, you can self host, but in the docs they say the provided self hosting setup is not recommended for high volumes, where they obviously recommend thei cloud offering.  
From a quick read of the docs it looks like it can be easily integrated in weweb’s frontend. For xano you probably need to send the error logs yourself using a http request.

---

<div class="post-metadata">

**Author:** ![caffeinatedwes](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/caffeinatedwes/32/625_2.png) [@caffeinatedwes](https://community.weweb.io/u/caffeinatedwes)\
**Post date:** [July 19, 2023, 3:16pm UTC](https://community.weweb.io/t/error-monitoring-managing-application-reliability/3583/5 "2023-07-19T15:16:01Z")

</div>

Thank you, @dorilama. Highlight looks just what I’m looking for. For me, I think it comes down to deciding if I really need some of the product analytics features or not. I feel like I’d lean towards LogRocket if I want those, and towards Highlight if I don’t need them.

> From a quick read of the docs it looks like it can be easily integrated in weweb’s frontend. For xano you probably need to send the error logs yourself using a http request.

I’m curious how you think about it, but I don’t like the idea of having to configure various error handling logic on every API endpoint.

And actually…hacking around with the metadata API, I was actually able to configure exactly what I needed yesterday (a simple dashboard to get an overview of errors and API performance) with Google Cloud Functions and BigQuery!

 ![CleanShot 2023-07-19 at 09.09.20@2x](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/b/b019a719693d16596b8451b784f1ca9d50d313a4.png)

---

<div class="post-metadata">

**Author:** ![Quentin](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/quentin/32/6_2.png) [@Quentin](https://community.weweb.io/u/Quentin)\
**Post date:** [July 24, 2023, 9:13am UTC](https://community.weweb.io/t/error-monitoring-managing-application-reliability/3583/6 "2023-07-24T09:13:13Z")

</div>

Personally, I’m a huge fan of [Sentry](https://sentry.io/welcome/) and [Fullstory](https://www.fullstory.com/) for this.

[Posthog](https://posthog.com/) might also help 😉

---

<div class="post-metadata">

**Author:** ![ben](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/ben/32/5605_2.png) [@ben](https://community.weweb.io/u/ben)\
**Post date:** [October 14, 2023, 5:29pm UTC](https://community.weweb.io/t/error-monitoring-managing-application-reliability/3583/7 "2023-10-14T17:29:59Z")

</div>

Hi @caffeinatedwes curious to learn what choice of tool you made in the end! 👀

---

<div class="post-metadata">

**Author:** ![caffeinatedwes](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/caffeinatedwes/32/625_2.png) [@caffeinatedwes](https://community.weweb.io/u/caffeinatedwes)\
**Post date:** [October 16, 2023, 2:42pm UTC](https://community.weweb.io/t/error-monitoring-managing-application-reliability/3583/8 "2023-10-16T14:42:24Z")

</div>

We’re just using the in-house back-end monitoring tool for now @ben.

We de-prioritized implementing a front-end tool, but I played around with [https://livesession.io/](https://livesession.io/) a bit, and I liked it as it was also helpful from a product analytics perspective.

---

<div class="post-metadata">

**Author:** ![viktor.kyrychenko](https://avatars.discourse-cdn.com/v4/letter/v/c67d28/32.png) [@viktor.kyrychenko](https://community.weweb.io/u/viktor.kyrychenko)\
**Post date:** [February 24, 2024, 10:31am UTC](https://community.weweb.io/t/error-monitoring-managing-application-reliability/3583/9 "2024-02-24T10:31:09Z")

</div>

I assume this topic is going to be hot now 🥲  
So, encourage everybody to share their experience and actual results with their monitoring tools with recent downtime.

We personally had BetterStack and it completely missed the incident. It still says we are fine, lol. So, we are definitely going to change it with something else, but what?..

Eager to see your recommendations, WeWeb folks!

---

<div class="post-metadata">

**Author:** ![caffeinatedwes](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/caffeinatedwes/32/625_2.png) [@caffeinatedwes](https://community.weweb.io/u/caffeinatedwes)\
**Post date:** [February 24, 2024, 8:11pm UTC](https://community.weweb.io/t/error-monitoring-managing-application-reliability/3583/10 "2024-02-24T20:11:22Z")

</div>

We use Better Uptime and we’ve been catching the incidents.

 ![CleanShot 2024-02-24 at 14.10.26@2x](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/a/a39d97299cdd494d8e7cd292a8e6cf07f3dbacd6.png)
