An open discussion forum for obtaining help with Nagios Core. Nagios Core users of all experience levels are welcome here. Subforum have been created for the discussion of Nagios Core and Nagios Plugin development.

NOTE: The SourceForge.net mailing lists have been deprecated in favor of this forum in order to expedite support and provide additional features not available on the old mailing list.

I am trying to figure out how I can monitor Windows Server print queues. I have an application called intellscribe that kicks off print jobs to a Solimar system. We had an issue where the Solimar unit wasn't listening to port 515, Nagios alerted of this problem, but there was nothing the the users waiting for output was aware of. So, I am trying to add monitoring to monitor the print queues. I have read a few article from Google searches that indicate using Performance Monitors; however, I don't see anything listed for this. The other snag I have encountered is the application writes it's log to a dated CSV file. I was going to try and use NRPE to monitor the log file for a "disconnect" message and then send an alert.

Is it possible to monitor a dated csv file and Nagios looks at the latest file all the time for specific content?Any other way to monitor local or remote print queue?

There could be more (better) plugins out there. This is just an example. You could call this plugin via check_nrpe and NSClient++ or via check_ncpa.py if you wish. You could also use NCPA or check_nrpe with NSClient++ to call a custom script, that can monitor the print queues locally.

As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.

Be sure to check out our Knowledgebase for helpful articles and solutions!

The application creates the logs in the directory like this.20180816.CSV20180815.CSV20180814.CSV20180813.CSV

Start of each new day a new dated .CSV file is created which the application logs to.

Here is a sample of data from the logs. The issue I am trying to get monitored occurred again between 1:35AM-1:42AM. There is a socket error which prevents the print job from getting sent to the printer.

Next step is configuring a custom timeperiod so this only runs three times a day. Once at 11:57PM to check the log before the date rolls on the filename. Then run it again at 6:00AM before people get in at 6:30AM, and once again at 3:30PM before they leave for the day around 4:00PM?

I can't think of a way to check this so once it sees the "Socket errror" it ignores that instance and only reports on new occurrences. So creating a custom time period to have the current day log checked 3 times a day should hopefully be sufficient.

Who is online

Nagios, the Nagios logo, and Nagios graphics are the servicemarks, trademarks, or registered trademarks owned by Nagios Enterprises. All other servicemarks and trademarks are the property of their respective owner.