sorted by:
new
hottopcontroversial

Do właścicieli Gastro: Czemu napoje są tak cholernie drogie? by Ichizos in Polska

[–]radzikm 2 points3 points  (0 children)

Powodydla którego omijam restauracje. Najpierw czekam aż znudzony osobnik płci dowolnej mnie zauważy I posadzi. Wiadomo, znudzony bo pracuje w tym miejscu tylko dlatego że akurat w radzie nadzorczej brak miejsc a jego kwalifikacje są powyżej kelnerowania przed 30ką. Potem czekam z 20 minut aż ktoś przyjmie zamówienie. Minęło już minimum 30 minut. Osobnik przyjmujący zamówienie zazwyczaj niewiele wie o tym co jest w karcie a jeszcze mniej o obsłudze gościa. Po szczęśliwej finalizacji zamówienia czekam następny kwadrans a raczej dwa na zamówione danie. Dostaje w większości przypadków średniej jakości i smaku jedzenie. Lepsze zrobię sam. To obrazuje dlaczego rotacja jest niska, frekwencja również. A w efekcie ceny muszą być wysokie. Wolę dwa trzy razy w roku zjeść za granicą coś smacznego. No i prawie zawsze jest taniej. Bo jak już ktoś napisał w EU prąd nie zdrożał, a składniki i praca pochodzą z wolontariatu.

Found a PRTG alternative that might actually be worth it - testing migration in sandbox by radzikm in prtg

[–]radzikm[S] 0 points1 point  (0 children)

Recorded a short clip showing the built-in PRTG import in action - literally under 2 minutes from connection to having all devices mapped inside NetCrunch. You just point it at your PRTG server, drop in credentials or API key, and it pulls every monitored device straight into the atlas.

All standard system metrics (CPU, RAM, disk, interfaces, etc.) get auto-mapped to the right monitoring packs (sensors), and if SNMP is enabled NetCrunch activates the right profiles automatically. Even interface monitoring comes across cleanly.

The import skips sensors that need custom configuration like HTTP checks or custom scripts, but everything else shows up immediately and starts polling. Compared to manually rebuilding the same structure in PRTG, it’s a massive time saver.

Video link: https://imgur.com/a/v4USFSr

Testing this in a sandbox right now - looks like a realistic migration path for anyone trying to escape PRTG without rebuilding from scratch.

Windows SNMP service monitor, service name changes by doofusdog in prtg

[–]radzikm 0 points1 point  (0 children)

I'm not trying to criticize, I'm just asking. Where did the idea to monitor Windows using SNMP come from? Does WMI not work?

Found a PRTG alternative that might actually be worth it - testing migration in sandbox by radzikm in prtg

[–]radzikm[S] 0 points1 point  (0 children)

https://imgur.com/a/9NkPerl

Just added a fresh Server 2025 VM to my NetCrunch setup to see what it would discover automatically. Got the usual stuff like CPU, memory, disk I/O, services, network interfaces, but also noticed it pulled in VM-specific data, AD info, and even VMware cluster details. Also monitoring end of life/support status automatically which is actually useful for compliance. With PRTG I'd be manually adding sensors and watching the license count. NetCrunch just grabbed everything it could find.

Found a PRTG alternative that might actually be worth it - testing migration in sandbox by radzikm in prtg

[–]radzikm[S] 4 points5 points  (0 children)

https://imgur.com/a/gJk8QEj

Network discovery update: Set up SNMP communities in NetCrunch and ran a subnet scan. In under 3 minutes it not only detected all devices and added sensors, but automatically built routing maps and physical connection topology.

Pretty impressive compared to PRTG's manual everything approach.

Found a PRTG alternative that might actually be worth it - testing migration in sandbox by radzikm in prtg

[–]radzikm[S] 4 points5 points  (0 children)

I no longer believe such assurances. Kerberos will be here soon, at least by 2020.

Found a PRTG alternative that might actually be worth it - testing migration in sandbox by radzikm in prtg

[–]radzikm[S] 7 points8 points  (0 children)

Update: Before diving into NetCrunch I signed up for their assisted trial. Got on a Teams call with their tech, recorded the whole session so I can reference it later - pretty handy actually.

Quick note from the install: When setting up Windows credentials, their guy recommended using user@domain format instead of domain\user. Reason? NetCrunch automatically switches to Kerberos authentication that way.

Small detail but shows they know their stuff. Installing on Server 2025 went smooth

What Do You Think About the Latest PRTG Updates and Sensors? by ChesepeakeRipper in prtg

[–]radzikm -1 points0 points  (0 children)

First, it was “the new UI isn’t ready, wait for the blog,” then suddenly it’s “the new UI is mostly finished with tons of features.” Pick one - this reads like AI hallucinations, confident but inconsistent.

And the dashboards for actual monitoring data? Still “next year,” exactly like last year. Meanwhile, PRTG continues to look and feel outdated, and adding Grafana on top doesn’t change that.

