Cacti VS Sentry

If you have SNMP access to your switches, a very simple quick start is to use Cacti (https://www.cacti.net/) which will give you some nice graphs in no time at all. Far less complex than setting up/configuring a full monitoring system or NetFlow/SFlow.

This was fixed in the following commit https://github.com/Cacti/cacti/commit/d1c1380ad9250c323f1dc874e26840c80edd3afb, I suggest upgrading cacti to at least the 1.2.20 version.

Cactai is also free, but has a steep learning curve. https://www.cacti.net/

Nice write-up! I've done similar with Cacti, which is free.

Cacti - network monitoring

https://www.cacti.net/.

Pretty simple request, but I couldn't find any solution on the internet, neither in Archwiki / Gentoowiki. There are some complicated things like cacti that can read sensord output, but that's a bit of overkill. I just want something like hwinfo64 for $forbidden_OS.

Just to throw this one out there, I use cacti https://www.cacti.net/ for my network monitoring.

I''ve had good luck graphing our switch port statistics with Cacti.

First, sign up for a free account at https://sentry.io. Create a new project and make note of your DSN (Data Source Name).

Using APM tools like NewRelic, Sentry, Datadog, etc to monitor the performance of your application and while you're on it, they can help you identify N+1 queries.

However, ensuring the reliability and performance of your Next.js app is equally crucial. That’s where Sentry comes into play. Combined with Sentry, an industry-leading error monitoring platform, Next.js empowers developers to proactively identify and resolve issues that may arise in their applications. In this article, we’ll explore how to integrate Sentry into your Next.js project for effective error monitoring and performance optimization.

Sentry: Error monitoring for applications, including APIs. Also offers application performance monitoring (APM).

Indeed, webapps are not immune to distribution problems. Wayward and invasive browser extensions are a clear threat, as are 3rd-party dependencies (and their dependencies) loaded at runtime. Which is why companies like https://sentry.io exist. I think the difference is that webapps are "distributable by default" and it takes real work to break this. Versus having local desktop apps which require work to distribute. A potent example of the power of defaults.

Sentry produces nothing of value? You don't value an open source error tracking and performance monitoring platform? https://github.com/getsentry/sentry

> You invent something, and then immediately turn it into a cheap commodity by releasing it for free.

Exactly. A 71-line python script https://github.com/getsentry/sentry/commit/3c2e87573d3bd16f6... was groundbreaking when it came out and the fact that it springboarded into a startup is commendable.

sentry.io: 5

Sentry - Open Source Alternative For Error Tracking

11. Sentry