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

Transform in Universal Device Poller

I'm having an issue with a Universal Device Poller transform. I've got a poller set up that returns an integer value for the temperature, but it needs to be divided by 100. For example 2137 should be 21.37 degrees Celsius. The poller for that OID is returning the result as it was designed.

I want to define a transform for it to divide the value by 100. However, even if I just add the poller only into the transform, for example the poller is "digital-sen1-1" - with just "{digital-sen1-1}" in the formula, it is returning "-2" instead of "21.37". Interestingly enough, when the temperature is below about 20.50, it returns "-1.01".

Why is this not behaving?

Find more posts tagged with

Accepted answers

dlharfst

Ok I figured it out. This is a bug - absolutely no question.

It was evaluating the name of the poller as if it were part of the formula. I left the name of the poller as it was defined in the MIB - "digital-sens1-1". When I renamed the poller to "InternalTempSensor", the transform returned the correct value.

With the transform formula set as {digital-sens1-1} it would return "-2" always. With it set to {digital-sens1-1]/100, it would return "-1.01" always.

When I renamed it to "InternalTempSensor", and set the formula to {InternalTempSensor}/100, it returned the expected result - the value of InternalTempSensor divided by 100.

All comments

christopher.t.jones123

@dlharfst, can you post a screenshot of the transform formula?

dlharfst

christopher.t.jones123

@dlharfst, it should read {digitalsen1-1}\100. Give that a try and post the results if its not the expected output

dlharfst

I would assume {digitalsen1-1}/100. What you posted with \ gives an evaluation error. But even without the division by 100, it is not giving the value of {digitalsen1-1}

christopher.t.jones123

@dlharfst, is the UnDP polling the value an SNMP table? I believe that it has to be a a specific OID within the table vs the table. You can tell by looking at the UnDP. If it is a leaf looking icon then it is a singular OID, if its a table looking icon then its polling the table.