Not sure what these OIDs are for If they are scalar values (ie they apply to the overall device, rather than a component), then you will almost certainly need a .0 on the end of the OID. snmpwalk gets values starting from the OID you give it but the zenperfsnmp daemon actually does an snmpget so it needs the precise OID.

Alternatively, if these OIDs are for a component (so the OID is part of a table with an answer per instance), then you may have too much OID in your template datasource.

oidview shows
uioSensorStatusTemperatureDegC 1.3.6.1.4.1.318.1.1.25.1.2.1.6

If this is the value you are trying to get, then make sure 1.3.6.1.4.1.318.1.1.25.1.2.1.6 is the OID you have in your template. A component template will append the instance number automatically for each component.

Cheers,
Jane

Email: jane.curry@skills-1st.co.uk    Web: https://www.skills-1st.co.uk

Thanks Jane for the info, learn something every day.

I was able to narrow the OIDs (I think I had the wrong ones) down to where testing with snmpget accepted the comands:

(output from snmpget at CLI of zenoss server)
.1.3.6.1.4.1.318.1.1.10.2.3.2.1.4.1 = INTEGER: 27
.1.3.6.1.4.1.318.1.1.10.2.3.2.1.4.2 = INTEGER: 27

And the data is flowing, I guess I got really lucky on the few new graphs I created, thank you!