Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

APM 2.5 Very Buggy

I don't know about anyone else but I have found APM 2.5 to be very buggy. After several attempts at creating a new monitor on my NPM server I finally gave up and contacted support. Although the tech was helpful the end result was the same, I did what he suggested and moved the NPM installation and all of the modules to a separate server from my database and attempted to create a new APM monitor.

Guess what it didn't work! I got the same result, keep in mind this was a fresh install with no alterations to the default configuration. I found that pages don't always load, script errors are pretty common, and that the application outright behaves erratically.

I know this is of no value technically to anyone on this board but it sure helps my mental state to vent, at least when you buy a car for 40k and it don't run you can bring it back.

Find more posts tagged with

apm

Accepted answers

All comments

Donald_Francis

Like most of SolarWind's products its takes a lot of massging and custimization. But once you got it where you want it , it's decently solid. The trick is just getting it where you want it.

FormerMember

Until the next upgrade......

FormerMember

Scott,

While I understand that it helps you to vent here on thwack, but if you were to post more detail about your problem, we might be able to help. I avoid trying to be reflexively defensive, but your claim APM 2.5 is "very buggy" is at odds with our data. We shipped APM 2.5 in February. We have not had to ship any service packs yet. There are a few minor bugs and one serious and hard-to-diagnose problem that a small number of people have found with WMI, but otherwise, it's been a really solid release.

That's not to say you don't have a very real problem. Again, if you provide some details, we will try to help. But in exchange, let's keep the discussion constructive. In other words, don't just tell us we suck. Tell us exactly how we suck.

rgalloni

Denny I don't know who Scott is but nowhere in my post did I say you suck I merely expressed my frustration with your product. In regards to telling you why you suck, well! I did that using the proper channels and in a very professional manor. And your right you shouldn't be quick to go on the defensive, now what if I had been a Mormon who may be appalled or offended by your language! I'm not but that's beside the point.

Being in the position you are in I'm sure you have been around long enough to know regardless of what a customer may say it is always important to maintain professionalism. I would also point out that whatever data you are reading may be inaccurate considering the numerous post on this board regarding the product and the bugs. You do read the post don't You?

Now lets get to the reason why! as you have asked. I had recently posted to this board explaining the issue I had with screen shots, "APM Behaving Erratically!"not one support person responded to the post. I also opened a ticket with your support department, guess what they were not able to resolve the problem and suggested the NPM and it's modules be reinstalled on a separate server from the database. We did as they directed and when everything was reloaded and the NPM was up and running the outcome was the same. "ERRATIC BEHAVIOR"

So I have to ask, if there are no other applications running on the server and the server is a fresh build from scratch "Only your Products" and the APM still behaves erratically were is the problem? I also should point out that one of your support tech remote into the server for themselves and witnessed the behavior and they were not able to fix it.