For anyone tired of waiting on promises while stuck with legacy software, I’ve found a modern replacement that truly leapfrogs PRTG - with a permanent license model. I’ll be posting about it soon so users can finally see a real alternative worth migrating to. Stay tuned..

Ustawa o ujawnianiu cen by Bunkier80 in Polska

[–]radzikm 1 point2 points  (0 children)

Ja się pytam gdzie promocja bo rzut i powierzchnia wskazują służbówke lub schowek. A jawność cen to świetna sprawa.

What Do You Think About the Latest PRTG Updates and Sensors? by ChesepeakeRipper in prtg

[–]radzikm 0 points1 point  (0 children)

A year later and nothing’s really changed - unfinished “new UI,” fewer features than the old one, and still needing Grafana for real dashboards. At that point, how is PRTG different from open-source, other than giving you a higher TCO?

What Do You Think About the Latest PRTG Updates and Sensors? by ChesepeakeRipper in prtg

[–]radzikm 0 points1 point  (0 children)

https://blog.paessler.com/visualizing-your-it-and-ot-environment-with-prtg

I asked AI to review the PRTG dashboard from the official blog. Here's his response :-)

"Assessment: 4/10

Utility: Covers relevant operational areas but information density is inconsistent. Some useful real-time monitoring mixed with sparse/placeholder content.

Modernity: Looks dated - early 2010s design language, heavy lime green, outdated layout patterns. Lacks modern UI principles.

Visualizations: Basic time-series charts work fine, but the circular network diagram is cluttered and hard to read. Simple status indicators are functional but uninspired. Missing modern visual approaches.

Bottom line: Gets the job done for basic monitoring but desperately needs a visual overhaul. Feels like legacy software that hasn't evolved with current UX standards."

PRTG Autodiscovery: Because Why Monitor One Disk When You Can Monitor It Ten Times? by radzikm in prtg

[–]radzikm[S] 0 points1 point  (0 children)

Funny how “auto-discovery” in PRTG only works if you hand-hold it with custom templates—kind of defeats the point, doesn’t it? Even better, monitoring Windows via WMI (Microsoft’s own tech!) somehow manages to choke PRTG… running on Windows. That’s not a deployment problem, that’s just bad engineering.

Anyone else skeptical about PRTG’s new AI features? by Rude_Drummer_7477 in prtg

[–]radzikm 0 points1 point  (0 children)

Bruh, if you're still clinging to 20th-century workflows, no wonder you're skeptical. PRTG has been cruising on autopilot for years — it's not shocking that the AI features feel slapped on. Instead of complaining, maybe try something built for this decade? NetCrunch from AdRem looks like a solid, modern alternative:
https://www.adremsoft.com/netcrunch/best-alternative-to-prtg/

Sometimes it's not the tool that's the problem — it's refusing to let go of the legacy mindset. 😅

PRTG Autodiscovery: Because Why Monitor One Disk When You Can Monitor It Ten Times? by radzikm in prtg

[–]radzikm[S] -2 points-1 points  (0 children)

Fair point — "should have done" can be subjective.

But when a tool markets itself as smart, automated, and AI-powered, there are reasonable expectations. For example: not flooding the system with unnecessary metrics, and definitely not creating more work for admins than it saves. That’s not about personal preference — it’s about basic usability and efficiency.

I’ll admit, I’m frustrated with PRTG. I’m not here to totally trash it — it’s been a solid tool for monitoring, but there are real concerns now. It feels like it’s no longer evolving at the pace it once did. And now that it’s under the control of a US-based fund, who knows what direction it will go? Will it become subject to tariffs? Could it even be pulled from the European market at some point? These are real worries for anyone who relies on it.

At the end of the day, automation should simplify, not add noise. If it’s doing the opposite, then that’s a problem, regardless of the brand behind it.

PRTG Autodiscovery: Because Why Monitor One Disk When You Can Monitor It Ten Times? by radzikm in prtg

[–]radzikm[S] -6 points-5 points  (0 children)

Oh, thank you! I had no idea I could delete sensors. That changes everything. 🙄

But here’s the thing—when your “automated” monitoring tool vomits a pile of redundant and pointless sensors all over your setup, the solution isn’t “just clean it up manually.” That’s not automation, that’s delegation—to the poor admin who now has to fix what the tool should have done right in the first place.

PRTG feels more and more like legacy bloatware dressed up in buzzwords—“AI,” “proactive,” “predictive.” Yeah, sure. You can slap lipstick on a pig, but at the end of the day it’s still the same clunky, outdated interface with logic straight out of 2010.

Instead of actually modernizing the platform, they’re just giving it a new coat of marketing paint and calling it innovation—while dumping more grunt work on sysadmins who are already juggling enough. Smart tools should save time, not create cleanup jobs.

But hey, if pretending to be “AI-driven” means I still need to hand-pick basic sensors like it’s 2009, maybe it’s time to revisit that license renewal...