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

Combination Alert for Print toner & Cartridge Type

I've got a custom poller to check for low toner on our printers. Using OID 1.3.6.1.4.1.11.2.3.9.4.2.1.4.1.10.1.1.18 and alerting if this percentage value is < 10.

This alert reaches out to those who will purchase and replace the toner, and I would like to include the cartridge type in the alert.

The OID for cartridge type is 1.3.6.1.2.1.43.11.1.1.6.1.1.

How can I combine two pollers in one alert?

Find more posts tagged with

Accepted answers

All comments

MarieB

Hi jdgray--

We are researching this for you and will get back to you.

In the meantime, I'm moving your post to the NPM forum where it will have more visibility.

pacetti

jdgray,

Unfortunately, you will not be able to include the OID value in the alert itself, but you can include the cartridge type on the Node Details view for the printer, as follows:

Confirm that you have created a poller for each OID, both toner level and cartridge type, and then confirm that they are both assigned to all corresponding printers. For more information, see "Monitoring MIBs with Universal Device Pollers" in the SolarWinds Orion NPM Administrator Guide.
Navigate to a Node Details view, and then click Customize Page at the top right of the view.
Click + next to a displayed column.
Click + to expand Node Detail Reports.
Check Universal Device Poller Status.
Click Submit on the Add Resources view, and then click Done on the Customize Node Details view.

For nodes to which you have assigned the toner level and cartridge type pollers, the new resource will report corresponding values. If you receive an alert, as you have configured it previously, you need only click the alert to see the Node Details view for the priniter that needs toner. The Universal Device Poller Status resource will then report the cartridge type required.

Currently, it's an extra step, but I can log a feature request to save the step by including poller results as variables in alert actions, if you'd like.

jdgray

Please create a feature request to include additional poller results as variable in alert actions. The recipients of these emails will not have access to SolarWinds.

smargh

I can imagine it being quite difficult for Solarwinds to code a relationship between a triggered alert and the associated value for that specific record for that specific node or poller record. It's also very difficult to work around, as custom SQL in the emailed alert isn't officially supported by SW and is difficult to do manually without a lot of cursing. I gave up a long time ago trying to get it to work correctly - it seems to require a very specific syntax.

Another thing which could complicate things is that it could perhaps end up being limited to custom pollers which only return one value. Currently, it's only possible to [reliably] alert if a value in a column exists - it's not possible to know which row an alert relates to, nor if there are ever multiple mentions of a particular string - it's just "check for this string in the result of a poller and kick off an alert if one is found, then stop looking" - you won't know what the found value is unless you dump the whole string in $status, which can often result in long unreadable output. As for specifiying row ID to find specific rows, the IDs can change over time, and individual alerts must be done for for each node, rather than one alert for all nodes, which is impractical.

For example: it would be nice to be able to have an alert for a failed hard drive where the triggered email stated (from my other universal pollers) the part# of the drive, the size, overall status, SMART failure code, and the serial number.

As another example, it's not currently possible to include in the alert emails the description of which temperature sensor is failing - the alerts must be based upon a custom GET TABLE poller rather than GET NEXT, otherwise only the first row is checked.

Someone feel free to correct me if I'm mistaken on any aspects.