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

Custom Pollers : Transform results AVG calculation is not an average

SolarWinds Orion Network Performance Monitor v9.5.0

We have 16 custom pollers that get temperature via SNMP from a sensatronics (see the screenshot below). We made a "Transform Results" that is the average of those 16 values. The average always comes out very wrong. The temperature sensors are in the 60 degrees range. The average value, whether with the AVG function or with arithmetic, always comes out 8.5. My formula looks like this

AVG({Temperature 01},{Temperature 02},{Temperature 03},{Temperature 04},{Temperature 05},{Temperature 06},{Temperature 07},{Temperature 08},{Temperature 09},{Temperature 10},{Temperature 11},{Temperature 12},{Temperature 13},{Temperature 14},{Temperature 15},{Temperature 16})

Any ideas?

Find more posts tagged with

temperature

custom_poller

transform

Accepted answers

axjww

Solved. The Custom Poller builder doesn't let you put spaces in the names of the pollers. In my infinite ninja wisdom, I updated the poller names in the Database directly (CustomPollers table), because it was faster than updating sixteen pollers with the GUI. I had put spaces in the names.

As soon as you remove the spaces from the poller names the AVG() function works as expected.

All comments

axjww

As soon as you remove the spaces from the poller names the AVG() function works as expected.

borgan

It looks like you demonstrated one of the risks of modifying the Orion database directly. In this case, the database manager allowed youto changes the custom poller names in a way that the UnDP would not habe allowed.

Good job. You could have gone on a while longer never knowing this.

byrona

Is there any good reason why one can't have spaces in the poller names? When I do custom reports based on these pollers it always looks funny because the poller name can be difficult to understand due to the lack of spaces. I think it would be really nice if this allowed spaces.

axjww

I'll speculate that it is just a syntax issue. They'd have to quote it or escape it in the database and their programming which would be tedious. I just use camel case and it's decent. Underscores are allowed I believe.